newgidmap: gid range [1005-1006) -> [1005-1006) not allowed

Stunod

New Member
Mar 30, 2024
2
0
1
I have a windows share that is mounted on the proxmox host. I'm trying to make the files available in the guest (unprivileged docker container). At first I can see the files in the container ok but they are read only.

Following the guide here;
https://pve.proxmox.com/wiki/Unprivileged_LXC_containers

I put the stated entries into;

/etc/pve/lxc/104.conf
lxc.idmap: u 0 100000 1005
lxc.idmap: g 0 100000 1005
lxc.idmap: u 1005 1005 1
lxc.idmap: g 1005 1005 1
lxc.idmap: u 1006 101006 64530
lxc.idmap: g 1006 101006 64530
/etc/subgid
root:100000:65536
root:1005:1
/etc/subguid
root:100000:65536
root:1005:1

Every time I start the container it fails and I get this error, if I remove the lines it works but then I don't have write access to the files in the mount
lxc_map_ids: 3701 newgidmap failed to write mapping "newgidmap: gid range [1005-1006) -> [1005-1006) not allowed": newgidmap 530607 0 100000 1005 1005 1005 1 1006 101006 64530
lxc_spawn: 1788 Failed to set up id mapping.
__lxc_start: 2107 Failed to spawn container "104"
TASK ERROR: startup for container '104' failed

I've seen this similar issue posted all over and nothing I seem to try is working.
 
Last edited:
it's "subgid", not "subguid"
 
  • Like
Reactions: bmchef

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!