-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
linux, rootless: clamp oom_score_adj if it is too low #19843
linux, rootless: clamp oom_score_adj if it is too low #19843
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM
Can you add a note to the docs as well?
c4999fd
to
91d5e01
Compare
sure, added a note to the docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@containers/podman-maintainers PTAL
91d5e01
to
abad970
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/hold
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc, giuseppe, vrothberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
when running rootless, if the specified oom_score_adj for the container process is lower than the current value, clamp it to the current value and print a warning. Closes: containers#19829 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
abad970
to
8b4a79a
Compare
needs again the lgtm label |
/lgtm |
Late comment but doesn't this run into the same problem similar to #18721? You know set the limit on container creation permanently. Which means a long living container cannot be started if the oom_score_adj limit for the current user is set higher. |
That is a good idea, taking a look right now |
Maybe not the right place to ask, but could you push a new 4.6.3 patch release with this fix? |
when running rootless, if the specified oom_score_adj for the container process is lower than the current value, clamp it to the current value and print a warning.
Closes: #19829
Does this PR introduce a user-facing change?