Docker Core
A write under Docker's storage ran out of filesystem space and failed.
no-space-left-on-deviceReviewed for reference consistency: August 11, 2026
A write under Docker's storage ran out of filesystem space and failed.
What no-space-left-on-device Means
The no-space-left-on-device error on the Docker Core indicates a write under docker's storage ran out of filesystem space and failed.. This typically occurs due to the partition holding the daemon's data root is full.
Images, container layers, volumes, and logs all live under the daemon's data root. When the backing filesystem hits its limit, layer extraction, log writes, and container creation abort with the kernel's no-space text, so the message reports the filesystem condition rather than a Docker-specific fault.
How to fix no-space-left-on-device
General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.
Break down disk usage by Docker category
The verbose df view itemizes images, containers, volumes, and build cache so the pressure maps to a reclaimable bucket.
docker system df -vMeasure the data root's filesystem
The host-level df line for the daemon's data root shows total, used, and free capacity behind every Docker write.
df -h /var/lib/docker
Technical Background
Docker inherits the kernel's space accounting: the error is emitted by the filesystem layer during writes, so the missing resource is disk space, and the daemon is the loudest victim rather than the cause.
The df view splits usage by images, containers, volumes, and build cache, which maps the abstract disk pressure onto concrete reclaimable categories. Log growth is the sneaky contributor because a single container can fill a disk quietly.
Common Causes
- The partition holding the daemon's data root is full
- Unbounded container logs consumed the remaining space
- Build cache and unused images accumulated past the disk's capacity
- A separate volume or partition assigned to a specific path filled independently
Typical Scenarios
- Pulling a multi-gigabyte image onto a small root partition
- A chatty container growing its log file until the disk fills
- Build caches and dangling images accumulating on a CI runner
What to Know
Reclaiming is category-specific: images without containers, exited containers, and build cache are the usual safe orders, while volumes deserve a separate look because they often hold real data.
Frequently Asked Questions
Common questions about Docker no-space-left-on-device error
Removals only free what they own; dangling image layers, build cache, and log files persist until their own cleanup paths run.
Yes. Layer-heavy workloads can exhaust inodes, and the kernel reports the same no-space condition even though capacity shows as free.
Related Error Codes
Related Errors From Other Categories
Similar error codes documented across different platforms and systems
Process Killed — the process was terminated by a SIGKILL signal
Signal 11 (SIGSEGV) — kernel signal for invalid memory reference segmentation fault
Exit Code 139 — process terminated by segmentation fault (Signal 11 / SIGSEGV)
Input/output error EIO — a read or write operation could not complete