Skip to content
Repeated deployment failures — BuildKit connection dropped
vmatson-studio
OP

23 days ago

Hello Railway team,

Two consecutive deployments of my production service have failed during image building. Railway’s diagnosis identifies an “Infrastructure Error” caused by the build daemon connection dropping.

Project ID: e0dfa7bf-9e62-4f37-9f51-264184e25fed

Service: moni-tito-app

Environment: production

Region: sfo

Builder: Railpack 0.43.0

Node: 22.23.3

Latest failed deployment:

910866cb-a735-496a-b3a9-987b7ab9ca33

Previous failed deployment:

b6fe17bd-be64-4131-8f89-bfac2531ba0e

Error:

“listing workers for Build: failed to list workers: Unavailable: connection error”

“/run/buildkit/buildkitd.sock: use of closed network connection”

The latest attempt spent about five minutes initializing, then failed during image building. The Deploy stage did not start.

Could you investigate the build infrastructure and advise how to retry successfully? Please preserve the existing production deployment and persistent volume.

I can provide the build logs and screenshots.

Solved

3 Replies

Status changed to Awaiting Railway Response Railway • 23 days ago


dizzydes90
EMPLOYEE

23 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 • 23 days ago


chandrika
EMPLOYEE

23 days ago

Sorry for the trouble. The build failures you're seeing ("build daemon returned an error" before any build step runs) are caused by an issue with our build infrastructure in US West, not by anything in your project or code. You don't need to change anything on your side.

We're working on a fix and tracking it here: https://status.railway.com/incident/ILLVW9WG

Your running services aren't affected. Redeploying may work in the meantime, but it can fail again until the fix is in. Once the incident is resolved, redeploying the same commit should build normally.


chandrika
EMPLOYEE

23 days ago

The issue causing builds to fail in US West has been resolved. Builds are now completing normally. If a build failed during this incident, redeploying it should now succeed.


Railway
BOT

4 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 • 4 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...