Replies: 3 comments
-
A friendly reminder that this issue had no activity for 30 days. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@giuseppe Ideas? |
Beta Was this translation helpful? Give feedback.
0 replies
-
you need to configure the cgroup for the nested container by yourself, since there is not systemd inside the outer container to do it for us:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Issue Description
I try to fully grasp all the possible combinations of cgroups behaviour that can happen with podman, so I run possibly strange combination of tests.
When I have a privileged rootless podman container and I run a rootless podman container it in, the
/sys/fs/cgroup
is mountedrw
there but owned bynobody
(meaning like the root in the parent containre), leading toPermission denied
.Steps to reproduce the issue
Steps to reproduce the issue
quay.io/podman/stable
container:/sys/fs/cgroup
mounts in a rootless container in a rootless container #21376 (comment)), remove the default configuration that is in thatquay.io/podman/stable
image:podman
user in that container, run a privileged container in that privileged container:Describe the results you received
Describe the results you expected
No error.
I wonder if this is podman equivalent of CRI-O's cri-o/cri-o#7623?
podman info output
Podman in a container
Yes
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
None.
Additional information
This is deterministic.
Beta Was this translation helpful? Give feedback.
All reactions