Skip to content
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

failed to setup UID/GID map - subuid / subgid #259

Open
idesk2596 opened this issue Jun 27, 2021 · 3 comments
Open

failed to setup UID/GID map - subuid / subgid #259

idesk2596 opened this issue Jun 27, 2021 · 3 comments
Labels
question Further information is requested

Comments

@idesk2596
Copy link

idesk2596 commented Jun 27, 2021

Hi,

Until The glibc nss name service switch mechanism have support for managing subuid and subgid mappings, we're managing those files with symlinks to nfs shares.

/etc/subuid -> /nfs/.../subuid
/etc/subgid -> /nfs/.../subgid

it is working great with singularity, but trying to implement it with docker-rootless (which use rootlesskit)
we get this error:

$ rootlesskit bash
[rootlesskit:parent] error: failed to setup UID/GID map: newuidmap 81751 [0 11737 1 1 4294836224 65536] failed: : exit status 1

it works if /etc/subuid and /etc/subgid were set as a regular files.
Trying to work this out on a large HPC node scale.

can you support this?

Thanks, Kobe

@AkihiroSuda AkihiroSuda added the question Further information is requested label Jun 28, 2021
@idesk2596
Copy link
Author

?

@AkihiroSuda
Copy link
Member

This is probably an issue of newuidmap/newuidmap, and probably they prohibit symlinking on purpose

@idesk2596
Copy link
Author

singularity use newuidmap as well with its --fakeroot functionality and it's working well when these files are symlinks.. this is why i wonder..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants