Hello everyone,

 

I have an issue that isn't new. I had this issue on 6.11 and even other version before that and I think it's about time I start talking about it so we can find how to solve it.

 

Randomly, my docker will stop being able to access device across network. Here's my exemple:

 

I have a mongodb set on my custom network "my-bridge". It's a normal custom network, nothing fancy. Mostly all my docker are on that network.

 

Then, I have another docker, for exemple unifi and pihole, set on br0/eth0 macvlan. This one have an ip that is the same range as my server. 

 

In normal operation, I can go into my unifi docker shell and ping my unraid server ip, other docker and computer on the same network (docker pihole, router, etc) and I can also reach dockers on other network like mongodb (which in the end sit at my server ip).

 

Now, when host access to custom network fail, 2 things happen.

 

First, my unifi and pihole container cannot talk anymore to my unraid server (and at the sametime all docker in my custom network my-bridge). If I try to ping my unraid server, it fail.

 

At the sametime, all my dockers not on the macvlan also cannot communicate with these docker. Found out the hard way this was the problem with many container that were having weird problem in DNS resolution (everyone was pointing to my pihole and I had firewall redirection to pihole) was because of that.

 

The fix is simple by have impact. I must turn off docker, disable host access network, apply, enable host access, apply, then start docker and everything start working again. Problem is, it will eventually fail.

 

So my big question, when it will happen, what you guys need me to get out of there? I won't be right in front of it when it happen so I won't be able to say "it happen at 2:15am", but I'll at least know when. I do have syslog on a share and I can get diagnostic. I know this is the normal procedure for bug report, my goal here is since it's a random bug, I want to maximize my change to give all the information that could be needed. If I need to enable something right now while it's working to see it fail, I'll do it.

 

Thank you

Does it still happen on 6.12.6? There were some major changes in the docker network in the past few versions.

I didn't update yet, I'm on 6.12.5 for now and since it's random, I could wait as far as many months before it occur back. I honestly though it was past issue until I stumble upon other docker that showed weird behavior

I still have this issue in V7.0.0

I have to turn off Docker, flip the access to custom networks on then off, then restart docker. It happened twice today.

I am still having this issue in v7.1.2