We may consider doing some of that when reworking the way we handle
storage in a few months.
For now, users will typically use "lxd init" which will create a LXD
pool for them that's marked with mounts disabled from the start (and a
clean config for everything else).
If you opt into using a subset of an existing pool, we assume you know
what you're doing and that you will properly configure it prior to
giving it to LXD (LXD won't create it for you so you kinda have to).
The fact that LXD doesn't put /var/lib/lxd itself in the ZFS pool is
intentional. LXD will eventually support multiple pools and storage
backends being used in parallel, which would directly conflict with this
approach.
** Changed in: lxd (Ubuntu)
Status: New => Triaged
** Changed in: lxd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: lxd (Ubuntu)
Status: Triaged => Won't Fix
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
