Affected versions: 20.04 LTS

πŸ“– ~1 min read

Table of contents
  1. Symptom & Impact
  2. Environment & Reproduction
  3. Root Cause Analysis
  4. Quick Triage
  5. Step-by-Step Diagnosis
  6. Solution – Primary Fix
  7. Solution – Alternative Approaches
  8. Verification & Acceptance Criteria
  9. Rollback Plan
  10. Prevention & Hardening
  11. Related Errors & Cross-Refs
  12. References & Further Reading

Symptom & Impact

Root filesystem reaches 100 percent usage, causing write failures, service crashes, and inability to install updates or create logs.

Environment & Reproduction

Common on CI runners and app hosts with frequent image builds where old layers and stopped containers accumulate.

Root Cause Analysis

Unpruned Docker images, dangling volumes, and build cache growth consume space faster than retention policies reclaim it.

Quick Triage

Identify largest mount points and confirm Docker data directories dominate usage before deleting files outside managed runtime paths.

Step-by-Step Diagnosis

Run docker system df, inspect overlay2 and volume directories, and map growth to deployment workflows.

Illustrative mockup for ubuntu-20-04-lts β€” docker_disk_full_problem
Overlay2 growth consuming root filesystem β€” Illustrative mockup β€” Progressive Robot

Solution – Primary Fix

Remove unused images, containers, and caches with controlled prune commands, then enforce explicit retention policies in pipelines.

Still having issues? Our Server Management team can diagnose and resolve this for you. Get in touch for a free consultation.

Illustrative mockup for ubuntu-20-04-lts β€” docker_prune_fix
Safe cleanup reclaiming disk space β€” Illustrative mockup β€” Progressive Robot

Solution – Alternative Approaches

Move Docker data root to larger storage, split build workers, or adopt registry-side layer management to reduce local accumulation.

Verification & Acceptance Criteria

Disk usage must return below warning thresholds and remain stable through normal deployment cycles without unexpected growth spikes.

Rollback Plan

Restore critical images from registry backups if aggressive cleanup removed required artifacts for offline or pinned workloads.

Prevention & Hardening

Schedule periodic cleanup jobs, set quotas where possible, and monitor layer growth with alerting tuned to workload profiles.

Associated issues include journal growth, apt cache bloat, and inode exhaustion addressed in storage maintenance tutorials.

Related tutorial: View the step-by-step tutorial for Ubuntu 20.04 LTS.

View all Ubuntu 20.04 LTS tutorials on the Tutorials Hub β†’

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Review Docker disk usage documentation, Ubuntu filesystem operations references, and SRE patterns for host-level storage governance.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today β€” we respond within one business day.