Skip to content
Repeated BuildKit worker connection failures
bhwmai
OP

22 days ago

Our production service repeatedly fails before any Dockerfile build steps run:

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"

  • Example failed deployment: aa93d29b-37f1-4b3e-9ec6-5316994d90bc

Previous deployments successfully used this Dockerfile configuration. We reviewed the commits after the last successful build and found no build-breaking configuration or dependency changes.

We tried redeploying the same commit multiple times and then pushing a small Dockerfile cache-invalidation change. Every attempt encounters the same worker-listing error, before dependency installation or application compilation.

Could you inspect the BuildKit infrastructure assigned to this service and recover or replace the affected worker if necessary? Please confirm whether this relates to an ongoing platform incident and whether there is a supported workaround.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 22 days ago


22 days ago

Apologies for the disruption and the delay getting back to you. These build failures were caused by a transient issue with an upstream provider, which has since been resolved. We’re sorry this interrupted your releases.


Status changed to Awaiting User Response Railway • 22 days ago


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