When one installs bind, and doesn't configure it, it listens on all interfaces.
Since LXD uses dnsmasq on LXD network (which uses the same port as bind), starting dnsmasq fails and therefore LXD too. We should not disable people's bind, because they must have installed it for a reason. Maybe bind, by default, should listen only on localhost. Or... LXD systemd service detects running service on port 53 on LXD's network and provides meaningful message. We can't solve this like we did with apache and nginx (autodetect, change port), because dns needs to be on port 53. Either way, juju can't do much here... uto, 8. kol 2017. 03:52 Tim Penhey <[email protected]> je napisao: > Yep, that is pretty strange. Why was bind running? > > Tim > > On 03/08/17 07:45, fengxia wrote: > > For anyone, the solution is rather strange: > > > > $ sudo service stop bind9 > > > > $ sudo lxd start > > > > Reference: https://github.com/lxc/lxd/issues/2046 > > > > > > On 08/02/2017 03:33 PM, fengxia wrote: > >> Hi Juju, > >> > >> I have a 16.04 KVM. Installed juju and LXD from apt. > >> > >> $ juju bootstrap localhost test > >> > >> ERROR creating LXD client: can't connect to the local LXD server: Get > >> http://unix.socket/1.0: read unix @->/var/lib/lxd/unix.socket: read: > >> connection reset by peer > >> > >> Please install LXD by running: > >> $ sudo apt-get install lxd > >> and then configure it with: > >> $ newgrp lxd > >> $ lxd init > >> > >> Tried the suggested commands. Rebooted KVM. No avail. > >> > >> Is this because I'm running LXD inside KVM? > >> > > > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Ante Karamatić [email protected] Canonical
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
