Hi,
I recently made an effort of re-creating all of my containers as unprivileged (all successful I might add, so yay!).
Since I just re-installed Proxmox I noticed the first time that restoring a container with a custom idmap creates the original folders with an incorrect owner - the uid / gid assigned are the ones that would be correct WITHOUT the id mapping.
A concrete example, here's one of my containers config:
So I'm only mapping user container user 1000 to host user 800 so the mapped folders can be used properly - all of that works, everybody's happy.
If you mount the container's drive from root you can see that for example the home folder of user 1000 belongs to host user 800.
After restoring the container the home folder now belongs to uid / gid 101000, which results the container listing "nobody" / "nogroup".
Mounting the drive from the host and chown-ing it back to uid 800 fixes things and the container works as expected.
I recently made an effort of re-creating all of my containers as unprivileged (all successful I might add, so yay!).
Since I just re-installed Proxmox I noticed the first time that restoring a container with a custom idmap creates the original folders with an incorrect owner - the uid / gid assigned are the ones that would be correct WITHOUT the id mapping.
A concrete example, here's one of my containers config:
So I'm only mapping user container user 1000 to host user 800 so the mapped folders can be used properly - all of that works, everybody's happy.
If you mount the container's drive from root you can see that for example the home folder of user 1000 belongs to host user 800.
After restoring the container the home folder now belongs to uid / gid 101000, which results the container listing "nobody" / "nogroup".
Mounting the drive from the host and chown-ing it back to uid 800 fixes things and the container works as expected.