a day ago
Error:
Build Failed: build daemon returned an error < failed to solve: ResourceExhausted: failed to copy to tar: rpc error: code = ResourceExhausted desc = write /var/lib/builder/build-sessions/fc60bd3e-741f-4069-aa12-2c22396cb563/oci-export-1434202055: no space left on device >
Failed deployments (most recent first):
- fc60bd3e-741f-4069-aa12-2c22396cb563 (2026-11-03 09:47 -06:00)
- 496f3c5b-779c-464f-b9a6-d2ad807b9378 (2026-11-03 01:05 -06:00)
- Several more since 2026-11-02 (all the same error)
What I already tried:
- railway redeploy --from-source
- railway up from a clean checkout
- Retrying at different times of day (about 12 hours apart)
Nothing in the Dockerfile or the repo changed between the last successful build and the failures. This looks like the builder host assigned to my project is out of disk, similar to https://station.railway.com/questions/no-space-left-on-device-9fecc4c3
Could someone clear or restart the builder for this project, or move my builds to a different build host? Production is still running on the last successful deployment, but I can't ship any fix until builds work again.
2 Replies
Status changed to Awaiting Railway Response Railway • 1 day ago
a day ago
We’ve escalated this to our build team. Your Dockerfile steps complete successfully; the failure happens while exporting the image, when the build environment runs out of space. We’ve included the failed deployment and builder details, so you don’t need to repeat the retries you’ve already tried.
We’ll update you here when we have a fix or a confirmed workaround.
Status changed to Awaiting User Response Railway • 1 day ago
6 hours ago
Hey,
We bumped the builder disk size for you service. Can you try again?