[lxc-users] Installing lxd doesn't create bridge lxdbr0?

[Fajar A. Nugraha]

On Sun, May 1, 2016 at 8:07 AM, Dan Kegel <dank at kegel.com> wrote:
> On ubuntu 16.04, the commands
>    sudo apt install lxd
>    sudo apt purge lxd
>    ip link list
> show that lxd leaves behind bridge lxdbr0 after uninstall, tsk tsk.
> A tidy user might well do
>    sudo ip link del lxdbr0
> to clean up after it.
>

A "clean" way would probably be

systemctl stop lxd-bridge
apt-get purge lxd

> But alas!  If you do that, *future* installs of lxd break, i.e.
>    sudo apt install lxd
>    lxc launch ubuntu: demo
> fails!
>   lxc info --show-log demo shows
>             lxc 20160430173001.967 ERROR    lxc_conf -
> conf.c:instantiate_veth:2594 - failed to attach 'veth7ME5PJ' to the
> bridge 'lxdbr0': Operation not permitted
> As mentioned in tych0's post
> https://github.com/tych0/tycho.ws/issues/1 that can mean the bridge is
> missing.
>
> Sure enough, the command
>   sudo ip link add name lxdbr0 type bridge
> rescues lxd and lets containers start again.

systemctl start lxd-bridge

As a side note, if you stop the lxd-bridge service before you purge
lxd, then it would automatically be started again the next time it's
needed (e.g. when you run "lxc list" or something)

>
> Why does lxd leave that bridge around after apt purge lxd, and why

Not sure.

Probably the devs think something else might still be using lxd
bridge? Or perhaps they think remove the service file is enough?

> doesn't it create it again on a new install?

Probably due to some systemd thinking "lxd-bridge" is (since the
service file was unceremoniously removed) started when it actualy
isn't.

-- 
Fajar