-
Notifications
You must be signed in to change notification settings - Fork 101
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: failed to compute uid map: no matching entries in passwd file #48
Comments
Thanks for the report.
How do you configure subuid/subgid? |
Manually editing it for my account. Without doing that first the install script throws errors like:
|
This issue moby/moby#20191 seems to deal with external auth for user namespaces and the pr here moby/moby#27599 seems to fix it. I can manage maps for /etc/subuid and /etc/subgid via configuration management. Just need lookups to work. |
I hacked this together using idtools to get the user and subid mappings in newuidmapArgs/newgidmapArgs. master...jaredbancroft:jb_idtools rootlesskit runs and dockerd-rootless.sh --experimental starts but attempting to run any container blows up in the following manner.
|
Looks like number of subuid is insufficient.
|
My uid appears mapped to root and the rest seems sufficient typos and all (was supposed to be 65537 for a full range of 65536 since count is the upper limit of an exclusive interval). |
also gid_map please? |
|
Deleted my entire XDG_RUNTIME_DIR and --data-root dir and started up from scratch and everything is working now. Must have been some crufty artifacts from earlier attempts causing the issue.
|
👍 could you open PR for idtools ? |
#53 opened |
Command producing the error was ./bin/dockerd-rootless.sh --experimental --storage-driver vfs
Trying to get this working on RHEL 7.6 kernel 3.10.0-957.1.3.el7.x86_64. We use NIS and SSSD so local /etc/passwd and /etc/group do not contain any network user specific information. ypcat passwd would be able to match uid.
The text was updated successfully, but these errors were encountered: