11 days ago
internal
load build definition from backend/Dockerfile
0ms
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 >
^ getting following error
6 Replies
11 days 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 • 11 days ago
11 days ago
CLI command > railway variable set NIXPACKS_NO_CACHE=1 remove cache or railway variable set RAILPACK_NO_CACHE=1
systemkarislabs
CLI command > railway variable set NIXPACKS_NO_CACHE=1 remove cache or railway variable set RAILPACK_NO_CACHE=1
11 days ago
nope that doesn't solve it
Attachments
11 days ago
The error no space left on device on /var/lib/buildkit/runc-overlayfs/containerdmeta.db means the build machine's disk is full — it's a Railway infrastructure-level issue, not something in your code or Dockerfile.
A few things to try:
-
Retry the deployment — Railway periodically recycles build machines, so a fresh retry may land on a builder with available disk space.
-
Disable the build cache — Set the environment variable
NIXPACKS_NO_CACHE=1(orRAILPACK_NO_CACHE=1if you're using Railpack) to prevent the builder from writing large cache layers. You can do this via the Railway dashboard under your service's Variables, or via CLI:railway variables set NIXPACKS_NO_CACHE=1This reduces the disk footprint during the build.
-
Check for unnecessarily large build artifacts — If your Dockerfile copies in large files or has many layers, consider using a multi-stage build so intermediate artifacts are discarded and don't fill the overlay filesystem.
Note: Given that Railway is currently experiencing a build incident (as noted in the banner), the build machines may be under higher-than-normal load and disk pressure. Waiting a short while and retrying may resolve it on its own once the incident is fully resolved.
suryalim11
The error `no space left on device` on `/var/lib/buildkit/runc-overlayfs/containerdmeta.db` means the build machine's disk is full — it's a Railway infrastructure-level issue, not something in your code or Dockerfile. A few things to try: 1. **Retry the deployment** — Railway periodically recycles build machines, so a fresh retry may land on a builder with available disk space. 2. **Disable the build cache** — Set the environment variable `NIXPACKS_NO_CACHE=1` (or `RAILPACK_NO_CACHE=1` if you're using Railpack) to prevent the builder from writing large cache layers. You can do this via the Railway dashboard under your service's Variables, or via CLI: ``` railway variables set NIXPACKS_NO_CACHE=1 ``` This reduces the disk footprint during the build. 3. **Check for unnecessarily large build artifacts** — If your Dockerfile copies in large files or has many layers, consider using a multi-stage build so intermediate artifacts are discarded and don't fill the overlay filesystem. Note: Given that Railway is currently experiencing a build incident (as noted in the banner), the build machines may be under higher-than-normal load and disk pressure. Waiting a short while and retrying may resolve it on its own once the incident is fully resolved.
11 days ago
no setting the no_cache var doesn't work either
kacesensitive
no setting the no_cache var doesn't work either
11 days ago
The BuildKit daemon ran out of space writing to /var/lib/buildkit/runc-overlayfs/containerdmeta.db. Running docker system prune -a should resolve it immediately in most cases
Clean up Docker resources (most effective)
Remove all unused containers, networks, images, and build cache
docker system prune -a
If you also want to remove volumes
system prune -a --volumes
- Check disk usage first
bash
df -h
docker system df
- More targeted cleanup
bash#
Remove stopped containers
docker container prune
Remove unused images
image prune -a
Remove build cache specifically
docker builder prune -a
If disk is still full
Find large files/directories
du -sh /* 2>/dev/null | sort -rh | head -20
Check Docker's storage directory specifically
du -sh /var/lib/docker/*
if this helps please reply and mark as solved
cheers
11 days ago
The error "no space left on the device" should be fixed now on railway. Caused From yesterday's major Railway incident. Redeploy should make it work.