-
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 fails to start containers due to RLIMIT_NPROC being too high #18555
Comments
@giuseppe PTAL |
Found out the issue! Somehow missed this while going over the generated kube yaml:
This line was generated only starting in podman 4.5.0 and somehow had no ill effect on fedora 37, but once I upgraded to fedora 38 I think the system |
has anything changed on your system related to the system memory? I've not seen any change in Fedora 38 related to user limits. What value do you have in
The first value, if not overridden, is approximately
|
My threads-max value is 513272, and my |
This logic was added in 35d16ea, it seems like a bad idea to add defaults when no limits were set on the cli. This makes the yaml much less portable across systems. And at least reading the logic it tried to avoid adding them when they were set to the default but it doesn't seem to work? |
I agree if we are adding these annotations, when they were never set in the first place by the user, that would be bad. |
@umohnani8 Can you change the podman code to only set the Annotation if the user actually set the limit, not if the limit is default. |
Issue Description
I just updated from fedora 37 -> 38, and a few containers that previously worked started breaking, but only ones I created within the last month or so. Here's an example of a kubernetes yaml file for one of the breaking containers:
kube yaml for pihole
When instantiated with
systemctl --user restart podman-kube@$(systemd-escape pihole.yml)
, this creates an image with the followingpodman inspect
output:`podman inspect` output for crashing pihole container
When started, this container fails with the error:
The output of
ulimit -u
is256637
. All containers I've created within the past week or so seem to on this new version of fedora/podman be instantiated withRLIMIT_NPROC
exactly 2 higher than myulimit
.As an example, here's a caddy container I created earlier that has a ulimit that respects the limit of 8000 that I specify in
containers.conf
:`podman inspect` output for caddy container.
This one was also instantiated using
systemctl --user start podman-kube@$(systemd-escape caddy.yml).service
, and it was created using the following yaml:kube yaml for caddy container
I've already done an entire
podman system reset
which did not resolve any of the issues. I'm out of ideas.Steps to reproduce the issue
noted above.
Describe the results you received
Describe the results you received
Describe the results you expected
Describe the results you expected
podman info output
output of `podman info`
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
The text was updated successfully, but these errors were encountered: