Skip to content
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

rootless: cgroups v1: Failed to add conmon to cgroupfs sandbox cgroup: error creating cgroup for SOMETHING #8721

Closed
edsantiago opened this issue Dec 14, 2020 · 2 comments · Fixed by #8726
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@edsantiago
Copy link
Member

Fallout from #8479 (changing log-level from error to warn): podman run, rootless, on a cgroups v1 system, emits unhelpful warnings:

$ podman run quay.io/libpod/testimage:20200929 date
WARN[0000] Failed to add conmon to cgroupfs sandbox cgroup: error creating cgroup for memory: mkdir /sys/fs/cgroup/memory/libpod_parent: permission denied
Mon Dec 14 21:39:58 UTC 2020

The command works fine, exits 0 and everything, but the warning is harmful to CI tests as well as to users who neither know nor care about libpod_parent and stuff like that.

The precise message differs. These are variants I see:

...creating cgroup for cpu: mkdir /sys/fs/cgroup/cpu/libpod_parent: permission denied
...creating cgroup for blkio: mkdir /sys/fs/cgroup/blkio/libpod_parent: permission denied
...creating cgroup for pids: mkdir /sys/fs/cgroup/pids/libpod_parent: permission denied

Please either fix the condition leading to the warning, or remove the warning.

@rhatdan
Copy link
Member

rhatdan commented Dec 15, 2020

@giuseppe @haircommander @mheon WDYT?

@giuseppe
Copy link
Member

Proposed fix here: #8726

giuseppe added a commit to giuseppe/libpod that referenced this issue Dec 15, 2020
Change the log level when running as rootless when moving conmon to a
different cgroup.

Closes: containers#8721

Signed-off-by: Giuseppe Scrivano <[email protected]>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants