-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
userns = "auto"
not respected in containers.conf
#12615
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 16, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
PR here: #12621 |
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 16, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 16, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 16, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 16, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 16, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 17, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 17, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 17, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 17, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 20, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 20, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 20, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Dec 20, 2021
when using the default userns value, make sure its value is parsed so that userns=auto is parsed and the options for the storage are filled. Closes: containers#12615 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
userns = "auto"
in/etc/containers/containers.conf
does not seem to be respected.Steps to reproduce the issue:
containers
Set
userns = "auto"
incontainers.conf
under[containers]
headingDescribe the results you received:
The container's root is mapped to the hosts's root.
The contents of '/proc/self/uid_map':
0 0 4294967295
Describe the results you expected:
I expect the container's root to be mapped to a uid somewhere in the range set in
/etc/subuid
This should yield the same output as if
--userns auto
is provided in the run command:Additional information you deem important (e.g. issue happens only occasionally):
Using the environment variable works the same as using the
--userns
flag.Output of
podman version
:Output of
podman info --debug
:Package info (output of
apk info podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes, I have tested with version 3.4.4 and I checked the guide.
Additional environment details (AWS, VirtualBox, physical, etc.):
The alpine machine this was tested on is a KVM virtual machine, however the same issue was also observed on a baremetal Debian 11 machine with podman 3.0.1
The text was updated successfully, but these errors were encountered: