I just migrated to 5.0 as a fresh install. I'm trying to get my containers back up, which in my last config (Proxmox 4.4) had mount points that pointed to directories (bind) for my different zfs subvolumes.
After the upgrade, my containers can't access the subdirectories in the shares, and I'm not sure why. I saw in my search that I can mount a ZFS subvolume directly in a container, but no instructions on how to do so. I want the contents of these subvolumes available between different containers, which worked before.
Thanks for any help you can provide.
Update: All the files in the directory are chmod 666, and within the container owned by nobody:nobody. This is an unprivileged container, and was in the previous version of Proxmox.
Update 2: I tried going through the unprivileged instructions for mapping user ids in the wiki, with no luck (container won't start), it looks like it needs to be updated, and thought this reddit post was really helpful, but ultimately not the solution I need. Apparently I can read the files if I give everybody execute permissions (777). Bizarre. I'll change my permissions to 777 for the time being, but it's not ideal.
After the upgrade, my containers can't access the subdirectories in the shares, and I'm not sure why. I saw in my search that I can mount a ZFS subvolume directly in a container, but no instructions on how to do so. I want the contents of these subvolumes available between different containers, which worked before.
Thanks for any help you can provide.
Update: All the files in the directory are chmod 666, and within the container owned by nobody:nobody. This is an unprivileged container, and was in the previous version of Proxmox.
Update 2: I tried going through the unprivileged instructions for mapping user ids in the wiki, with no luck (container won't start), it looks like it needs to be updated, and thought this reddit post was really helpful, but ultimately not the solution I need. Apparently I can read the files if I give everybody execute permissions (777). Bizarre. I'll change my permissions to 777 for the time being, but it's not ideal.
Last edited: