Arch Linux

MilanKnizek

Member

Registered: 2005-12-13

Posts: 88

Stopping docker.service leaves network bridges intact? Why?

Hi,
docker.service starts a multitude of network bridges. While trying to re-configure `/etc/docker/daemon.json` to use particular network ranges, I noticed that `systemctl stop docker.service` does not remove the bridges. I can do so manually `ip link delete <bridge name>` but that is quite slow.

Is that an expected behaviour?

P.S. These are not managed by systemd-networkd, so `systemctl restart systemd-networkd.service` does not remove them either.

[root@tiger ~]# networkctl list
IDX LINK             TYPE               OPERATIONAL      SETUP     
  1 lo               loopback           carrier          unmanaged 
  2 eno1             ether              routable         configured
  3 eno2             ether              off              unmanaged 
  4 docker0          bridge             no-carrier       unmanaged 
  5 br-a33d057cd1dc  bridge             no-carrier       unmanaged 
  6 br-ffad8781660b  bridge             no-carrier       unmanaged 
  7 br-01ff9b9f4bec  bridge             no-carrier       unmanaged 
  8 br-36c2859a51eb  bridge             no-carrier       unmanaged 
  9 br-4936c03c3ac5  bridge             no-carrier       unmanaged 
 10 br-4d6f39cf0462  bridge             no-carrier       unmanaged 

---

--
Milan Knizek
http://knizek.net