Zfs LXC mountpoint inherit

dragon2611

Renowned Member
Jul 2, 2010
85
7
73
Code:
mount: special device /Vms1/subvol-105-disk-1 does not existmounting container failed - command 'mount -o bind /Vms1/subvol-105-disk-1 /var/lib/lxc/105/rootfs/' failed: exit code 32
extracting archive '/zfsdata/dump/vzdump-lxc-105-2015_10_04-09_08_18.tar'
Total bytes read: 1163151360 (1.1GiB, 25MiB/s)
Detected container architecture: amd64
TASK OK

Looks like the lxc provisioning/restore scripts get screwed up if the subvolume it creates inherits a mountpoint from the subvolumes parent, I suspect they're not explicitly setting the ZFS mountpoint on subvolume creation

Edit: Ah I see now, it completely and utterly trips up if the Pools Inherited mountpoint does NOT match the pool name, ie for Vms1 it HAS to be mounted in /Vms1 for a create/restore to work.

Also restoring an LXC container seems to allow selection of storage destinations where "Disk image" is allowed but "container" isn't enabled.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!