Jump to content
subagon

[Solved] Missing br0 interface in GUI

18 posts in this topic Last Reply

Recommended Posts

unRAID 6.4.0

Supermicro - X9DRD-7LN4F with 4 NICs

 

I have a couple of dockers that I had setup and working that I had bridged to their own IP addresses. My NICs were all bonded together in active-backup mode. I messed around with the network setting to setup some of the NICs as separate interfaces. Somewhere in this process the br0 interface was deleted/disappeared. I put everything back to the way it was before (I think), but the br0 is gone from the GUI. Here's a sample from the log file;

 

Jan 23 10:47:25 asok root: pihole: Error response from daemon: network br0 not found Error: failed to start containers: pihole

And some screenshots below.

 

Reboot server a few times, started and stopped docker and VM service many times...

 

How do I get br0 back?

 

 

 

 

 

01.jpeg

02.jpeg

03.jpeg

Edited by subagon
added content

Share this post


Link to post

Some more info after reading this post https://lime-technology.com/forums/topic/61006-how-to-setup-ips-for-dockers/

 

root@asok:~# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
32176c05a279        bridge              bridge              local
7ce2002afcd5        host                host                local
5b8a210f2546        none                null                local
root@asok:~# docker network create -d macvlan --subnet=192.168.1.0/24 --gateway=192.168.1.1 -o parent=br0 br0
Error response from daemon: network dm-2f4a429bc5a3 is already using parent interface br0
root@asok:~# docker network rm dm-2f4a429bc5a3
Error response from daemon: network dm-2f4a429bc5a3 not found

 

Share this post


Link to post
2 hours ago, subagon said:

How do I get br0 back?

 

Do the following to let docker rebuild the networks

rm /var/lib/docker/network/files/local-kv.db
/etc/rc.d/rc.docker restart

 

Share this post


Link to post

bonienl,

 

The commands restored the br0 interface and all my dockers are working again. If you're ever in Tampa, Florida, the beer is on me.

Edited by subagon

Share this post


Link to post

bonienl,

 

One more question...

 

As I said, my motherboard has 4 NICs. I now have eth0 setup to bridge and therefore have the br0 interface. I've turned off bonding (this server is in my home and I don't need redundancy). So I now have the following interfaces showing up on the Network Setting page;

 

  • br0
  • br1
  • eth2
  • br3

 

I want to use br0, br1, and br3 for various dockers plus file sharing off of eth0/br0. I'd like to put Plex on eth2 all by itself.

 

The problem is I can only see Bridge, Host, None, and br0 when editing the Plex (or any) docker. I tried the commands you provided above, but without any luck. How can I add br1,eth2, and br3 to the drop down list or manually edit the Plex docker file to use eth2?

 

Thanks

Edited by subagon

Share this post


Link to post

You'll need to have an IP assigned to the interface you want to show up Docker network drop down. This will be fixed in a future release according to @bonienl

Or you'll need to have the docker network manually recreated every startup of the docker service.

caveat: If you have multiple interfaces with ip addresses in the same subnet (and are physically on the same LAN), some protocols are known to misbehave - I think Samba (Windows File Shares) is one of those. This is because broadcast and discovery sometimes get confused.

caveat: The host cannot talk to dockers on the same interface as itself, so if br0 has an IP of 192.168.1.10, br1 has an IP of 192.168.1.11, container A is on br1 with ip of 192.168.1.110. Container A will fail to talk to 192.168.1.11 and vice versa. This is by design. Container A needs to talk to unRAID using 192.168.1.10 and 192.168.1.10 only. However, any protocol that uses discovery and broadcasting will potentially be confused and try to use the wrong IP at times, resulting in flaky behavior.

 

To manual create a docker network and use it with the Plex docker container see this topic:

 

Edited by ken-ji
Corrected the reference post with details for 6.4

Share this post


Link to post

for me this solution works but it is not permanent after restarting or restarting docker i have to do it again, why?

Share this post


Link to post

This fixed my issue.

On 1/23/2018 at 5:59 PM, bonienl said:

 

Do the following to let docker rebuild the networks


rm /var/lib/docker/network/files/local-kv.db
/etc/rc.d/rc.docker restart

 

 

Yes I also get the same issue but it is actually the Docker Execution error I am getting. 

 

 

Edited by witalit

Share this post


Link to post

I have no idea why this issue just start for me. i'm on 6.5.3 and after every reboot i now have to do this.

rm /var/lib/docker/network/files/local-kv.db
/etc/rc.d/rc.docker restart

I have also tried a new docker img with no fix after reboot

Capture.PNG

Edited by H2O_King89

Share this post


Link to post

I rebuilt my flash drive with unraid flash tool. But get the same issue when I reboot I lose br0 and I also upgraded to  6.6.0-rc4 to see if that would fix it...

 

Share this post


Link to post

Post you diagnostics file. I'm guessing there's something wrong in your config that's causing the docker to treat the br0 network as a custom definition and possibly purging it. You might also want to provide the screenshot of your docker network settings 'Settings | Docker'

Share this post


Link to post
11 minutes ago, ken-ji said:

Post you diagnostics file. I'm guessing there's something wrong in your config that's causing the docker to treat the br0 network as a custom definition and possibly purging it. You might also want to provide the screenshot of your docker network settings 'Settings | Docker'

 

king-unraid-diagnostics-20180918-1703.zip

Capture.PNG

Edited by H2O_King89

Share this post


Link to post

I don't see anything wrong. except there are 4 docker custom networks defined. docker0 and three br-* networks.

Can you run

docker network list

on the terminal?

Share this post


Link to post
root@KING-UNRAID:~# docker network list
NETWORK ID          NAME                DRIVER              SCOPE
9494a8ea6aac        br0                 macvlan             local
2b4bf512628e        bridge              bridge              local
e8e134764a20        host                host                local
27a6395f1007        none                null                local
0dd83d63baea        proxynet            bridge              local

 

Share this post


Link to post

This is weird. Other than the proxynet bridge, did you create any other bridges by cli?

because the bridges in your network interfaces (from the diags) named br-* do not line up with those the docker is reporting... only docker networks of type bridge can be seen with the ifconfig -a

Maybe @bonienl has some idea...

 

Share this post


Link to post
1 minute ago, ken-ji said:

This is weird. Other than the proxynet bridge, did you create any other bridges by cli?

because the bridges in your network interfaces (from the diags) named br-* do not line up with those the docker is reporting... only docker networks of type bridge can be seen with the ifconfig -a

Maybe @bonienl has some idea...

 

just that proxy net and have reboot with no issues for months then reboot a few days ago and started having this issue and found this topic.

Share this post


Link to post

Hi guys

 

I am getting the same issue, after changing motherboard to a supermicro C9-X299 PG-300F. The solution to restart the docker network works, but only untill reboot, then I have to manually do it again. Did you guys get it solved for you?

 

One thing that might be a clue is that on boot I get this message "RTNETLINK answers: Network is down". It waits for a bit but then proceeds to boot.

I have tried to disable all but one network interface (using LAN2, the one with shared IPMI) and I have disabled all VLANS.

 

Anyone has any ideas?

Share this post


Link to post
On 5/13/2018 at 4:22 PM, knex666 said:

for me this solution works but it is not permanent after restarting or restarting docker i have to do it again, why?

Started having this same exact problem today for the first time, one problem after another lately.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.