Docker / Volumes, Filesystems & Recovery
Separate Docker image, writable-layer, cache and volume disk usage
A full host can involve several storage categories whose sizes overlap or use different accounting. Inventory before choosing a cleanup target.
Environment and inputs: Docker Engine · Compose v2 and Buildx where specified; Linux containers unless noted. Verify daemon context, installed feature support and authorized host or Swarm manager access first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
docker system df -vRead the result
The detailed report summarizes Engine-managed usage and shared content. It does not include every external bind mount, logging path or filesystem allocation behavior.
Resolve and verify
Compare the report with host free space, build-cache and application storage. Plan scoped retention or capacity changes at the correct layer and verify the original write succeeds.
Before changing production
Do not delete files from Docker's data directory manually or assume all reported reclaimable content is approved to remove.