Docker / Volumes, Filesystems & Recovery
Locate Docker logging configuration during unexpected host disk growth
Container logs can consume host space outside an application's data volume. Identify the driver and its managed path before cleanup.
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 container inspect --format '{{json .HostConfig.LogConfig}} {{.LogPath}}' appRead the result
The log configuration and path depend on the selected driver and platform. A blank path can be valid for nonlocal drivers.
Resolve and verify
Compare growth with driver retention options and application output volume. Correct supported rotation or centralized collection and plan any required container recreation.
Before changing production
Do not truncate or delete Docker-managed log files manually during active logging without a supported procedure.