Closed doppelrittberger closed 1 year ago
@giuseppe PTAL
mount_setattr
was added in 5.12 according to the man page.
I think it is caused by https://github.com/containers/crun/commit/908bfc43087a845ba3f779cfed933e2a539b714a, that is an intentional change. To mount a fresh sysfs
, /sys
must be fully visible in the current context, which is not the case when running an unprivileged pod. If we bind mount it, we risk to expose the cgroup file system as writeable (in your case it would not matter since anyway you are in a container).
I suggest to workaround it either with --net host
or -v /sys:/sys
since we know you are already in a container, so there is not much you need to protect the nested container from
Issue Description
Hi
we use rootless podman to run containers inside a gitlab pipeline. Unfortunately we get the following error when trying to run a container:
The same call works using a different environment/newer kernel version. Anything I missed to configure?
Thanks for your great support
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
A failing container
Describe the results you expected
A running container
podman info output
Podman in a container
Yes
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional debug log: