How to fix Disk quota exceeded in Docker

DockerINTERMEDIATEHIGH

This error occurs when Docker operations fail due to disk space limitations, inode exhaustion, or kernel keyring limits. The fix involves pruning unused Docker resources, increasing disk space or inodes, and adjusting kernel parameters.

What this error means

The "Disk quota exceeded" error in Docker can stem from several different causes, making it one of the more confusing errors to troubleshoot. While the message suggests you've run out of disk space, the actual cause is often not related to disk space at all. The most common causes are: 1. **Kernel keyring exhaustion**: The Linux kernel maintains a keyring for session keys. Docker creates a unique session key for each container, and the default limit is relatively low. When this limit is reached, new containers cannot start and report "disk quota exceeded" even though the filesystem has plenty of space. 2. **Actual disk space exhaustion**: Docker images, containers, volumes, and build cache can consume significant disk space over time. Dangling images, stopped containers, and unused volumes accumulate and eventually fill the disk. 3. **Inode exhaustion**: On some filesystems (especially in VPS environments), you can run out of inodes before running out of disk space. Each file and directory consumes one inode, and Docker creates many small files. 4. **Storage driver quotas**: Some Docker storage backends (devicemapper, ZFS, btrfs) support per-container disk quotas that may be exceeded. Understanding which cause applies to your situation is the first step in resolving this error.

How to fix "Disk quota exceeded"

1Check available disk space and inodes

First, determine whether this is actually a disk space issue:

bash

# Check disk space
df -h

# Check inode usage (often overlooked!)
df -i

If disk space shows plenty of room but inodes are at 100%, you've hit inode exhaustion. If both show available space, the issue is likely the kernel keyring limit.

Check Docker's own disk usage:

bash

docker system df

This shows space used by images, containers, volumes, and build cache.

2Fix kernel keyring limit (most common cause)

If disk space and inodes look fine, the issue is likely the kernel keyring limit. This is especially common when running Docker inside LXC containers or after creating/destroying many containers.

Check current keyring usage:

bash

cat /proc/sys/kernel/keys/maxkeys
cat /proc/sys/kernel/keys/maxbytes

Increase the limits temporarily:

bash

# Run on the HOST (not inside a container)
echo 200000 | sudo tee /proc/sys/kernel/keys/maxkeys
echo 25000000 | sudo tee /proc/sys/kernel/keys/maxbytes

Make the change permanent by adding to /etc/sysctl.conf:

bash

sudo tee -a /etc/sysctl.conf << EOF
kernel.keys.maxkeys = 200000
kernel.keys.maxbytes = 25000000
EOF

sudo sysctl -p

Note: If you're running Docker inside LXC/LXD, you must change these settings on the LXC host, not inside the container.

3Prune unused Docker resources

Clean up unused Docker objects to free disk space:

bash

# Remove all stopped containers
docker container prune -f

# Remove unused images (not just dangling)
docker image prune -a -f

# Remove unused volumes (WARNING: may delete data!)
docker volume prune -f

# Remove build cache
docker builder prune -f

# Nuclear option: remove EVERYTHING unused
docker system prune -a --volumes -f

To see what would be removed before actually removing:

bash

docker system prune -a --volumes  # without -f, shows confirmation

Warning: docker volume prune will delete data in unnamed volumes. Make sure you don't need any data before running it.

4Clean up container logs

Container logs can grow very large and consume significant disk space:

bash

# Find large log files
sudo find /var/lib/docker/containers -name "*.log" -size +100M

# Truncate a specific container's log
sudo truncate -s 0 /var/lib/docker/containers/<container_id>/<container_id>-json.log

Configure log rotation in your Docker daemon (/etc/docker/daemon.json):

json

{
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "10m",
    "max-file": "3"
  }
}

Then restart Docker:

bash

sudo systemctl restart docker

For individual containers, set log limits at runtime:

bash

docker run --log-opt max-size=10m --log-opt max-file=3 myimage

5Address inode exhaustion

If df -i shows high inode usage, you need to find and remove files:

bash

# Find directories with many files
sudo find /var/lib/docker -xdev -type d -exec sh -c 'echo "$(find "{}" -maxdepth 1 | wc -l) {}"' \; | sort -rn | head -20

Common culprits:
- Old container layers in /var/lib/docker/overlay2
- Small temporary files created by applications
- Package manager caches inside images

For VPS environments, you may need to contact your provider to increase inode allocation or recreate the VPS with better inode settings.

As a workaround, move Docker's data directory to a partition with more inodes:

bash

# Stop Docker
sudo systemctl stop docker

# Move Docker data
sudo mv /var/lib/docker /mnt/larger-partition/docker
sudo ln -s /mnt/larger-partition/docker /var/lib/docker

# Start Docker
sudo systemctl start docker

6Configure storage driver quotas

If you need per-container disk quotas, configure them in the storage driver:

For overlay2 with XFS (requires project quota support):

bash

# Mount XFS with project quota
sudo mount -o pquota /dev/sda1 /var/lib/docker

# Set default container size in daemon.json
{
  "storage-driver": "overlay2",
  "storage-opts": [
    "overlay2.size=10G"
  ]
}

For devicemapper:

json

{
  "storage-driver": "devicemapper",
  "storage-opts": [
    "dm.basesize=20G"
  ]
}

At container runtime:

bash

docker run --storage-opt size=5G myimage

Note: Not all storage drivers support runtime size limits.

7Set up automatic cleanup

Prevent future disk quota issues by scheduling regular cleanup:

Using cron:

bash

# Add to crontab (crontab -e)
0 2 * * * docker system prune -f --filter "until=168h" > /dev/null 2>&1

This removes unused resources older than 7 days every night at 2 AM.

Using systemd timer:

bash

# /etc/systemd/system/docker-cleanup.service
[Unit]
Description=Docker cleanup

[Service]
Type=oneshot
ExecStart=/usr/bin/docker system prune -f --filter "until=168h"

# /etc/systemd/system/docker-cleanup.timer
[Unit]
Description=Run Docker cleanup weekly

[Timer]
OnCalendar=weekly
Persistent=true

[Install]
WantedBy=timers.target

Enable with:

bash

sudo systemctl enable --now docker-cleanup.timer

Monitor disk usage: Set up alerts when Docker disk usage exceeds a threshold to catch issues before they cause failures.

How to fix Disk quota exceeded in Docker

What this error means

Typical symptoms

Common causes

How to fix "Disk quota exceeded"

Advanced notes

Related errors

Official resources & further reading