-
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
[Bug]: podman play kube with disabled cgroup #17436
Comments
I think runc simply has no support for nocgroup feature. cc @giuseppe The test passes under remote because it does not work correctly under remote, https://github.com/containers/podman/blob/eef1b825d5ac4eeb1d739b2e0973b19917c3ea1c/test/e2e/play_kube_test.go#L4662-L4668 |
Meaning, because it can't use a "remote" |
It needs a
after the setenv call to make the server pick it up. |
Gotcha, and then we'd expect it to fail the same way. So okay to skip it entirely then if |
Reading the error message it sounds specific to runc but @giuseppe can confirm. |
I think this should only be tested against crun. |
Thanks for the feedback. Once @giuseppe confirms, I'll update my skip message and we can close this I think. |
yes runc does not support disabling cgroups. It is a crun-only feature. We need to skip the test unless we are using crun |
Thanks Giuseppe. |
* Skip play-kube test when runc is in use containers#17436 * Skip uid/gidmapping idmapped-volume test containers#17433 Signed-off-by: Chris Evich <[email protected]>
To silence my find-obsolete-skips script, remove the '#' from the following issues in skip messages: containers#11784 containers#15013 containers#15025 containers#17433 containers#17436 containers#17456 Also update the messages to reflect the fact that the issues will never be fixed. Also remove ubuntu skips: we no longer test ubuntu. Also remove one buildah skip that is no longer applicable: Fixes: containers#17520 Signed-off-by: Ed Santiago <[email protected]>
Issue Description
Under Debian SID, the podman play kube with disabled cgroup (test/e2e/play_kube_test.go:4657) test fails under root, and remote scenarios (oddly, it passes under 'remote'). Note: The all CI Debian VM's are setup to use runc and CgroupsV1 (not the default).
Steps to reproduce the issue
Steps to reproduce the issue
containers.conf
(see additional info below)podman --storage-opt vfs.imagestore=/tmp/imagecachedir --root /tmp/podman_test595160758/root --runroot /tmp/podman_test595160758/runroot --runtime runc --conmon /usr/bin/conmon --network-config-dir /etc/containers/networks --network-backend netavark --cgroup-manager systemd --tmpdir /tmp/podman_test595160758 --events-backend file --storage-driver vfs play kube /tmp/podman_test595160758/kube.yaml
Describe the results you received
Error: requested OCI runtime runc is not compatible with NoCgroups: invalid argument
Describe the results you expected
podman info output
and
simplePodYaml
:The "remote" flavor of the test can be observed passing in the raw log by searching for the test name.
Additional information
The text was updated successfully, but these errors were encountered: