Builder out of disk space — need builder rotation
federicoelcovich
HOBBYOP

a month ago

Hi team,

My builds are failing repeatedly with ResourceExhausted: no space left on device on the buildkit snapshots directory. This is a builder-side issue, not a project configuration problem.

Project: renewed-abundance

Service: web

Failed deployment IDs:

6dfa9fdd-2e09-404f-a664-84cafb4a2d5e

0ab47cdb-ce11-4d01-9bb6-85857e04a5a7

46f9855d-ed0a-4321-a5f1-7c854cdcc76c

Error log:

Build Failed: build daemon returned an error < failed to solve: ResourceExhausted: failed to prepare as y9z34akeg0pc2bzy77pfg4233: failed to create prepare snapshot dir: failed to create temp dir: mkdir /var/lib/buildkit/runc-overlayfs/snapshots/snapshots/new-1775083310: no space left on device >

Already tried: NIXPACKS_NO_CACHE=true, multiple redeploy attempts.

Could you please rotate my project to a builder with available disk space?

Context: This service runs a healthcare monitoring system (VitalSync) for real-time patient vitals. Postgres recovered correctly after billing was settled, only the web service is unable to deploy due to the builder issue.

Thanks for your help.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


chandrika
EMPLOYEE

a month ago

Your build failures coincided with a platform-wide builder issue that caused disk pressure on our build machines. That incident is now recovering, and we can see your web service already has a new build in progress. You should not need a manual builder rotation - the underlying issue has been addressed. You can track the incident here: https://status.railway.com/incident/KVZ1Z8GY. If your current build still fails, please try one more redeploy and let us know.


Status changed to Awaiting User Response Railway about 1 month ago


Railway
BOT

a month 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 27 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...