Docker erroring on br0

[ErikRedbeard]

Can't get docker to see network type br0.

br0 works fine for my VMs (which is the main reason I use it), but I also want one of my dockers to have it's own dedicated IP on my local network through br0.

 

I've been trying to get my docker to see the br0 bridge, but it keeps erroring on the br0 interface.

If I disable br0 and run either bond0 or eth0 as a custom network they work without issues and show up under the dockers as network type.

 

This error appears when I start docker with br0 as a custom network:

Sep 10 14:38:14 UNRAID-Redbeard rc.docker: Error response from daemon: network dm-3fedf868ec10 is already using parent interface br0

 

My question is if anyone has any idea how to progress from here to get docker working with the br0 network.

 

I'm including my network settings, docker settings and part of the log when starting docker.

 

 

System Log (docker start only):

Sep 10 14:38:10 UNRAID-Redbeard ool www[9139]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply'
Sep 10 14:38:10 UNRAID-Redbeard emhttpd: Starting services...
Sep 10 14:38:10 UNRAID-Redbeard emhttpd: shcmd (4000): /etc/rc.d/rc.samba restart
Sep 10 14:38:10 UNRAID-Redbeard winbindd[6022]: [2020/09/10 14:38:10.476434,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
Sep 10 14:38:10 UNRAID-Redbeard winbindd[6024]: [2020/09/10 14:38:10.476438,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
Sep 10 14:38:10 UNRAID-Redbeard winbindd[6024]:   Got sig[15] terminate (is_parent=0)
Sep 10 14:38:10 UNRAID-Redbeard winbindd[6022]:   Got sig[15] terminate (is_parent=1)
Sep 10 14:38:10 UNRAID-Redbeard winbindd[7186]: [2020/09/10 14:38:10.476861,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
Sep 10 14:38:10 UNRAID-Redbeard winbindd[7186]:   Got sig[15] terminate (is_parent=0)
Sep 10 14:38:12 UNRAID-Redbeard root: Starting Samba:  /usr/sbin/smbd -D
Sep 10 14:38:12 UNRAID-Redbeard root:                  /usr/sbin/wsdd 
Sep 10 14:38:12 UNRAID-Redbeard smbd[9578]: [2020/09/10 14:38:12.629945,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Sep 10 14:38:12 UNRAID-Redbeard smbd[9578]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Sep 10 14:38:12 UNRAID-Redbeard root:                  /usr/sbin/winbindd -D
Sep 10 14:38:12 UNRAID-Redbeard winbindd[9591]: [2020/09/10 14:38:12.661067,  0] ../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache)
Sep 10 14:38:12 UNRAID-Redbeard winbindd[9591]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Sep 10 14:38:12 UNRAID-Redbeard winbindd[9591]: [2020/09/10 14:38:12.661409,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Sep 10 14:38:12 UNRAID-Redbeard winbindd[9591]:   daemon_ready: daemon 'winbindd' finished starting up and ready to serve connections
Sep 10 14:38:12 UNRAID-Redbeard emhttpd: shcmd (4013): /usr/local/sbin/mount_image '/mnt/user/Docker/docker.img' /var/lib/docker 20
Sep 10 14:38:12 UNRAID-Redbeard kernel: BTRFS info (device loop2): using free space tree
Sep 10 14:38:12 UNRAID-Redbeard kernel: BTRFS info (device loop2): has skinny extents
Sep 10 14:38:12 UNRAID-Redbeard kernel: BTRFS info (device loop2): enabling ssd optimizations
Sep 10 14:38:12 UNRAID-Redbeard root: Resize '/var/lib/docker' of 'max'
Sep 10 14:38:12 UNRAID-Redbeard emhttpd: shcmd (4015): /etc/rc.d/rc.docker start
Sep 10 14:38:12 UNRAID-Redbeard root: starting dockerd ...
Sep 10 14:38:14 UNRAID-Redbeard rc.docker: Error response from daemon: network dm-3fedf868ec10 is already using parent interface br0
Sep 10 14:38:14 UNRAID-Redbeard kernel: device br0 entered promiscuous mode

 

 

Edited September 10, 2020 by ErikRedbeard

[ErikRedbeard]

Ended up resorting to removing the docker.img and creating a new one and reinstalling all the dockers.
This solved the issue for me.

 

Looked to me like there was a rogue network that didn't even show up with "docker network ls".