yes, that workaround works, also you can change /etc/default/lxd-bridge and restart the lxd-bridge service.
On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall <casey.marsh...@canonical.com > wrote: > On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer < > alexis.bruem...@canonical.com> wrote: > >> >> Hi All, >> >> As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589 the >> latest LXD will not work with Juju 2.0-beta3. This is a result of LXD >> moving to use a default bridge of lxdbr0 and Juju expecting lxcbr0. Thanks >> to the heads up and help from the LXD team there is a fix for this in Juju >> master that will be available in the release next week. However, until >> then Juju 2.0-beta3 will not work with the latest LXD (v2.0.0-rc8). >> > > If you `dpkg-reconfigure lxd` and name the bridge "lxcbr0", does this work > for beta3? I've been able to bootstrap with latest LXD and current Juju > master (beta4) by configuring LXD this way. > > >> >> Alexis >> >> -- >> Alexis Bruemmer >> Juju Core Manager, Canonical Ltd. >> (503) 686-5018 >> alexis.bruem...@canonical.com >> >> -- >> Juju mailing list >> Juju@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju >> >> > > -- > Juju-dev mailing list > juju-...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
