I’m not sure if this is a LXD4.8 issue or the fact that I’m attempting to use LXD inside a VMWare Fusion virtual machine.
either way I’m seeing…
3: lxdbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 00:16:3e:5f:e8:f5 brd ff:ff:ff:ff:ff:ff
inet 10.69.114.1/24 scope global lxdbr0
valid_lft forever preferred_lft forever
inet6 fd42:dcd9:5a35:cf8::1/64 scope global
valid_lft forever preferred_lft forever
So that’s pretty unlikely to be a LXD issue then. LXD would have effectively done that, if the kernel then flips it back to down, that suggests something else on your system is messing with it.
It could be NetworkManager as it appears to be reacting to things in this case, but it could be something else.
OK so I switched to simplified devices and disabled NetworkManger and its starting to work reliably again.
So nothing todo with LXD though perhaps its the NetworkMangers integration with a VMWare bridged device. I’ve not seen this problem on bare metal Unix nodes with exactly the same OS versions under NetworkManger.