Fix rootless Podman logging and enforce runner-specific configuration #21
Conversation
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
gabrielpetry
changed the title
gabrielpetry
changed the title
gabrielpetry
changed the title
debdutdeb
reviewed
Feb 1, 2026
debdutdeb
reviewed
Feb 1, 2026
debdutdeb
reviewed
Feb 1, 2026
debdutdeb
approved these changes
Feb 9, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR addresses permission issues encountered when using the journalctl logger with rootless Podman. The system has been updated to force file logging instead of the default journald.
Key Changes
Important Usage Note
For this setup to work correctly, users must now explicitly include the configuration file relevant to their runner in the command pipeline. The configurations are no longer shareable.
For Podman: ... -f podman.yml ...
For Docker: ... -f docker.yml ...