# Docker logging change: review and acceptance

Life Linked Lab | practical checklist | 2026-11-07

Blank manual checklist, not an observed result or migration script.
Guide: https://lab.life-linked.com/articles/docker-log-rotation-existing-containers/

## Identify the source before a change

- [ ] Record the affected filesystem, free space and inode use.
- [ ] Record Docker context, Engine version and default logging driver.
- [ ] Inspect the selected container's HostConfig.LogConfig, ID and Created time.
- [ ] Separate stdout/stderr logs from application files, volumes and images.
- [ ] Record current log-shipping compatibility and retention obligations.

## Prepare one service

- [ ] Select local OR bounded json-file for the actual collector requirements.
- [ ] Pick max-size/max-file from observed growth and needed history.
- [ ] Merge the logging fragment into the correct existing service.
- [ ] Validate the real merged Compose configuration with config --quiet.
- [ ] Keep rendered configuration private; interpolation can reveal secrets.
- [ ] Confirm data persistence, dependencies, maintenance window and rollback.
- [ ] Preserve required evidence before recreating a container.

The daemon JSON is an example of settings to merge, NOT a replacement for an
existing daemon.json. It requires a reviewed daemon change and applies to newly
created containers. This worksheet does not restart Docker or any service.

## After a reviewed recreation

- [ ] Compare the container ID and Created time with the previous record.
- [ ] Inspect the selected container's effective driver and options again.
- [ ] Check service health and intended persistent data.
- [ ] Generate a small known application message; check docker logs and collector.
- [ ] Rehearse rotation in a disposable environment before relying on retention.
- [ ] Record file-count/history behavior, errors and unresolved work.

Container / owner / environment:
Previous ID / created / logging configuration:
New ID / created / logging configuration:
Application and collector checks:
Rotation rehearsal evidence / NOT RUN reason:
Remaining work / next action:

Do not edit or truncate Docker-managed log files. Driver rotation does not cap
application files, volumes, images or all host storage. A successful config
parse is not proof of runtime rotation, retained history or data recovery.