a month ago
Build Failed: build daemon returned an error < failed to solve: ResourceExhausted: failed to prepare sha256:599856979135ac0f66340250a329b0f6bb3b0c9101feaaec7c6c487d2624a360 as z8i1zjsk9uaw8hu9jnmo1tq47: failed to create prepare snapshot dir: failed to create temp dir: mkdir /var/lib/buildkit/runc-overlayfs/snapshots/snapshots/new-2422144076: no space left on device >
14 Replies
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
I am also newly getting this error. I think it's a problem on the host side - sometimes the deploy works, and sometimes it errors with the disk space problem
mcintoshjames-sketch
I am also newly getting this error. I think it's a problem on the host side - sometimes the deploy works, and sometimes it errors with the disk space problem
a month ago
I agree, same issue has been happening for me.
a month ago
I've been getting no space left on device failures the past few hours. Im trying to deploy a commit that is currently sucessfully deployed. Likely host side issue, no?
a month ago
same here ...
a month ago
Please help me : Erreur : no space left on device
a month ago
same here
a month ago
Weird part is it's out of space just to create a directory? How much space does that take up in the FAT, 50 bytes?
a month ago
i dont have docker use railrack any till now wark fine same deplayment work in develop ...
a month ago
same here
a month ago
I am running into this too. This just let my project deploy: https://station.railway.com/questions/persistent-no-space-left-on-device-on-da0502e9#md6n
a month ago
Yah. Me too.
I suspect it's likely overloaded build machines sharing disk under GCP outage recovery. Nothing wrong with your code.
Wait for Railway to stabilize, retry deploy.
a month ago
I think it's working now again! At least here worked when I've tried.
a month ago
For the specific out-of-space error: from yesterday's incident, GCP brought our builders back up in an incorrect state.
We have since fixed that. Please cancel and retry any builds where needed.
Status changed to Solved Railway • about 1 month ago