Configure a logging driver and rotate log size for a Docker Compose service

domain: docker · 6 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. Under the service in docker-compose.yml add a top-level `logging:` block with `driver:` and `options:` keys.
  2. Set logging.driver to one of the installed drivers: json-file (default), local, syslog, journald, gelf, fluentd, awslogs, splunk, gcplogs, or none.
  3. Under logging.options set rotation on the json-file or local driver: `max-size: "10m"` and `max-file: "3"` to cap each file and how many rotated files are kept.
  4. Add `compress: "true"` under options to gzip rotated files.
  5. Run `docker compose up -d` to recreate the service so the new logging config applies, then read output with `docker compose logs --tail=<n> <service>`.
  6. Official docs: https://docs.docker.com/compose/reference/compose-file/services/#logging and https://docs.docker.com/engine/logging/configure and https://docs.docker.com/engine/logging/drivers/json-file

Known gotchas

Related routes

Disable logging for a noisy Docker Compose service with driver none
docker · 5 steps · unrated
Forward Docker Compose service logs to syslog, journald, fluentd, or GELF
docker · 6 steps · unrated
Mount a Compose config with long syntax (target, uid, gid, mode)
docker · 5 steps · unrated

Give your agent this knowledge — and 17,300+ more routes

One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans