Mountpoints for LXC containers broken after update

[Darkk]

# apt changelog pve-container
pve-container (6.1.1) trixie; urgency=medium
  * setup: plugin interface: add missing check_systemd_nesting stub.
  * fix #7270: setup: add no-op check_systemd_nesting implementation for
    unmanaged containers.
  * setup: add no-op detect_architecture for unmanaged CTs.
  * fix #7271: exclude non-volume mount points, like e.g. bind mounts, from
    attribute preservation.
 -- Proxmox Support Team <support@proxmox.com>  Fri, 06 Feb 2026 15:40:44 +0100

Just installed now and appears all is working fine for my lxc containers that had nfs mounts. So fix #7271 was what was required.

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.

 

[Darkk]

I wish Proxmox VE Developers would test this kind of Breaking Changes BEFORE deploying them.

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 quickly fixed. I use non-enterprise repos for my home lab and it's not critical to me if they break. I do have a couple of production clusters at work that are using enterprise repos.

 

[silverstone]

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.

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) .

 

[silverstone]

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 quickly fixed. I use non-enterprise repos for my home lab and it's not critical to me if they break. I do have a couple of production clusters at work that are using enterprise repos.

You have a Point. Isn't it pve-test where the modifications land first though, before they get to pve-no-subscription ?

 

[hnguk]

You have a Point. Isn't it pve-test where the modifications land first though, before they get to pve-no-subscription ?

Per the documentation it does state: "It’s not recommended to use this on production servers, as these packages are not always as heavily tested and validated." Source: https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_no_subscription_repo

Without knowing the development cycle my only guess is that it was missed in testing before it got to the no-sub repo. It's worth noting however this is probably the first bug I've personally encountered since using Proxmox since ~2017.