Unable to clone mountpoint during container clone

[David Fell]

I am running current (pve-manager/5.2-9/4b30e8f9 (running kernel: 4.15.18-5-pve)) pve and getting an error during container cloning. My container has a mount point, and I remember reading something about mounpoints can be awkward with clones but can't find it now. The conf file for the container (id 105) is:

arch: amd64
cores: 1
hostname: temp10
memory: 3072
mp0: /home/borris,mp=/home/borris,replicate=0
net0: name=eth0,bridge=vmbr0,hwaddr=72:50:60:2F:E6:B1,ip=192.168.111.60/24,type=veth
onboot: 1
ostype: debian
rootfs: vmstore:subvol-105-disk-0,size=8G
swap: 0

There error I get is:

root@zen:/etc/pve/lxc# pct clone 105 149 --description "ct149 clone" --hostname ct149 --target zen
unable to clone mountpint 'mp0' (type bind)

Could someone please point me at what I'm doing wrong? I added the replicate=0 as a guess as to what needed doing, but obviously this isn't quite the issue.

Thanks

 

[dcsapak]

bindmounts cannot be cloned (the semantics of this would be a little ambiguous, should we copy it, or only reference it),
and there is no flag that tells pve to not include a disk/mp in a clone
so you would have to remove the bindmount temporarily, clone the container, and add it again

 

[David Fell]

Ah, ok. I ended up temporarily removing the mp. I thought I'd read something that a workaround - well, more of a workaround than just hiding the mount. But I must have been wrong. Thanks for resonding