Skip to content
Build failures — BuildKit daemon connection drops before Dockerfile execution (repeated across several deployments)
dnelse2b
OP

22 days ago

We're seeing repeated build failures on our service where the build stops immediately after the code snapshot is unpacked, before any Dockerfile step runs. The build log shows only the builder start line (uploading snapshot, unpacking archive) with no further output and no error from our side.

Error reported by the builder:

Build Failed: build daemon returned an error < listing workers for Build: failed to list workers: Unavailable: connection error: desc = "error reading server preface: raw-read unix @->/run/buildkit/buildkitd.sock: use of closed network connection" >

This has happened on multiple consecutive deployment attempts of the same commit/config, with no changes to the Dockerfile, railway.toml, or source code between attempts — ruling out a code or configuration issue on our end. Railway's own automated diagnosis on one of these attempts confirmed: "the build failed when the connection to the build daemon dropped right after the code snapshot was unpacked, before any Dockerfile step ran, and the code and config were not at fault."

Failed deployment IDs:

  • 0bda61c8-476f-429a-8d28-8173d01271d7
  • b59a0950-013d-4aa0-a170-3675ff999f1a
  • bc84aab7-7c0c-4b12-99b6-25c29ae1f7bd

Service: Conecta360Ws (backend)

Builder: Dockerfile (builder v4)

Could you please investigate the builder infrastructure for these attempts? Retrying (redeploy) has sometimes succeeded after one or more failures, which points to a flaky backend builder rather than anything deterministic on our side.

Solved

3 Replies

Status changed to Awaiting Railway Response Railway • 22 days ago


chandrika
EMPLOYEE

22 days ago

We're sorry for the trouble. These failures match an active incident, Builds failing in US West, which is causing some builds in that region to fail with the "build daemon returned an error" message before any build step runs. Your service deploys to US West, and running services are not affected.

We're working on a fix. In the meantime, redeploying may succeed.


Status changed to Awaiting User Response Railway • 22 days ago


chandrika
EMPLOYEE

22 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

22 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

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...