a month ago
- Deployment IDs: e515dbee-1b44-401f-af55-f41580c0b34d (and the earlier one: b945176f-9428-4737-9cc6-c2e44072c382)
- Service: endless-fr/phoenix (main branch)
- Commit: f7419db3727b12c75a8b45e650dadd6091173e36
- Issue: Four consecutive build attempts failing at BUILD_IMAGE stage with zero Docker output after snapshot unpacking, timing out after ~10 minutes across multiple builders (builder-rssxib, builder-ytzuhu)
- Context: Dockerfile and code are unchanged from previous successful builds; same Dockerfile deployed successfully on other branches recently
3 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We're looking into an issue with builder scheduling that is affecting your builds. Our infrastructure team is investigating. In the meantime, canceling the stuck builds and redeploying may route them to a different builder node and unblock you.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Thank you for your quick response !
I don't think I need to cancel the stucked builds because after 10 minutes it automatically fails (and the deployment is in the failed status).
I clicked on the three dots menu to redeploy it and trigger a new deployment it still fails. I tried it four times in a row, that's why I decided to open a ticket.
I'm trying a new deployment and this one seems to works !
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Glad the latest deploy went through. The issue was caused by degraded builder nodes that were still in rotation. If you hit this again, redeploying should route to a healthy node. Let us know if builds stall again.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved brody • about 1 month ago