So we certainly agree that the lxdbr0 configuration experience isn't
exactly great on 16.04.
This is caused by the fact that the bridge is configured as part of
Ubuntu packaging instead of through LXD itself and so uses debconf
dialogs which come with a bunch of limitations.
In recent LXD, network management is done directly inside LXD and so the
"lxd init" experience is much nicer.
As for your questions:
1) That's a debconf limitation, nothing we can do here.
2) Nope, it's an IPv4 address. The same question is asked later for IPv6 as we
supported configuring both.
3) If it was easy to do subnet math inside a limited shell script, we'd totally
do that but unfortunately it's not exactly easy and even then, modifying
pre-seeded debconf values is a pain.
4) Same as above, doing subnet math in basic POSIX shell isn't exactly easy :)
On LXD 2.4 or higher, things now look like:
root@lxd:~# lxd init
Name of the storage backend to use (dir or zfs) [default=dir]:
Would you like LXD to be available over the network (yes/no) [default=no]?
Would you like stale cached images to be updated automatically (yes/no)
[default=yes]?
Would you like to create a new network bridge (yes/no) [default=yes]?
What should the new bridge be called [default=lxdbr0]? br0
What IPv4 subnet should be used (CIDR notation, “auto” or “none”)
[default=auto]? 10.0.5.1/24
Would you like LXD to NAT IPv4 traffic on your bridge? [default=yes]?
What IPv6 subnet should be used (CIDR notation, “auto” or “none”)
[default=auto]?
LXD has been successfully configured.
** Changed in: lxd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651426
Title:
sudo lxd init user experience is poor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1651426/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
