Pain point · Reliability & bugs · Blocks work
Docker container will not start in v1.33 because npm-run-all is missing
4 source threads · first seen 2022-06 · last seen 2025-05
Summary
After updating to release 1.33 the Docker container fails to boot because npm-run-all cannot be found.
- Affects
- docker self-hoster
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“I get the file-system-permission-related error below in the migration step”
“Error loading shared library libssl.so.1.1: No such file or directory”
“Upon starting up v2.8.0 via docker you get a Node.js error on the semver package”
“/bin/sh: npm-run-all: not found”