LXC Fails to start when using read-only Mountpoint

silverstone

Renowned Member
Apr 28, 2018
191
28
68
36
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 Log obtained by lxc-start -F --logpriority=DEBUG --logfile=/root/debug_104.log 104.
The Logs don't say explicitly where the Problem is/was, so I had to open the File /etc/pve/lxc/104.conf and try to comment (disable) one-by-one the different Lines.

The Failures are those at around Time 20260208131701 and 20260208131942. Afterwards, it's the Startup Log after the Offending Line has been commented out in the Configuration File (see below).

Contents of /etc/pve/lxc/104.conf File:
Code:
lxc.idmap: u 0 100000 1000
lxc.idmap: g 0 100000 1000
lxc.idmap: u 1000 2000 1
lxc.idmap: g 1000 2000 1
lxc.idmap: u 1001 101001 165536
lxc.idmap: g 1001 101001 165536
#mp0%3A /tools_nfs,mp=/tools_nfs,mountoptions=discard;noatime,ro=1
arch: amd64
cmode: console
cores: 2
dev0: /dev/dri/card0,mode=0660
dev1: /dev/dri/renderD128,gid=992,mode=0666
features: fuse=1,keyctl=1,nesting=1
hostname: ollama
memory: 4096
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=BC:24:11:F4:C5:55,ip=dhcp,ip6=dhcp,type=veth
onboot: 1
ostype: fedora
rootfs: local-zfs-rpool:subvol-104-disk-0,mountoptions=discard;noatime,size=64G
swap: 0
tags: production
unprivileged: 1
lxc.cgroup.devices.allow: c 10:200 rwm
lxc.cgroup2.devices.allow: c 10:200 rwm
lxc.mount.entry: /dev/net dev/net none bind,create=dir
lxc.mount.entry: /dev/dri/by-path dev/dri/by-path none rbind,create=dir 0 0
 

Attachments