Ensure podman copes with a hard reboot #460
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
sjpb
force-pushed
the
fix/podman-hard-reboot
branch
from
f7a0e93 to
c7954d4
Compare
|
Tested on RL9: without this PR hard reboot fails with described problem, with it problem is fixed. |
jovial
approved these changes
Oct 23, 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.
This PR fixes podman containers failing to start after a hard reboot, with an error "invalid internal status" in the journal for the unit.
Note that originally the podman role ensured the podman temporary directories were on a tmpfs; this appeared to be problematic with later podman and #351 removed this.
Fixes #459.