-
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
Pod level cgroup resource limits are not assigned to containers by default in Quadlet #23664
Comments
@giuseppe PTAL |
|
The problem is that Quadlet implicitly set Another problem is that Quadlet does not have a specific key ( |
Care to open a PR to fix documentation or allow for CGroups= flag? Not sure if we want to allow anything but --cgroups=split, though. I would leave this up to @giuseppe @mheon @alexlarsson @ygalblum |
I wonder if we can get pod-level limits working with |
Ah, Giuseppe already indicated no. Hm. Maybe containers in a pod should default to non-split even for Quadlet? |
I think |
We can probably pop up a warning in the logs if Cgroups=split is used on a pod with resource limits set, give people some breadcrumbs to figure out what is going wrong. |
A friendly reminder that this issue had no activity for 30 days. |
I suspect my issue is related #24130. I've been tracking down a Rootless NFS volume permissions issue on the stable branch (v4.9.4 as of writing), and the key difference between Quadlet's non-functional unit file vs EDIT: Further testing points my permissions issues elsewhere. |
Issue Description
Containers created by Quadlet implicitly use
--cgroups=split
, which ignores pod level cgroup resource limits if they join a pod.Steps to reproduce the issue
Create a Quadlet
.pod
file with cgroup resource limits:Create a Quadlet
.container
file which joins the pod:Start the container (or pod):
$ systemctl start --user child.service
Describe the results you received
The container and the pod belong to different cgroups:
The
cpu
controller is set for the pod:But is not set for the container:
Describe the results you expected
In CLI, with
--cgroups=enabled
(which is the default) or--cgroups=no-conmon
, the cgroup of the container is inside the cgroup of the pod, so that the resource limits can take effect. IMO this is the expected behavior.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
None
Additional information
None
The text was updated successfully, but these errors were encountered: