22 days ago
My golddays backend deployment has failed twice before any project build steps ran.
The first failure showed:
resolve image config for docker-image://ghcr.io/railwayapp/railpack-frontend:v0.43.0
context deadline exceeded
I triggered another deployment using an empty commit. It failed after approximately 4.5 minutes. Its Build Logs only contain:
“All aboard, next stop: builder v4”
Railway Diagnose classified both failures as infrastructure errors. No dependency installation or application build output appears.
Service: golddays
Builder: Railpack
Root directory: /backend
Start command: gunicorn app:app
Latest failed deployment short ID: 9f1393c4
The previous deployment remains online, but I cannot deploy the latest changes. Could you investigate the builder timeout and advise how to retry successfully?
1 Reply
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
This is on our side. There is an active incident on our build infrastructure (https://status.railway.com/incident/ILLVW9WG, "Builds failing in US West"): builds are failing before any of your build steps run, with the build daemon connection dropping or the build machine never coming up, which is exactly what your deployments show. Your source, build configuration and dependencies are not at fault, and nothing needs to change on your end.
Running services are not affected. A fresh deployment of the same commit may get through in the meantime; otherwise please follow the status page for the all-clear, and redeploy once it is posted.
Status changed to Awaiting User Response Railway • 22 days ago
3 days 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 • 3 days ago