I've usually ended up just running my containers as privileged, since it makes things work, but I don't want to keep doing that.
Just as a generic example, since container content is irrelevant here. I have a folder on my NAS mounted in /mnt/pve/backups. I want this folder to be writeable from a container. On the Synology side, the folder was created by the backup user, and is owned by backup:users. On the host side it is owned by root:root, and the same inside the container if I just map it with:
mp0: /mnt/pve/backups, mp=/backups
But of course it's not writeable.
I've tried various guides and tutorials, but I don't understand enough about what I'm doing to understand why they don't work.
Just as a generic example, since container content is irrelevant here. I have a folder on my NAS mounted in /mnt/pve/backups. I want this folder to be writeable from a container. On the Synology side, the folder was created by the backup user, and is owned by backup:users. On the host side it is owned by root:root, and the same inside the container if I just map it with:
mp0: /mnt/pve/backups, mp=/backups
But of course it's not writeable.
I've tried various guides and tutorials, but I don't understand enough about what I'm doing to understand why they don't work.
