I did try redeploying already 10 times, but the issue keeps persisting.
gnazaryan
PROOP

20 days ago

Diagnosis: Infrastructure Error

I did try redeploying already 10 times, but the issue keeps persisting. Try redeploying to get routed to a different builder node. The build failed because the assigned Railway builder ran out of disk space, causing BuildKit to fail instantly before even reading the Dockerfile. This same error has affected all recent deployments on this service.

Build Failed: build daemon returned an error < failed to solve: ResourceExhausted: failed to read dockerfile: failed to create lease: write /var/lib/buildkit/runc-overlayfs/containerdmeta.db: no space left on device >

Solved

2 Replies

Status changed to Awaiting Railway Response Railway 20 days ago


19 days ago

The "no space left on device" error here is fallout from yesterday's incident, where GCP brought our builders back up in an incorrect state. That's been fixed on our end, so canceling and retrying the failed builds should get you unblocked. Sorry for the disruption this caused.


Status changed to Awaiting User Response Railway 19 days ago


brody

The "no space left on device" error here is fallout from yesterday's incident, where GCP brought our builders back up in an incorrect state. That's been fixed on our end, so canceling and retrying the failed builds should get you unblocked. Sorry for the disruption this caused.

gnazaryan
PROOP

19 days ago

After 15 tries, the build and deploy succeeded.


Status changed to Awaiting Railway Response Railway 19 days ago


Status changed to Solved gnazaryan 19 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...