Cannot build
usepathlyuk
HOBBYOP

a month ago

Project ID: a6f7d03b-48ce-40a1-bc62-a72f8d20e3d5

Service ID: 1314732c-dfde-447c-9c07-76919ac17fe4

Failed deployments: 36f5748a-4128-4a4c-b292-35ac07a17d32, 220b124f-8f33-4dd3-8a42-6a16493fa9ef, 9bc263a5-7495-4e1c-8d75-6f74c3096040

Issue: Builder (Railpack) schedules on builder-wpdzgx but produces no logs and fails after 6-7 seconds with "Failed to build an image". Same builder assigned repeatedly. Code is valid (tested locally). This appears to be builder infrastructure failure.

The builder is stuck or broken on Railway's side.

$10 Bounty

4 Replies

usepathlyuk
HOBBYOP

a month ago

npm install

4m 12s

npm error Exit handler never called!

npm error This is an error with npm itself. Please report this error at:

npm error https://github.com/npm/cli/issues

npm error A complete log of this run can be found in: /root/.npm/_logs/2026-08-23T19_08_04_513Z-debug-0.log

scheduling build on Metal builder "builder-wpdzgx"

Build Failed: build daemon returned an error < failed to solve: process "npm install" did not complete successfully: exit code: 1 >


Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 1 month ago


Try to set NO_CACHE=1 in your service variables, to rule out any caching related issues.


darseen

Try to set `NO_CACHE=1` in your service variables, to rule out any caching related issues.

usepathlyuk
HOBBYOP

a month ago

Tested to rule out code/config:

  • Multiple build commands (npm ci --prefer-offline, default Railpack)
  • NO_CACHE=1 to bypass any build cache issues
  • Service config reset to defaults
  • All fail identically at ~4m mark

This is a builder resource or timeout issue. Same builder assigned repeatedly. Code and config are correct.

Request: Reassign to a different builder or investigate builder-wpdzgx infrastructure fault.


Based on the error, it seems that the issue is happening during npm install. Do you have any db migrations running in postinstall? If yes, try to move the db migrations to pre-deploy command. Also, you can try to use a package manager like pnpm instead of npm.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...