Service stuck on broken Metal builder builder-goucoz — Railpack jobs producing no output
javierci
PROOP

25 days ago

Hey, I have an urgent issue and already opened a private support thread,

sharing here in case anyone has hit this or someone from the team can take

a look.

Service whatsminder (project endearing-prosperity, production, region

us-west2) — every deploy since switching to Railpack lands on builder

builder-goucoz and fails silently in 10–50s. Build logs only show:

"scheduling build on Metal builder builder-goucoz"

…and nothing after.

Already verified:

  • railway.json: "builder": "RAILPACK", "metal": false
  • railpack.json present (Node 20, npm install / npm run build / node dist/index.js)
  • Dockerfile renamed to Dockerfile.legacy
  • 8 retries, all routed to the same broken builder
  • Railway Diagnose says: "The project configuration is correct and would build successfully if Railpack actually ran. Reach out to Railway support to investigate or reassign the builder."

Service ID: 32a3e0dc-325c-41bc-8e57-4c73b498d176

Failing builder: builder-goucoz

Last successful deployment: 4917ffbe (Dockerfile-based)

Private thread: https://station.railway.com/support/service-stuck-on-broken-metal-builder-bu-ef9fdd1e

Thanks!

Closed

0 Replies

Status changed to Closed brody 25 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...