[SOLVED] PVE5 cannot add bind mount point to LXC

[johnnywoz]

So here I am banging my head against the keyboard once again trying to get an NFS mount point into a container.
previous post where I learned how to do it

When I had PVE4.4 running I was able to successfully setup a bind mount point, but for some reason now with PVE5 running (fresh build) every time I start the LXC it fails to start. If I remove the mount point the LXC starts.



Any thoughts???

Thanks!

 

[fireon]

Please post your containerconfig.

 

[johnnywoz]

arch: amd64
cores: 2
hostname: foobar
memory: 4096
mp0: /mnt/foo,mp=/home/bar
net0: name=eth0,bridge=vmbr0,gw=10.10.10.1,hwaddr=DA:EA:47:87:05:76,ip=10.10.10.220/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-110-disk-1,size=8G
startup: order=2,up=60,down=60
swap: 1024
unprivileged: 1

 

[johnnywoz]

Here is the error message;

Job for lxc@110.service failed because the control process exited with error code.
See "systemctl status lxc@110.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start lxc@110' failed: exit code 1

 

[johnnywoz]

OK, I have no idea what happened with that LXC

As a test case I created a new Debian8 LXC, and was able to add the mount point. hmmmm...
So then I created a fresh Debian9 LXC (which is what my original lxc was), and was able to add the mount point

Whatever, I must have made some sort of change in the original lxc to cause the problem, geez.

 

[fireon]

Strange! Have also done an upgrade from 4.4 to 5.0. Every mounts in LXC working fine... the only differnce: i using ubuntu, not debian lxc.