Build failing on this error
iwatlasproject
PROOP

a month ago

Build Failed: build daemon returned an error < failed to solve: ResourceExhausted: failed to read dockerfile: failed to create dir /var/lib/buildkit/runc-overlayfs/snapshots/snapshots/34011/fs/apps/api: mkdir /var/lib/buildkit/runc-overlayfs/snapshots/snapshots/34011/fs/apps/api: no space left on device >

Solved

3 Replies

Railway
BOT

a month ago

The "build daemon returned an error" is a transient build infrastructure error, not an issue with your code. Your other services are deploying successfully, so please try redeploying this service and let us know if the error persists.


Status changed to Awaiting User Response Railway about 1 month ago


iwatlasproject
PROOP

a month ago

Still persisting


Status changed to Awaiting Railway Response Railway about 1 month ago


sam-a
EMPLOYEE

a month ago

Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.

It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.

You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY

If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c

Feel free to respond if your question has not been addressed.


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 about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...