I'm trying the new mount-point ID mapping feature introduced in Proxmox VE 9.2 with an Ubuntu 26.04 LTS unprivileged container.
The host is running the latest PVE packages with kernel
On the host, the shared directory is owned by group
The
Inside the container, I want this mapped to GID
Container configuration:
Inside the container, the mapping appears to work:
The
However, a user who belongs to that group cannot write to the directory:
So the mount-point GID mapping appears to be applied correctly for ownership/display purposes, but it does not seem to grant write access.
Am I missing an additional configuration step for mapped GIDs on unprivileged containers, or is this a limitation/bug in the new mount-point ID mapping feature?
The host is running the latest PVE packages with kernel
7.0.14-12-pve.On the host, the shared directory is owned by group
media:
Code:
root@pve:/data# ls -l
drwxrwsr-x 5 david media 5 Aug 23 11:56 downloadsThe
media group has GID 1000 on the host.Inside the container, I want this mapped to GID
2000.Container configuration:
Code:
cat /etc/pve/nodes/pve/lxc/123.conf
...
mp0: /data/downloads,mp=/data/downloads,idmap=g:1000:2000:1
...Inside the container, the mapping appears to work:
Code:
root@my-container:/data# ls -l
drwxrwsr-x 5 nobody media 5 Aug 23 09:56 downloadsThe
media group inside the container has GID 2000.However, a user who belongs to that group cannot write to the directory:
Code:
root@my-container:~# id bob
uid=103(bob) gid=1000(media) groups=1000(media)
Code:
root@my-container:~# sudo -u bob touch /data/downloads/test
touch: cannot touch '/data/downloads/test': Permission deniedSo the mount-point GID mapping appears to be applied correctly for ownership/display purposes, but it does not seem to grant write access.
Am I missing an additional configuration step for mapped GIDs on unprivileged containers, or is this a limitation/bug in the new mount-point ID mapping feature?