3 days ago
We're running into out of space errors on our build.
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/cc5f9a58-0e51-4172-9f07-349f455abc61/oci-export-199165008: no space left on device
This just started this am
12 Replies
Status changed to Awaiting Railway Response Railway • 3 days ago
3 days ago
That error means the builder machine's own working disk filled up while it was exporting your image, rather than anything in your image or build configuration.
A fresh redeploy usually lands on a builder that has space, so starting a new deploy of the same commit should get the build through.
Status changed to Awaiting User Response noahd • 3 days ago
noahd
That error means the builder machine's own working disk filled up while it was exporting your image, rather than anything in your image or build configuration. A fresh redeploy usually lands on a builder that has space, so starting a new deploy of the same commit should get the build through.
3 days ago
Hi @noahd, I've tried that a few times.
Status changed to Awaiting Railway Response Railway • 3 days ago
gmacmaster
Hi @noahd, I've tried that a few times.
3 days ago
Trying the diagnostic tool says "The Next.js 16.4.5 build finished, but the deployment failed while exporting the container image, and the logs show no error message at that step. Redeploying may help, and if the failure keeps repeating, contact Railway support." I've tried 10 times now
Status changed to Awaiting Railway Response Railway • 3 days ago
3 days ago
Your preview deployment is now running. We increased its builder disk space, rebuilt the same commit successfully, and confirmed the preview is responding. The larger disk allocation will also apply to future builds of this preview.
Sorry we sent you through repeated retries before addressing the disk limit.
Status changed to Awaiting User Response Railway • 3 days ago
sam-a
Your preview deployment is now running. We increased its builder disk space, rebuilt the same commit successfully, and confirmed the preview is responding. The larger disk allocation will also apply to future builds of this preview. Sorry we sent you through repeated retries before addressing the disk limit.
3 days ago
Thanks Sam! Is there I can do this my self in the future?
Status changed to Awaiting Railway Response Railway • 3 days ago
sam-a
Your preview deployment is now running. We increased its builder disk space, rebuilt the same commit successfully, and confirmed the preview is responding. The larger disk allocation will also apply to future builds of this preview. Sorry we sent you through repeated retries before addressing the disk limit.
2 days ago
Sam, this is now happening on our staging environment. Anything I can do?
2 days ago
Yesterday’s disk increase applied only to the preview, so staging hasn’t received it.
Your build installs dependencies across the monorepo, even though it only builds the portal. Try setting RAILPACK_PRUNE_DEPS=true in a preview environment and redeploying. This removes development dependencies before packaging, so first check that Next.js and anything needed to run the portal are listed under dependencies, then test that the app starts and works correctly. (I probably should have suggested this yesterday in the first place. Sorry!)
Let us know if that doesn't work and we can look into applying the same builder disk increase to staging that worked for your preview.
Status changed to Awaiting User Response Railway • 2 days ago
2 days ago
same issue.
Status changed to Awaiting Railway Response Railway • 1 day ago
sam-a
Yesterday’s disk increase applied only to the preview, so staging hasn’t received it. Your build installs dependencies across the monorepo, even though it only builds the portal. Try setting `RAILPACK_PRUNE_DEPS=true` in a preview environment and redeploying. This removes development dependencies before packaging, so first check that Next.js and anything needed to run the portal are listed under dependencies, then test that the app starts and works correctly. (I probably should have suggested this yesterday in the first place. Sorry!) Let us know if that doesn't work and we can look into applying the same builder disk increase to staging that worked for your preview.
2 days ago
Sam I now have this issue all day today. 4 days ago was fine! How can i increase mine too. What do I need to do?
rossman22590
Sam I now have this issue all day today. 4 days ago was fine! How can i increase mine too. What do I need to do?
2 days ago
I would love some help.
rossman22590
Sam I now have this issue all day today. 4 days ago was fine! How can i increase mine too. What do I need to do?
2 days ago
This is very frustrating, we cannot push changes to users.
2 days ago
Sorry for the delay. We increased your build disk size to 64GB, up from the standard 32GB.
Status changed to Awaiting User Response Railway • 1 day ago
