-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Incus does not respect /etc/sub*id #289127
Comments
I wonder if this is related to lxc/incus#575 . I haven't had a chance to troubleshoot myself, but would like to get it resolved. |
I noticed errors around |
Well I can confirm #307218 does in fact improve Incus's handling of the id ranges. Since it caused my containers to fail to start as I was missing a range I had manually added to instances. |
@FlyingWombat if you're able to confirm it fixes your described issue, I'd appreciate it. |
@adamcstephens With the changes in the linked pull request, Incus seems to be working as expected. |
Thank you for testing! |
Describe the bug
Incus does not respect subuid/subgid mappings set in /etc/sub*id.
Steps To Reproduce
Steps to reproduce the behavior:
sudo mv /var/lib/incus /var/lib/incus.bk
cat /etc/sub{gid,uid}
sudo incus admin init --minimal
sudo incus launch images:archlinux/current/amd64 test
sudo incus config show test
Notice how Hostid and Maprange are wrong.
Expected behavior
Additional context
My incus installation in Archlinux generates idmap correctly.
If the same is done with LXD, the idmap is generated correctly.
Incus docs /userns-idmap.md:40
BTW, docs for
users.users.<name>.autoSubUidGidRange
is misleading. It says "Default: false". This should read "Default:config.isNormalUser && config.subUidRanges == [] && config.subGidRanges == []
"Notify maintainers
@aanderse
@adamcstephens
@jnsgruk
@megheaiulian
@mkg20001
Metadata
"x86_64-linux"
Linux 6.7.4, NixOS, 24.05 (Uakari), 24.05.20240212.aff1ac0
yes
yes
nix-env (Nix) 2.18.1
"nixos"
/run/current-system/nixpkgs
commit d934204Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: