22 days ago
I'm experiencing persistent build failures when deploying my Ruby on Rails application, JobFlow, to Railway.
Every deployment attempt fails with the following 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" >
Plan: Hobby
Service: jobflow
Environment: production
Application: Ruby on Rails
Repository: https://github.com/cpllumaj01/jobflow
First observed: October 28, 2026
Troubleshooting attempted:
Retried the failed deployment multiple times.
Attempted redeployment using the Railway CLI and dashboard.
Added NO_CACHE=1 to force a fresh build.
Checked Railway's status page.
Unfortunately, every attempt continues to fail with the same BuildKit connection error. The failure appears to occur during build infrastructure initialization, before the application build proceeds.
Could someone investigate whether the build worker assigned to my project is unhealthy or whether this is related to Railway's ongoing infrastructure recovery?
Project ID: 203d2532-eff0-4d08-ba15-17e929ed2699
Edit:
I also successfully built the application locally using the exact Dockerfile:
docker build --progress=plain -t jobflow-test .
All steps completed successfully, including gem installation, Rails asset precompilation, and final image creation.
Railway continues failing during BuildKit initialization with the buildkitd.sock connection error.
This suggests the issue is specific to Railway's build infrastructure. Could someone investigate the builder assigned to my project?
2 Replies
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
I also have the same problem
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
Also experiencing this issue
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
Status changed to Solved cpllumaj01 • 21 days ago