Rotate Gunicorn access logs in Docker Compose - #226
Closed
Michael-C-Strobel wants to merge 1 commit into
Closed
Conversation
Michael-C-Strobel
force-pushed
the
fix/rotate-gunicorn-access-logs
branch
from
August 28, 2026 17:16
0e892b7 to
2df1ba5
Compare
Contributor
Author
|
Closing this as superseded by the logging-only approach. We are preserving the existing access-log behavior and full history, while limiting only Docker JSON stdout/stderr logs in the relevant service repositories. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
copytruncate, avoiding host cron configuration and Docker-socket access.Motivation
The bind-mounted Gunicorn access logs bypass Docker's existing
json-filelimits and currently grow without bounds. On the production host, the web and
API access logs had grown to approximately 10.6 GB and 3.5 GB.
Validation