Docker / Volumes, Filesystems & Recovery
Explain why a Docker daemon logging-default change missed existing containers
Default logging configuration normally applies when containers are created, not as a guaranteed live rewrite of every existing container.
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}}' appRead the result
The inspected configuration records this container's selected driver and options. Daemon defaults and explicit deployment overrides can differ.
Resolve and verify
Compare actual container settings with the reviewed retention policy. Roll out replacements safely where required and validate log delivery and bounded growth.
Before changing production
Do not assume changing daemon defaults retroactively fixed every workload or recreate stateful containers without a data plan.