10 months ago
Build Process:
- Snapshot fetched successfully (86 MB)
- Archive unpacked successfully
- Build daemon connection fails (connection refused)
Services:
- Backend: Dockerfile builder
- Frontend: Nixpacks builder
- Builder: "builder-dwjhes" (Metal builder)
What I've tried:
1. Multiple redeploy attempts with 15+ minute delays
2. Disconnected other services to prevent simultaneous builds
3. Verified Dockerfile and railway.json (no config issues)
4. Checked Railway status page (all systems operational)
Timeline:
- Started on Dec 9, 2025
- Still occurring as of Dec 10, 2025
Question:
Has anyone else experienced this issue? The snapshot and unpacking complete successfully, but the build daemon refuses connections. Is there a workaround or known fix?
Any help would be greatly appreciated!
Attachments:
scheduling build on Metal builder "builder-dwjhes"
fetched snapshot sha256:514597702d32fc524d6a66c1ec90ba6109e3bd24fe7042fbde52c7e5d012c293 (86 MB bytes)
fetching snapshot82.4 MB1.1s
unpacking archive153.1 MB1.5s
Build Failed: build daemon returned an error < listing workers for Build: failed to list workers: Unavailable: connection error: desc = "transport: Error while dialing: dial unix /writeable/merged/run/buildkit/buildkitd.sock: connect: connection refused" >
3 Replies
10 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
10 months ago
Hey there!
We're tracking this issue over here --> https://station.railway.com/questions/build-failed-build-daemon-returned-an-e-b0158a3b
I am going to close this one as duplicate. Thank you for the report.
Status changed to Awaiting User Response Railway • 10 months ago
Status changed to Closed echohack • 10 months ago
10 months ago
✅ The ticket Build service temporarily unavailable has been marked as completed.