-
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
cgroupsv1(?): cannot toggle freezer: cgroups not configured for container #11785
Comments
I think we should not allow the combination If there is no usable cgroup, as it is the case of rootless on cgroup v1, then it is impossible to know what processes a container is running since it has no pid namespace. |
my suggestion is to skip this test for rootless on cgroup v1 |
opened #11798 also, the first error is coming from runc. Are you also trying to reproduce with runc? |
I have no idea; I just set cgroups to v1 on f33 (which took me several hours to figure out, because 1minutetip is not normal). I didn't remember about runc/crun. |
I think by default we use crun. You'd need to force runc, with |
Thank you, that explains why I couldn't reproduce. I've removed the |
skip the test "podman selinux: shared context in (some) namespaces" on cgroupsv1 when running as rootless since the tests requires --pid=container:. If the container runtime cannot use cgroupsv1 and the container has no pid namespace. then it is not possible to correctly terminate the container. Without a cgroup or a pid namespace, the runtime has no control on what processes are in the container. Closes: containers#11785 Signed-off-by: Giuseppe Scrivano <[email protected]>
Almost certainly related to #11784, but this one is rootless-only. Seen in f33. This is blocking #11776.
As with #11784, I see hundreds of instances of this in CI logs but cannot reproduce it myself on a cgroupsv1 f33 host. While trying to reproduce it, though, I did get a different error:
The text was updated successfully, but these errors were encountered: