a month ago
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 >
The build failed because the assigned builder node ran out of disk space on its internal metadata database before it could even read the Dockerfile. The same commit has already built and deployed successfully on a different builder node, confirming this is a transient infrastructure issue.
1 Replies
a month ago
Your assessment is correct, this was a transient builder-node issue. We can see your production deployment is currently building again, and your staging deployment is already in the deploying phase, so things appear to be progressing. If a build fails due to a builder issue like this, retriggering the deployment is the right move as it will typically land on a healthy node.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved Railway • about 1 month ago