I just ran lxd init and I told lxd that:
Would you like LXD to be available over the network (yes/no): YES!
And
Do you want to configure the LXD bridge (yes/no) [default=yes]? NO!
And I told it that br0 is a bridge I have created.
Everything seems fine but when I run lxc list:
The network says 10.134.96.160 (eth0), that is not the IP of the bridge not even close.
And the container can be pinged from the network and can ping the local network but not outside the LAN.
And apt doesn’t work since it doesn’t have a internet connection.
Ok, if using the snap, make sure you don’t have the deb installed (lxd and lxd-client packages) at the same time as it could lead to what you described.
So I had to reinstall the server completely (or so I thought) so here I am with an clean install of everything.
I did ran lxd init found a post about networking wih lxc/lxd that looked good:
I havn’t made any changes yet since I dont have /etc/lxc or /etc/default/lxc.
All I have installed concerning this is bridge-utils. I have set up an br0.
I have one container as of now it has an erh0 network that is uniqe to that on, it can ping all the machine on the lan but no one on the lan can reach the container.
So I am running the lxc/lxd install that comes with Ubuntu Server 18.04 LTS.
So now what?
I cant since the network is in use - now I am asking to simple questions it feels like.
The lxdbr0 network is set to down.
I tried to stop the container - that didnt help.