unfortunately besides some more shitty things the Pi-Hole Addon is gone forever since years.
Adguard Home is a really kiddy solution but preferred by big chief Frenck. For me Adguard is a piece of crap.The internal DNS resolution is shitty and the resolution time is for U10 script kiddies.
Do you have a How-To for that?
I am running a x86 installation and really don’t know how to get custom docker containers in that capsulated installation.
You would need to change your install method from HAOS to HA Core in docker or VM but will lose ability to use addons. You will need to install and manage each addon separately.
I prefer docker install. This site explains method and requirements, although the site makes the complicated more complicated.
BASICALLY
Backup HA >> install Linux >> install docker >> recommend install portainer to manage docker >> install HA in docker >> verify you can get to HA login screen >> restore HA config
Losing addons is a bad idea - use a VM: one for HAOS and one for Pi-hole. This is what I have, but am planning to move from VirtualBox to Proxmox (a web interface to a server is a better option as Ubuntu Remote Desktop is flaky, and autostarting VirtualBox containers is also flaky imo).
But preferably put Pi-hole on a physical box of its own. With your main router using pi-hole for DNS, any reboots/outages also takes out your internet access for a while. This is what I will do when I pull my finger out.
Is this just requesting that Pi-Hole be cooked into HA through the actual Add-Ons? I use the extension and run Pi-Hole on a separate system (VM) and the extension works great. Until I moved it I ran Pi-Hole & Homebridge on one rPi and HA on another.
IPv4 works like a charm but I am not able to have it work using IPv6. I included the IPv6 address and stamp of the DNS in the config but it seems that the pi-hole docker container (running on HA yellow) does not have an IPv6 address. Any idea how to fix this?
Is there any way to access the pi-hole container using the remote app? This would make it a lot easier to, e.g., with pi-hole of for a couple minutes if needed.
Personally I think this is the way to go anyway. Pi-Hole covers your whole network, so it really shouldn’t be dependent on your HA box running. I’ve had it on an old RPi3 for years now and haven’t even had to think about it other than updating it occasionally. The integration works fine to monitor (and disable) it.
I run two PiHoles: one as a container on the same NAS that runs HA (also in a container); and the other as a “bare metal” installation on an old Banana Pi M1 that is also a Spotify client.
Router includes both IP addresses in DHCP, so if one goes down whilst being upgraded, the other is still available.
And it’s really not difficult to use! Pi-hole is running great as a Docker container, and Docker is an officially supported installation method for Pi-Hole.
I’m running my Pi-Hole on an old Pi3 (used an old Pi2, worked great as well, but the Pi2 broke) more or less exclusively and it works like a charme! As @Troon said, I think Pi-Hole should be worth its own machine, as it will be one of very few integral parts of your home setup.
That’s why Docker is so easy to use. You “pull” the new container(s), before you do the “recreate”.
> docker compose pull
> docker compose up -d --force-recreate
I can see the use of two installations, but that’s a wanted “overkill”. Not necessary, but cool to have!