After updating to 7.0.1 from 7.0.0 recently, my dockers connected to my br0 network stopped being accessible, both through ngnix and the local network.

I'd had a similar issue before, which I solved by deleting the network.cfg file and allowing unRaid to rebuild it. I tried this again, but am having an entirely new problem

 

Now br0 won't show up at all under 'Network Type' when I try to update my containers, and instead I have 'None' show up in the dockers which used to have br0 assigned.

I've tried deleting the network.cfg and changing my network settings around, but have had no luck. 

Currently I am using:

Docker settings:
- Docker custom network type: ipvlan
- Host access to custom networks: Enabled

- Preserve user defined networks: Yes
- IPv4 custom network on interface br0: Subnet: 192.168.1.0/24 Gateway: 192.168.1.1 DHCP pool: not set

 

Network Settings:

- Enable bonding: No

- Enable bridging: Tes

 

Can someone please help me figure this out?

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

Sorry about that, I appreciate you letting me know I forgot to add that! Here is my diagnostics file.

mhdpc-diagnostics-20250227-1744.zip

So it's resolved?

It is not, I'm still unable to set any of my dockers to br0... here are my interface details. This is the only place I'm able to see br0 referenced

Edited February 28, 20251 yr by HDodd

8 minutes ago, HDodd said:

It is not

So why did you change the topic title to [Solved]?

Post a screenshot from the docker settings page, with the docker service stopped.

Here's the screenshot you requested

Looks OK to me, which options show up for container network? You can also try recreating the docker image, in case it helps.

and I apologize for the title, I must've copied that by mistake

The behavior is the same as the issue here:
  https://docs.unraid.net/unraid-os/release-notes/7.0.0/#issues-using-docker-custom-networks

Even though the settings look correct, it feels like there is an issue with this:

On Settings -> Docker Settings, try this: disable Docker, then remove the checkbox next to "IPv4 custom network on br0" and Apply. Then re-add the checkbox and Apply. Enable Docker and see if that helps?
 

I just tried that and unfortunately nothing changed... Would checking the DHCP Pool checkbox help at all?

Mhmmm. When docker is running, you could try to remove the existing br0 (there must be one cause docker creates one upon start)

 

docker network rm br0

then stop the docker service and then start it again

When I enter that into the console I get : "Error response from daemon: network br0 not found"

42 minutes ago, HDodd said:

When I enter that into the console I get : "Error response from daemon: network br0 not found"

now that is very strange. 

but i might have found your issue.



Feb 27 01:39:37 mHDPC root: Error response from daemon: network di-b3c2cf3baf6e is already using parent interface br0

So one of your custom networks highjacks br0


Edit: To make absolutely sure, i recreated the circumstance and yes. That is your issue
I created a bogus network via 
 

docker network create -d ipvlan --subnet=10.0.1.0/24 --gateway=10.0.1.1 -o parent=br0 test

and the result is the missing br0 interface upon docker start

 

Feb 28 19:51:47 Tower rc.docker: Starting network...
Feb 28 19:51:47 Tower root: Error response from daemon: network di-661d5701ce59 is already using parent interface br0

 

Edited February 28, 20251 yr by Mainfrezzer

Okay, what do I need to do to identify which custom network is causing the issue? I've used 'docker network ls' to list them, but none of the IDs match with the above id you found. Are these re-generated every launch?

you have to go through them 1 by 1 with 

"docker network inspect NAME" and then see whos parent is br0

I've checked all of the netowrks shown in the list and none of them show a parent of br0... here is the text from my console. I searched for br0 after inspecting every network and found nothing

dockerNetworkInspectLog.txt

Would giving br0 a new subnet help? (192.168.3.0/24 instead of 192.168.1.0/24)

I'd like to avoid that if I can, but I'm open to any options and really appreciate the help you all have given so far

Not sure if this is helpful, but here:

This is getting really strange. At this point it might be easier to recreate the docker image

If you stop docker and start it again. Grab the output from the syslog after 
rc.docker: Docker daemon...  Started.
rc.docker: Starting network...


and if there is a message with "is already using parent interface br0" again

take the name, thats displayed, in the syslog message. As it was "network di-b3c2cf3baf6e" before and then type "docker network rm b3c2cf3baf6e"

obviously, you need to change it for whatever its gonna display in the syslog.

Interestingly enough the network id is unchanged after restarting docker

"Feb 28 17:32:39 mHDPC root: Error response from daemon: network di-b3c2cf3baf6e is already using parent interface br0"

And even more strange is this: "Error response from daemon: network b3c2cf3baf6e not found"

Even though the log specifically calls out that network above, it also claims it is not found...

What do I need to do to recreate my docker image? Just delete the docker.img file and reinstall previous apps from CA?

So I completed the above and br0 is now back, but my VPN connection no longer shows up when adding/updating docker containers... It still shows up in the VPN manager, and is able to handshake/ping, but I can't connect any of my containers to the VPN now