Closed rockdrilla closed 1 year ago
We're already hit by this issue, e.g. https://github.com/nginxinc/docker-nginx/pull/701.
@giuseppe PTAL
thanks, opened a PR: https://github.com/containers/podman/pull/20086
Please be aware that it fixes only the cgroup mounted on the top of /sys/fs/cgroup
. The previous /sys/fs/cgroup
coming from the host will still be visible in /proc/self/mountinfo
. There is no way to address that because without a netns we cannot mount a fresh sysfs and we are forced to bind mount it from the host. Unprivileged users can only use recursive bind mounts, so we will grab /sys/fs/cgroup
from the host as well
Issue Description
Rootless Podman exposes whole
/sys/fs/cgroup/
to container while in "partial" isolation.Correct behavior (achieved with
--systemd=always
):Hovewer,
/proc/self/mountinfo
and/proc/self/cgroup
look "sane" (but they're not).Correct behavior:
Steps to reproduce the issue
Steps to reproduce the issue
--network=host
) and with systemd in "auto" mode (i.e. not specifying--systemd=always
)./sys/fs/cgroup/
.Example:
Describe the results you received
Describe the results you expected
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Running rootless Podman:
Running rootful Podman: