The Hidden Network Conflict: Update

A couple of weeks ago I was playing around with some new dockers but this resulted in messing up some of my Home Assistant integrations.

I use Portainer to deploy some new dockers and it seemed that when creating those Dockers, a new network was created. That network had the same IP segment as my IoT VLAN and upon deleting that, everything started working again.

The funny part was that the issue was limited to a part of the IoT VLAN. Some devices were working just fine without any issues and some weren’t!

When reviewing the issue, it all made sense now. This network was created on my Raspberry Pi and that’s the reason why it couldn’t route the traffic back to Home Assistant for the dockers running on the same host.

Now with this information I need to make sure to exclude my IoT IP range from Portainer. ChatGPT suggested to modify the Docker Daemon Configuration using sudo nano /etc/docker/daemon.json with the following commands.

{
  "default-address-pools": [
    {
      "base": "172.17.0.0/16",
      "size": 24
    }
  ],
  "bip": "192.168.1.1/24"
}

This should prevent Docker from automatically assigning networks in my IoT range. The "bip" setting ensures Docker’s default bridge network is within a different subnet. Since this is my live environment I’ll not test it out yet, but perhaps the easiest way to do this is per container? I just need to specify the IP ranges as well.

So far I haven’t found any simpler solution, but should you know any, just let me know! 😉