Use journald log driver, update DEPLOY docs on logging #512
Conversation
This file contains 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
humphd
added
the
category: deployment
Eakam1007
approved these changes
Apr 4, 2023
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.
Fixes #117
This switches Docker to use the
journaldlog driver instead of the defaultjson-filelog driver, see https://docs.docker.com/config/containers/logging/journald/. Doing so means that the OS (RHEL8) will take care of our log files/rotation for us.I've also updated the docs to show how to use this. You can get logs via
dockerorjournalctl.This is running on staging, where I've confirmed that it's working. In order to check both Redis and MyCustomDomain, I had to recreate the containers. Updating Redis to a new version is the easiest way, and also takes care of doing the update at the same time.