I Updated this evening and indeed it seems to have fixed this specific Issue.
Seems to work also for me that don't have any write access to that mountpoint (from the Host I mean) :) .
Well, using non-enterprise PVE repos we ARE the beta testers. If they deployed this on the Enterprise repos then yes you have a valid point. This is the risk we take using non-enterprise repos. These kind of breakages are very rare and...
Yep, I've updated this morning and the read only NFS shares on my TrueNAS are working on my containers. The NFS shares read only attribute is set on TrueNAS.
I've used apt-mark unhold pve-container to get the container updated.
After the update, Proxmox now handles container mount points more strictly. This mainly affects unprivileged containers.
Mounted folders now show up as root:root inside the container, so services like MySQL can’t access their files.
If a mount...
I've ran into the same problem, took me a while trying to figure out what the problem was until I found this thread. Downgrading pve-container to 6.0.18 resolved it for me, thanks. Will hold off updating my proxmox nodes until an updated version...
Maybe this can be fixed by removing the code that's causing this issue in /usr/share/perl5/PVE/LXC.pm:
PVE::Tools::fchownat(fileno($mount_fd), '', $uid, $gid, PVE::Tools::AT_EMPTY_PATH)
or die "failed to propagate uid and gid to mountpoint...
Running the apt install pve-container=6.0.18 fixed it for me for now but it's a downgrade of the package.
So what is the official fix to get the newest container package? I've tried apt dist-upgrade which loaded the newest package but it failed...