-
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
change in ulimit -u
causes existing containers to not start
#18714
Comments
Some updates. Couldn't reproduce this issue running podman inside a container. So that made my debugging a little more difficult on Silverblue (had to resort to some print debugging ...). Thus far I have tracked the issue down to this line: podman/pkg/specgen/generate/oci.go Line 24 in e7dc507
In the container (where the issue does not occur), len(s.Rlimits) is 0 and s.Rlimits is nil. On the host (where the issue occurs) len(s.Rlimits) is also 0 but s.Rlimits is not nil. Changing this line to:
fixes the issue. Still investigating if something preceding this is the root-cause. |
The above fix does not work for the rootfull setup on my host. |
I've identified some more things in the ulimit handling that I think needs some cleaning up. WIP fix is at: https://github.com/Cydox/podman/tree/fix-ulimit |
This seems to be a duplicate of #18696 |
Issue Description
Similar to #18555 but without using kube.
Updating my computer from Fedora Silverblue 38.20230526.0 to 38.20230527.0 slightly decreased the value output by
ulimit -u
from 63329 to 63304. This caused existing containers to not launch with the error:The containers never had a ulimit set manually on the command line, however looking at the output of
podman inspect
the ulimit value did get saved into the config causing a subsequent decrease in ulimit to break the containers.Steps to reproduce the issue
Not a full reproduction as I'm not sure how to easily decrease the value of
ulimit -u
for your system, but just demonstrating that without using--ulimit
a value does get saved into the config:podman create test docker.io/alpine:3.18
podman inspect test
Describe the results you received
Output includes:
Describe the results you expected
Output includes:
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: