-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Podman v5 Quadlet .pod support for "ShmSize=" parameter #22915
Comments
Thanks for bringing this up. The |
A friendly reminder that this issue had no activity for 30 days. |
@ygalblum I can take a look and add this to |
@Odilhao, thanks for offering. I've assigned the issue to you. LMK if you need any help and/or tag me when you have the PR ready |
This closes containers#22915 Signed-off-by: Odilon Sousa <osousa@redhat.com>
This closes containers#22915 Signed-off-by: Odilon Sousa <osousa@redhat.com>
This closes containers#22915 Signed-off-by: Odilon Sousa <osousa@redhat.com>
This closes containers#22915 Signed-off-by: Odilon Sousa <osousa@redhat.com>
This closes containers#22915 Signed-off-by: Odilon Sousa <osousa@redhat.com>
This closes containers#22915 Signed-off-by: Odilon Sousa <osousa@redhat.com>
Feature request description
Quadlet .container files support the
ShmSize=
option, however when running a container in a Pod, the ShmSize needs to be set at the Pod level.When manually creating a Pod via
pod create -n example-pod -p 1234:1234 --shm-size=1g
this works fine, however when creating a Quadlet .pod file, theShmSize=
option is not available.As a work-around the
PodmanArgs=--shm-size=1g
option seems to be working though.Suggest potential solution
Like on individual .container level, the
ShmSize=
option should also work in .pod files.Have you considered any alternatives?
As a work-around the
PodmanArgs=--shm-size=1g
option seems to be working in a .pod file.Additional context
It is a bit odd that
--shm-size=1g
needs to be set at the Pod level and doesn't work at the container level when running a container in a Pod, but unless this changed in Podman5 it still seems to be true.The text was updated successfully, but these errors were encountered: