Build failure: no space left on device on elegant-vitality service
deibyd07
HOBBYOP

a month ago

Service: elegant-vitality

Problem: Build error: not enough space on the device.

Deployment ID: d85f9743-4b57-49ce-bb1f-aa9e9e493918

Commit: a09499952dbddb8024d553b22690af5ecd34301c

Error: ResourceExhausted: Error reading the Dockerfile: Error creating the tenancy:

Write /var/lib/buildkit/runc-overlayfs/containerdmeta.db: not enough space on the device

The service has failed multiple times due to insufficient space on the build machine.

Infrastructure intervention is required.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 28 days ago


Hey there,

We had a builder disk pressure issue across our V3 fleet (us-west1 region) following the post-outage recovery on May 20. The build queue is fully healthy again now; end-to-end deploys across the platform are completing in under a minute.

I just kicked a fresh redeploy on your service from my side. It should land on a clean builder.

If you're still hitting the same "no space left on device" error after this, reply with the latest deployment ID and I'll route it for direct attention.

Sorry for the disruption,

Angelo


Status changed to Awaiting User Response Railway 28 days ago


Status changed to Solved Railway 21 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...