a month ago
Problem
Every railway up deployment fails during the "Build › Build image" step in approximately 10 seconds. The build never executes any Dockerfile instructions — no Docker layer output, no compilation, nothing. The only output is:
scheduling build on Metal builder "builder-oujoni"
scheduling build on Metal builder "builder-oujoni"
Deploy failedThe service is consistently assigned to builder builder-oujoni and always fails there.
What I tried
- Multiple railway up attempts — all failed the same way
- Added .dockerignore to reduce snapshot size — still failed
- Fetched build logs via CLI railway logs --build <deployment_id>) — no output beyond the scheduling lines
- Checked Railway status page — all systems reported as operational
- Found a similar reported issue: https://station.railway.com/questions/scheduling-build-on-metal-builder-not-de-ff529db3
Key finding
Redeploying the previous day's deployment (without a new build) succeeded — the healthcheck passed and the service is currently running.
Failed deployment IDs
- 6ab6bc07-dbc7-44b4-bd7e-7f33dc342fba
- 80edc2ae-61da-485c-bd56-22c63a12b43f
- 050e7078-39a4-43af-8870-c3e08da979d5
- 59231fab-b9aa-4696-ad55-8b1b08694190
- b36ad4a5-e737-43a2-bab1-824ebe9ee493
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hello,
The build is failing with [ERROR] ##NOT-FOUND## repository not found
You can see the error in deployment "Details" tab.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago