fix: configure log source for podman events
#47
Merged
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
When we switched the log driver from `journald` to `k8s-file` due to podman being unable to log to the system journal, it broke the events command since it defaults to searching the journal for log entries. This commit changes the `events_logger` configuration so it searches for events in the correct place.
mirkobrombin
approved these changes
May 27, 2024
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.
When we switched the log driver from
journaldtok8s-filedue to podman being unable to log to the system journal, it broke the events command since it defaults to searching the journal for log entries.This commit changes the
events_loggerconfiguration so it searches for events in the correct place.podman eventsused by apx-gui for monitoring changes to the subsystems.