25 days ago
Hello,
Deploy is failing on services related to API: Build Failed: build daemon returned an error < failed to solve: mount source: "overlay", target: "/var/lib/buildkit/runc-overlayfs/cachemounts/buildkit719249019", fstype: overlay, flags: 0, data: "workdir=/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/3/work,upperdir=/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/3/fs,lowerdir=/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/2/fs:/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/1/fs,index=off,redirect_dir=off", err: invalid argument >
(Redeploy the latest commit. If it fails again, contact Railway support. The build stopped with a BuildKit overlay mount error (invalid argument) before any build steps ran, and the same error hit an earlier deployment of this commit.)
On front-end:
[ 2/12] COPY backoffice /usr/share/nginx/html/backoffice
12ms
Build Failed: build daemon returned an error < failed to solve: mount source: "overlay", target: "/var/lib/buildkit/runc-overlayfs/cachemounts/buildkit3869766600", fstype: overlay, flags: 0, data: "workdir=/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/12/work,upperdir=/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/12/fs,lowerdir=/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/11/fs:/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/10/fs:/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/9/fs:/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/8/fs:/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/7/fs:/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/6/fs:/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/5/fs:/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/4/fs,index=off,redirect_dir=off", err: invalid argument >
Could you provide info?
3 Replies
25 days ago
We're sorry for the trouble. These builds run in EU West (Amsterdam), and we're dealing with an ongoing incident, "Slow build snapshot uploads in EU West (Amsterdam)", that can make builds there fail early. The build logs for your API service match that: the build stopped on our builder before any of your own build steps ran, so nothing in your repository or Dockerfile caused it.
The incident is still open while we work with our storage provider to add capacity. You can follow it here: Slow build snapshot uploads in EU West. Your services that are already running are not affected.
Status changed to Awaiting User Response Railway • 25 days ago
Railway
We're sorry for the trouble. These builds run in EU West (Amsterdam), and we're dealing with an ongoing incident, "Slow build snapshot uploads in EU West (Amsterdam)", that can make builds there fail early. The build logs for your API service match that: the build stopped on our builder before any of your own build steps ran, so nothing in your repository or Dockerfile caused it. The incident is still open while we work with our storage provider to add capacity. You can follow it here: [Slow build snapshot uploads in EU West](https://status.railway.com/incident/QORAHHDA). Your services that are already running are not affected.
25 days ago
Hello. The thing is that this error should be solved on redeploy. And, when I do redeploy, the issue persists.
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
A redeploy won't get past this while the Slow build snapshot uploads in EU West incident is still open. These builds fail before any of your build steps run, so they can keep failing early in EU West (Amsterdam) however many times you redeploy.
The incident is still marked as identified, and we're working with our storage provider to add capacity. We can't give you an ETA yet. Your services that are already running are not affected.
Status changed to Awaiting User Response Railway • 25 days ago
18 days 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 • 18 days ago