Builder node builder-fsjlwt stuck — cannot pull container images, 0/100 deploys in 3 days
embeddedflowai
HOBBYOP

4 months ago

Project 19ec38cc, service 199e4ffe, all builds route to Metal builder builder-fsjlwt which hangs at image resolution (Docker Hub +

GHCR). Tried Dockerfile, Nixpacks, and Railpack — all hang at the same step. Builds that do get past the pull complete all steps but

get canceled by newer deploys. Need builder node reset or reassignment.

Solved

7 Replies

Status changed to Awaiting Railway Response Railway 4 months ago


tiiwoo
PRO

4 months ago

Same issue here — my builds are also stuck on builder-fsjlwt, perpetually showing "Building the image..." and never progressing.


jamesajao1
HOBBY

4 months ago

Me too


jamesajao1
HOBBY

4 months ago

"Every build is being scheduled on builder-fsjlwt which is broken — builds either hang indefinitely or fail. Project: enchanting-adaptation, Service: worker. Please reassign to a different builder or kill this node."


sam-a
EMPLOYEE

4 months ago

We're aware of issues with the Metal builder node you're hitting. Cancelling the failed build and redeploying may route you to a different builder and resolve it. If that doesn't work, let us know.


Status changed to Awaiting User Response Railway 4 months ago


sam-a

We're aware of issues with the Metal builder node you're hitting. Cancelling the failed build and redeploying may route you to a different builder and resolve it. If that doesn't work, let us know.

embeddedflowai
HOBBYOP

4 months ago

doesnt work sorry, tried that mutiple times. this has been going on for three days now


Status changed to Awaiting Railway Response Railway 4 months ago


sam-a
EMPLOYEE

4 months ago

Apologies for the trouble. In resolving the initial issue we needed to pause builds and deployments on Metal, and declared an incident that our team is actively working. Follow updates at https://status.railway.com/incident/cmm2cvzx50dxkx4rz5dx8efxh


Status changed to Awaiting User Response Railway 4 months ago


sam-a

Apologies for the trouble. In resolving the initial issue we needed to pause builds and deployments on Metal, and declared an incident that our team is actively working. Follow updates at <https://status.railway.com/incident/cmm2cvzx50dxkx4rz5dx8efxh>

embeddedflowai
HOBBYOP

4 months ago

thank you


Status changed to Awaiting Railway Response Railway 4 months ago


Status changed to Solved embeddedflowai 4 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...