-
Notifications
You must be signed in to change notification settings - Fork 99
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
[rootlesskit:parent] error: failed to setup UID/GID map [...] newuidmap: write to uid_map failed: Operation not permitted #404
Comments
I also tried
This does seem to set the capability correctly, as |
What's your host OS and docker version? The dockerfile works for me with Docker 24.0.7 on Ubuntu 22.04.3 LTS (kernel 5.15.0-86-generic). |
|
Just getting back to this, sorry for the really late response. Here's the docker info:
I'm not trying to run this inside rootless docker - just regular docker. This is Ubuntu 22.04, with kernel 5.15.0-92-generic on aarch64. From what I can tell reading the two links, it doesn't need any sysctl setup - it's too old for the 23.10 ntroduced userns but new enough to need
|
@AkihiroSuda
error shows:
If I apt-get install uidmap, then download rootlesskit package manually, it still not work
If I install the newuidmap and newgidmap from shadow, then it works
why rootlesskit doesn't work in Debain? |
It may because Debian doesn't set cap for /usr/bin/newuidmap and /usr/bin/newgidmap, it works after setting the capabilities:
Example:
|
That's really interesting @zhoufenqin! I had the following lines in my
but that doesn't work. But
does?! |
Aaaaah, it's because my second one was doing |
Awesome project :) I'm trying to use rootlesskit directly, since I want isolation without necessarily image management, etc.
I'm trying to run it inside a docker container, with this
Dockerfile
:And I build this image, and run it with
docker run -it --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined wat /bin/bash
.But rootlesskit just fails, with
/etc/subuid
and/etc/subgid
look fine:Dropping the
--privileged
flag seems to have no effect either.The text was updated successfully, but these errors were encountered: