-
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
There is no option to set ulimit while using podman kube play #16404
Comments
Thanks for reaching out! This is working in more recent versions of Podman:
See the memory: 10Mi? |
Ah, apologies, the ulimits are not added yet. |
Oh, thanks for confirming this, I didn't test with version |
Interested in opening a PR? |
Can you specify a ulimit within a kubernetes.yaml file? |
Perhaps the solution would be for us to add --ulimit to |
podman pod create should probably have a ulimit as well. |
@cdoern PTAL |
Q1: Q2: Q3: Perhaps the solution would be for us to add --ulimit to podman kube play command? |
@cdoern or @umohnani8 Care to take a stab at Option 3? |
Sure @rhatdan I'll try it this week |
Another option would be to use annotations to define the intended limits. |
@fpoirotte , But that would only export/import the annotation, which can express the intention, but will not actually change container's limit, right? so I don't see how it would help |
podman could parse the annotations when reading the manifest in This would allow for self-contained manifests (instead of having part of the configuration in the manifest, and the rest as command-line options to |
We already do some of this with annotations now. man podman-kube-play
|
A friendly reminder that this issue had no activity for 30 days. |
However I would still need a fix to this problem. I'm hoping that when @cdoern has some updates, he'll let us know 🤞 . Thank you ! |
I will get started on this next week. |
A friendly reminder that this issue had no activity for 30 days. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
I would like to revive this issue from the redhat bugzilla tracker: https://bugzilla.redhat.com/show_bug.cgi?id=1950183 . I'm facing a similar issue.
This is my context (machine setup) - And to be honest, it'll be hard to upgrade the entire OS just for a patch on podman(but that's another story) - I hope that at least this will be fixed in a latest version for newer environments:
This is my problem. The ulimits are not exported - I understand that podman doesn't want to introduce support for anything that is not in the k8s standard specs. But there is also no other way to apply ulimits to containers created through
kube play
. A command line parameter would be nice, or any option, really.Steps to reproduce the issue:
podman run -d --name=ulimit_test --ulimit nofile=1231:3123 alpine:3.16.2 sleep infinity
podman exec -it ulimit_test /bin/sh -c "ulimit -Sn ; ulimit -Hn"
observe values 1231 and 3123podman generate kube -s ulimit_test -f ulimit_test.yml
podman stop -t0 ulimit_test && podman rm ulimit_test
podman play kube ulimit_test.yml
podman exec -it ulimittest /bin/sh -c "ulimit -Sn ; ulimit -Hn"
observe different values than beforeDescribe the results you received:
After exporting and re-importing the container, the ulimits are different. 1231:3123 versus 1024:1024
Describe the results you expected:
I was hoping to be able to keep the original ulimits, even though the container definition was exported and re-imported. Or at least have an option that would allow me to set ulimits at
play
time, appending the--ulimit
flag to podman, besides what's in the yml definition file.Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
No
I've only checked https://docs.podman.io/en/latest/markdown/podman-kube-play.1.html and couldn't see an option/support for ulimits.
Additional environment details (AWS, VirtualBox, physical, etc.):
Physical machine, environment details are above.
Thank you ! You're doing an awesome job !
The text was updated successfully, but these errors were encountered: