Repository navigation
chore(docker): cap the container log size of every production service - #310
Merged
Merged
Conversation
…uction-container-log-size # Conflicts: # src/production/cloudflared/compose.yaml # src/production/postgraphile/compose.yaml # src/production/vibetype/compose.yaml
…ainer-log-size' into chore/docker/cap-production-container-log-size
dargmuesli
enabled auto-merge (squash)
October 21, 2026 03:56
dargmuesli
added a commit
that referenced
this pull request
Oct 21, 2026
maevsi-bot
pushed a commit
that referenced
this pull request
Oct 21, 2026
## [21.2.8](21.2.7...21.2.8) (2026-10-21) ### Bug Fixes * **docker:** cap the container log size of every production service ([#310](#310)) ([c01ac6d](c01ac6d))
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.
No production container declared a log size cap, so the json-file driver grows each container's logs without bound. This adds a json-file cap of 20 MB per file and 3 files to every long-running production service, bounding container logs at about 60 MB per service. One-shot job services and the development-only minio are left uncapped.