LXD expects the pool or part of the pool that it's provided to be owned by it with no other data there. This is actually enforced in a few places in the LXD code.
So as an acceptable change to LXD, we could just have it enforce that the provided zfs_pool_name (which can be a pool or dataset) exists but is empty. Right now we only check that it's empty when you attempt to unset zfs_pool_name which is a bit weird. And then we can have it always set mountpoint=none on that given that it's then guaranteed to be owned only by LXD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629824 Title: lxd should explicitly create "containers" and "images" datasets on ZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1629824/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
