[WIP] Set container oom killed state correctly #17756
Closed
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.
Parse the oom file created by conmon when a container is oomkilled and set the oomkilled value to true in the container state. conmon writes the oom file in a persist directory that podman checks now for any oom files for a given container.
Partially fixes #13102
Signed-off-by: Urvashi Mohnani [email protected]
Does this PR introduce a user-facing change?