-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
podman-2.0.2: --pids-limit value out of range #6908
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
Something related to c4023a9? |
Confirmed. Only happens on the v2.0 branch, not master. |
Fix in #6910 |
mheon
added a commit
to mheon/libpod
that referenced
this issue
Jul 15, 2020
The --pids-limit flag was using strconv.ParseInt with bad arguments, resulting in it being unable to parse standard integers (1024, for example, would produce an 'out of range' error). Change the arguments to make sense (base 10, max 32-bit) and add a test to ensure we don't regress again. Fixes containers#6908 Signed-off-by: Matthew Heon <[email protected]>
@rhatdan please close this issue |
Closing as the PR addressing this has merged: #6910 |
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 23, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I added
--pids-limit 1024
to my default launch scripts for runningpodman
(after nearly accidentally fork-bombing my host!) at aboutpodman-1.9.3
, and this has been accepted (... and, I assume, applied?) ever since...However, with
podman-2.0.2
suddenly I'm getting:... as
podman
's sole output.I've tried various different values, and it turns out that values from
0
to511
are accepted, but values512
and above result in the above error. I've confirmed that this is the--pids-limit
parameter causing this issue.A value of 1024 seems sane for a root-run container, and has always been accepted up to and including
podman-2.0.1
- has this always been silently ignored, or is there a problem introduced withpodman-2.0.2
?(Is there some
sysctl
tunable or otherwise which limits the default number of available PIDs which wasn't previously being checked?)Output of
podman version
:Output of
podman info --debug
:The text was updated successfully, but these errors were encountered: