Thanks! That already makes a lot more sense, although it's still quite a bit more complicated than necessary, and for sure a lot more complicated than earlier versions that "just worked":
❱❱❱ sudo lxd init Do you want to configure a new storage pool (yes/no) [default=yes]? → ok, I suppose yes Name of the new storage pool [default=default]: → seems plausible Name of the storage backend to use (dir, btrfs) [default=dir]: btrfs → could default to btrfs if /var/lib/lxd is on btrfs Create a new BTRFS pool (yes/no) [default=yes]? → that is either redundant or confusing Would you like to use an existing block device (yes/no) [default=no]? → IMHO this shouldn't even be asked, but as long as "no" works.. Would you like to create a new subvolume for the BTRFS storage pool (yes/no) [default=yes]: → "yes" is the only plausible answer, as I already said that I wanted to create a btrfs storage backend Would you like LXD to be available over the network (yes/no) [default=no]? → finally done, and onwards to networking questions :) But this was already the difference between "failure" (or "wreck your hard disk") and "got it working", so thanks again for fixing! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717771 Title: confusing btrfs storage pool creation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1717771/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
