Specify docker daemon network bridge IP

[pH1L (Philipp Gille)]

Docker uses the default “172.17.0.0/16” subnet for container networking. If your network already uses this subnet you have to change it. Usually I do this with the configuration file at “/etc/docker/daemon.json” (e.g. “bip”: “192.168.3.5/24”).

dockerd

Is there any way to do this in “Home Assistant OS” ? Something like a “file overlay” which will be there after an update or reboot?

I assume this is the problem for some issues which have been reported here. Like this one

Hass.io on RPI3B+ not reachable on 172.17/16 network

Installed hassos_rpi3-2.12.img multiple times, on two different microSD cards and using two different versions of Etcher, but issues remain: After first boot of the RPi Hassio seems to complete its update process and is accessible via console (attached keyboard and monitor), but not via the network. Using the config/network/my-network file I set the eth0 address to 172.17.140.100 (on my 172.17./16 network). I see this Ip address come alive on the (wired) network, and pinging it works for app. …

[MarcLIMON (Marc)]

Thanks, Philipp !

[MischaBoender (Mischa)]

Same issue here. Running HASSOS on VMWare and had to put 3 NICs in my VM to be able to access my 3 networks (LAN, DMZ and IOT) in different 172.17.x.x subnets.

Why on earth does docker need a /16? Would also like to know how to change this.

[gr2659 (Grant)]

So… it looks like creating the daemon.json file per this post works:

Change docker0 network from 172.16.0.0/16 due to IP conflict

Actually I think I deviated and forget you not using docker but using VM with HASS OS(docker). In this case portainer and above cannot help but the .json suggestion still should. Originally I realize the VM but I forgot when I look back at this question. I will look at HASSOS and check this on one of my RasPi with HA to see where this file live and how changes affect it. I beileve this should be similar enough to your issue.

I just did so, rebooted and I’m up and running. I can reach my 172.16.0.100 HASS install from my 172.17.0.0/16 network and HASS can now see my devices on that network, too!