Docker / Images, Dockerfiles & Build Reliability
Inspect BuildKit cache usage before performing cleanup
Build cache can consume substantial storage separately from running container data. Inventory it before choosing a retention action.
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 buildx duRead the result
For the selected supported builder, this reports cache usage and reclaimability metadata. It does not authorize deleting caches used by other jobs or describe all Engine storage.
Resolve and verify
Compare cache growth with build concurrency and host or builder capacity. Plan scoped retention through the build owner and verify active pipelines remain unaffected.
Before changing production
Do not run broad prune commands during another build or assume cache cleanup recovers database volume capacity.