Installing docker screwed up my bridge br0

General system EndeavourOS installation
1

I have/had a working EOS system where I have a bridge created so when I create kvm vm’s all those vm’s are on the same subnet as my host machine and my entire home lan. Makes it easy to ssh into a vm from anywhere in my house.

So what when wrong was I install Docker and it created it’s own bridge call docker0. Docker works so far fine, but any vm’s I launch with the Bridge br0 as usual can no longer get to the network; connection is down.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp90s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether a8:a1:59:6b:0a:44 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
    link/ether a8:a1:59:6b:0d:28 brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 1e:0b:15:3c:67:54 brd ff:ff:ff:ff:ff:ff permaddr 08:5b:d6:cb:21:68
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 12:7a:c9:de:81:17 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.139/24 brd 192.168.0.255 scope global dynamic noprefixroute br0
       valid_lft 4354sec preferred_lft 4354sec
    inet6 fe80::df55:a7f0:b82d:3e2b/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:fb:32:34:89 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:fbff:fe32:3489/64 scope link 
       valid_lft forever preferred_lft forever

[jim@den-pc ~]$ nmcli con show
NAME                UUID                                  TYPE      DEVICE  
br0                 62375f30-d000-4b0e-bbf8-9f6050f43a10  bridge    br0     
docker0             f27cd525-aa6b-4114-a260-b1b03f59f106  bridge    docker0 
bridge-slave-eno1   36eafe56-1e94-43a7-87fa-1abea64acf24  ethernet  eno1    
Wired connection 1  e7c510d3-a88b-3d02-b0cf-9403cd21263d  ethernet  --

Is there a way to make both Docker and br0 for everything else work together?

BTW, I use snapper so I can undo all this back to before docker if I want.

2

Possibly related to https://wiki.archlinux.org/title/Docker#Starting_Docker_breaks_KVM_bridged_networking

3

Thanks, if I make the change to assign my bridge br0 for docker, it allows the KVM VMs to run, but then Docker will not. Not sure what change is needed to run both

4

What about the

bit?

5

I’ll try the other solutions later. My short term solution was to bring up a VM for just running Docker for an Android-studio build engine. I use more VMs than Docker containers, so it’s easier to push the problem down a level and not screw up the main system. Snapshots are great, but for today, I’m tired of rolling them back.