-
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
cgroup: fix rootless --cgroup-parent with pods #10234
cgroup: fix rootless --cgroup-parent with pods #10234
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: giuseppe The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Needs a test, please. Unfortunately, IIUC, this only happens on rootless + cgroups v1 + runc? If that's true, then we're in trouble because we don't test that in CI. @containers/podman-maintainers can we add Prior-ubuntu + rootless to our CI matrix? I do not ask this lightly: I ask because that's the only way we can catch RHEL problems early. |
SGTM |
extend to pods the existing check whether the cgroup is usable when running as rootless with cgroupfs. commit 17ce567 introduced the regression. Signed-off-by: Giuseppe Scrivano <[email protected]>
in this case I like more the runc behavior. If the path is explicitly set in the configuration file (as Podman did before this PR), then the error should not be ignored even in rootless mode on cgroup v1. I've opened a PR for crun to fix it: containers/crun#658 |
LGTM. Tests are passing in #10237, which I rebased onto this PR (they failed catastrophically before I rebased). @containers/podman-maintainers PTAL and let's get this in ASAP. |
/lgtm |
Reason: to catch errors before they surface in RHEL. One of the Ubuntus is specially crafted to run with cgroups v1 and runc. Although this isn't quite the same as RHEL, it's as close as we can come in our CI environment, and I suspect it would have caught containers#10234 (a regression). Sorry, team. Also: play kube limits test: skip on all rootless, not just rootless+fedora. There was a complicated and unnecessary check in there for Fedora. Also: workaround for bug containers#10248, a spurious error message on the first invocation of rootless podman on Ubuntu.Old Signed-off-by: Ed Santiago <[email protected]>
extend to pods the existing check whether the cgroup is usable when
running as rootless with cgroupfs.
commit 17ce567 introduced the
regression.
[NO TESTS NEEDED] -- we already have tests, they're just not being run. #10237 hopes to fix that.
Signed-off-by: Giuseppe Scrivano [email protected]