Hello all,
I have the following configuration (and similar like it) for a lot of my LXC containers:
They are on a glusterfs share (yes, I know it's deprecated, don't come at me about it - I'm not using it as an integration, just standalone shared filesystem), with permissions of a user somewhere in the
However, whenever I start up a container with a mountpoint like this, the permission of ONLY the top-level directory gets changed to 10000.
Is that by design somewhere, or is there something about my mount point configuration that's missing?
This is really throwing me off, as I am having to re-set permissions every time that I stop/start a container.
I have the following configuration (and similar like it) for a lot of my LXC containers:
Code:
./209.conf:mp0: /mnt/glusterfs/hub-volume/andrewcz-org/firefly-importer_uploads,mp=/var/lib/firefly-importer/data/storage/uploads
./209.conf:mp1: /mnt/glusterfs/hub-volume/andrewcz-org/firefly-importer_configurations,mp=/var/lib/firefly-importer/data/storage/configurationsThey are on a glusterfs share (yes, I know it's deprecated, don't come at me about it - I'm not using it as an integration, just standalone shared filesystem), with permissions of a user somewhere in the
10000+ range because of remapping, so that it will match the uid of the user inside of the container.
Code:
root@hub-proxmini02:/etc/pve/lxc# ls -l /mnt/glusterfs/hub-volume/andrewcz-org/firefly-importer_configurations -a
total 8
drwxr-xr-x 2 109014 109014 4096 Dec 21 14:30 .However, whenever I start up a container with a mountpoint like this, the permission of ONLY the top-level directory gets changed to 10000.
Is that by design somewhere, or is there something about my mount point configuration that's missing?
This is really throwing me off, as I am having to re-set permissions every time that I stop/start a container.