21 days ago
Body:
Service: api (ID 32a33af6-a1ed-4784-b456-855b70186588)
Project: giving-spontaneity (ID e1c662f3-c133-4c18-ad96-5ae80c1d1dbc)
Environment: production (ID 4c4140bd-484d-4581-a37a-ae09f79e1302)
Service URL: https://approc-api.up.railway.app
Problem: railway up (CLI) is stuck indefinitely at BUILD_IMAGE stage.
Service Configuration:
- Builder: Dockerfile
- Dockerfile Path:
apps/api/Dockerfile - Deployment method:
railway upfrom repo root
Exact Symptom:
railway upuploads correctly ("Uploaded")- Build starts but hangs indefinitely
railway logs --build <deployment-id>only shows:
scheduling build on Metal builder "builder-zzixyx" scheduling build on Metal builder "builder-zzixyx"
- No actual build steps appear (no
npm ci, noCOPY, etc.) even after 3+ minutes - Build never progresses and eventually times out/fails
Affected Deployments (all fail identically):
19483d4a-da5c-4d21-818a-e1ed9d113b282a105f1a-317c-4fdb-aa77-db33b17f5e28fffdd4ad-d480-4270-b14f-afc188c0a567
Reproducibility: 4-5 distinct attempts over ~20 minutes today, all stuck on the same builder node (builder-zzixyx). Same symptom observed in a previous session.
Important Note: A redeploy triggered from the web dashboard (not CLI) succeeded at one point — so the build system overall is not down, only this specific queue/path via railway up.
Request: Please check the health and logs of b
0 Replies
21 days ago
It looks like you already have a thread open about this: Builder zzixyx stuck: railway up CLI deployments fail with zero build logs. We're automatically closing this one, and we'll reply to you there soon. If you have anything more to add about this topic, please post it in that thread.
Status changed to Duplicate Railway • 21 days ago