a month 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 >
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month 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 • about 1 month 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.
a month ago
After 15 tries, the build and deploy succeeded.
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved gnazaryan • about 1 month ago