Repository navigation
Bound Docker container logs in all deployment templates #13
Description
The 2.0 all-in-one and split Compose templates omit a per-service logging policy. With Docker’s default json-file driver and no daemon rotation override, container stdout/stderr logs can grow indefinitely. Rotating Caddy’s access.json does not bound these Docker log files.
Reproduction: start either supplied template on a default Docker daemon, then inspect a service with docker inspect --format '{{json .HostConfig.LogConfig}}' <container>. The driver is json-file and its options have no max-size or max-file.
Requested change: supply a bounded policy for every app, web, proxy, database and cache service in both deployment types, and document that existing containers need a planned recreation to adopt it. Preserve data volumes. A proposed 10 MB × 3 policy is prepared on the experimental docs branch; all 11 services in the three templates parse with that policy.
This is deployment hardening, not a claim that the current live host is out of space. No production configuration has been changed. Experimental work remains draft, with no review request.
Activity
n30nex commentedon Oct 23, 2026
The current core/roadmap docs PR #43 now adds the bounded
json-filepolicy to every service in all three deployment templates: 11 services,max-size: "10m",max-file: "3".I parsed both versions and compared their resolved structures with logging removed; images, volumes, ports, environment and dependencies are unchanged. The roadmap also states that existing containers need a planned recreation to adopt the policy, and that this does not bound separate Caddy access logs, database/WAL files or backups. No live container was recreated for this change.
Keep this issue open until the docs change is accepted and any desired runtime rollout is separately verified.