10 hours ago
Builds for personal-os-runtime-prod consistently fail immediately after being scheduled on Metal builder builder-aahlhs. This occurs with both Railpack and Dockerfile builds. No build commands execute and the build log contains only scheduling build on Metal builder "builder-aahlhs".
This reproduces across Railpack and Dockerfile builds, including a manual dashboard redeploy. Is builder-aahlhs experiencing an infrastructure issue, and is there a way to force the service onto another builder?
2 Replies
Status changed to Awaiting Railway Response Railway • about 10 hours ago
an hour ago
This isn't a builder fault, and switching builders won't change the result. Your latest deployment's build did run: it loaded your Dockerfile, pulled node:24-bookworm-slim, and got as far as the RUN npm ci steps. Both npm ci steps then failed with npm error EUSAGE: "The npm ci command can only install with an existing package-lock.json or npm-shrinkwrap.json".
Those error lines are in the full build log, logged at 22:33 UTC. The scheduling build on Metal builder line comes after them, at 22:34 UTC, so it's the last line in the log and easy to mistake for the only one.
Status changed to Awaiting User Response brody • about 1 hour ago
an hour ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 hour ago
an hour ago
Make sure package-lock.json file exists on the folder you're running that command on
You can run npm install to reinstall dependencies and generate the lockfile, If the file exists locally, you probably put it in the .gitignore file