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) :) .
Keep in Mind that that only works if your Host System can actually write to that Directory ;) .
It doesn't work in my Case with a read-only NFS Share exported by a remote NFS Server.
Thus a more permanent Fix is needed. Currently the only "fix"...
Well, maybe so, but a breaking change such as this one (which is NOT the first by a long Shot) which causes Containers to not start should be treated more carefully and not just forced upon Users.
It clearly doesn't work. System is uptodate...
I confirm I was also just affected by this
I opened another Issue a few Minutes ago about it:
https://forum.proxmox.com/threads/lxc-fails-to-start-when-using-read-only-mountpoint.180440/
I have a Mountpoint /tools_nfs that is mounted read-only on most of my Systems, and I want to be able to pass it to each Container.
It used to work OK until now.
I suspect one of the last System Updates messed it up :( .
Attached is the Debug...
I have a use-case where I have some Host Folders that is actually an NFS Mount (could also be CIFS/SSHFS/...).
I then bind-mount (bind or rbind) inside the LXC Container in the Form of
lxc.mount.entry: /mnt/<container_name> data/ none...
Not much to go by really :( .
It's stuck immediately after starting booting Kernel, I cannot do anything with a Keyboard attached to the Server (even via a PS2 to USB Adapter).
I tried adding pci=biosirq or setting pci=noats or...
Well, while for sure integrity of the File is important, if a few links here and there are broken, I don't see that as a valid Reason to abort everything and delete the 99.9% good Container.
I already faced an Issue where the Fedora OCI Image...
the issue is that the template contains hardlinks to symlinks, with one of the hardlinked copies being dangling:
$ ls -lha llvm/usr/lib64/llvm18/lib/
total 114M
drwxrwxr-x 2 fgruenbichler fgruenbichler 180 Jan 12 12:01 .
drwxrwxr-x 3...
Anything weird I am doing ? I seem to hit Edge Cases all them Time. It seemed to me like a pretty standard Container Configuration, isn't it ?
What caused you to NOT have the Issue (when you replied me this Morning) ;) ?
Still Error.
Now I tried downloading the OCI that's marked as stable Release:
https://quay.io/repository/fedora/fedora-coreos?tab=tags&tag=43.20251214.3.0
(on the right Side, behind the Popup, there is a small Green Line with 2 Dots / Images...
What would you like to know exactly ?
Unfortunately it's been a while :(.
If a container Creation fails (like this one did to me), everything gets aborted & erased. So I don't even know exactly where & what I was trying to create it :(. In...
Old Thread but I'll add my 0.02$ just in case you are still looking for a Solution.
In my Case, this can happen (mostly on a Backup Server) if I sent there a ZFS Snapshot WITHOUT specifying a -o mountpoint=/zdata/BACKUP/<HOST> Parameter when...
Alright, thanks :) .
That's a valid Consideration for sure :).
But to mind comes Scenario related to NIC Firmare / Driver which led to both Interfaces disappearing at the same Time (even though only one was being used). Rare Events but they do...