I’m not an expert, but I’m pretty sure anything in docker has the same IP (externally to the network) as the host machine running the container, and then has an internal “docker network” IP that’s typically 172.x.x.x
. So if you are blocking ports that are used by a docker container (which a VM shouldn’t do, since it has it’s own IP), you can just change which ports a docker container exposes, externally to the host machine.
But in any case, if HassOS is not available, regardless of pihole, then that’s probably where the issue is.
A few questions that might help getting closer:
- Do you set a static IP, make an IP reservation for the HassOS VM, or is IP dynamically assigned?
- Can you see the HassOS IP appear on the network (either in the router settings, or when running
nmap 192.168.0.0/24
from the CLI)? Can youping
HassOS IP? - What does
virsh net-list
show? I saw that at least one person who needed to remove the default bridge before it worked (described here) - When you do this with the router as DHCP, does everything else than HassOS and pihole work as expected?