Hi All,
Thank you very much for posting this thread. I've been following the
"getting started" developer's guide at
https://jujucharms.com/docs/devel/getting-started, and this info got me
unstuck.
I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
create an ipv4 subnet, rather
The rename works if you haven't removed `lxc1` which removes the original
`lxcbr0`. If you have you will need to correctly configure another bridge
as the new `lxcbr0` that is created has the same configuration as `lxdbr0`
if you configured an `lxdbr0`... For me this led to two bridges with the
sam
I think you'll need to `service lxd-bridge restart' in either case.
On 6 April 2016 at 22:18, Horacio Duran wrote:
> 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...
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 wrote:
> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
> alexis.bruem...@canonical.com> wrote:
>
>>
>> Hi All,
>>
>> As recently highligh
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
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 i
