Skip to content
Repeated BuildKit daemon disconnect before application build on the same commit
xiswaudits
OP

22 days ago

Our DARBS web-service deployments repeatedly fail while listing BuildKit workers. No execution of npm install or npm run build is logged before the error. Local TypeScript checks and the production Vite build pass.

The most recent retry deployed exactly the same commit, without code, service configuration, resource or spending-limit changes. It failed again at 2026-10-28T10:13:56Z with:

text

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

Identifiers for investigation:

  • Project: 466ed8d9-251b-412f-a16b-96c40845398c
  • Service: 60fe7976-edd6-4cd7-aaf6-6076ffe87382 (Darbs-WebApp-clone)
  • Environment: 1e2eb16d-23ba-446b-9a40-c0fd933077a8
  • Commit: c4088787bd78f4e2b2d6780c4ad36902b23cd2b8
  • Latest failed deployment: 1c2943c8-98d3-4e04-b1e0-1d99fda58dd1 (created 2026-10-28T10:11:46Z)
  • Earlier failures for this commit: c52c0445-d1b4-436a-8eeb-f49a04264624, b2a85e22-bbb9-4c62-a03f-878a897f6d15
  • Build driver: Railpack 0.43.0; latest preparation output selected Node 24.22.0.

The previous production deployment is still serving successfully, so this is a blocked release rather than a production outage. Could you inspect the assigned build worker/BuildKit daemon and advise how to get this exact revision built successfully?

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • 22 days ago


dizzydes90
EMPLOYEE

22 days ago

We're sorry for the trouble. That "build daemon returned an error" failure matches an active incident, Builds failing in US West, where some builds in that region fail before any build steps run. Running services like your current production deployment are not affected.

Your build fails before npm install starts, so nothing in your commit is involved, and redeploying may succeed in the meantime. You can see the incident details here.


Status changed to Awaiting User Response dizzydes90 • 22 days ago


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