Build error after many tries build daemon
pavankris
PROOP

10 days ago

Getting this build error

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" >

Have tried many times.

Awaiting User Response

3 Replies

Status changed to Awaiting Railway Response Railway • 10 days ago


dizzydes90
EMPLOYEE

10 days ago

That buildkitd.sock error matches a builder fault from the October 21 incident, and that fault has since been dealt with. Start a fresh deployment rather than redeploying an existing one, either by pushing a new commit or by choosing Deploy Latest Commit from the Cmd+K / Ctrl+K command palette.

If a fresh deployment still fails, please share the link to that deployment.


Status changed to Awaiting User Response dizzydes90 • 10 days ago


chandrika
EMPLOYEE

10 days ago

This corrects our earlier reply: these failures come from a new incident in US West, not the October 21 one.

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

10 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.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...