60
15
I'm using docker via
# service docker start
This creates a docker0 bridge. However using
# service docker stop
doesn't remove this bridge.
How do I get rid of it? I'm not sure if I missed something here.
tynn
Posted 2015-11-03T10:47:19.667
Reputation: 703
97
Just delete it:
ip link del docker0
(The old way, specific to bridges: brctl delbr docker0)
user1686
Posted 2015-11-03T10:47:19.667
Reputation: 283 655
6That was step one, but the NetworkManager still had the bridge. So calling nmcli connection delete docker0 resolved the issue completely. – tynn – 2015-11-03T12:11:18.750
Thanks for the note @tynn, definitely useful when developing from a system with a GUI. – dragon788 – 2016-04-02T00:17:32.723
3Will this solution prevent Docker from starting correctly after doing service docker start or will docker create the bridge again? – AlikElzin-kilaka – 2017-05-14T12:05:42.090
This is not an old way, you still need brctl package to do any bridges process. – Mohammed Noureldin – 2017-07-15T02:00:37.040
1No you don't. iproute2 is perfectly capable of doing the same. – user1686 – 2017-07-15T07:46:08.070
5@AlikElzin-kilaka the bridge is created again when you start docker – Fabian Schmengler – 2018-10-19T06:21:21.880
1For the googlers: Check command docker network ls and docker network rm <ID>. The ID is the same as in the br- or bridge name! – uav – 2020-01-09T18:54:08.600
See also https://serverfault.com/questions/642981/docker-containers-cant-resolve-dns-on-ubuntu-14-04-desktop-host
– Ondra Žižka – 2018-02-23T19:57:43.783