Sorry, I figured this out yesterday afternoon but then I got the phone call that my 12-year old roof needs to be completely replaced again and in my fury and subsequent sadness + a strong drink, I completely forgot that I was going to come back here and tell you.
I went to the Discord channel to ask where Frenck and paul_sinclair led me around to understand that I failed the first rule of addon-adguard-home… RTFM. The readme (https://github.com/hassio-addons/addon-adguard-home/blob/edd538a6e1c90150c99fac9c308c95f557fc95e1/adguard/DOCS.md) on line 1 warns " Ensure your Home Assistant device has a static IP and static external DNS servers! This is important! You WILL end up having issues if you skip this step. Also, please note, setting a fixed IP in your router is NOT static."
I, of course, had Adguard Home and had set my router to give out a static DHCP lease to the HA machine figuring that was good enough. I also had the router giving out the DNS server as the HA machine itself since it was running the Adguard Home server.
So I tried what you suggest there. I was able to do
apk add --no-cache php7=7.3.18-r0 --repository=http://18.104.22.168/alpine/edge/main --repository=http://22.214.171.124/alpine/edge/community and it worked just fine. IP addresses fine. All signs pointing to DNS.
Then after a bunch more messing around and failboating in the Discord channel with Frenck and paul-sinclair watching, they guided me a bit as I used the root login on the HA device itself, used the
login command to drop into the base os, then used
nmcli to set the IP address directly into the device and gave it 126.96.36.199 as a DNS server instead of using itself with the Adguard Home container. (This is the directions I found on how to do
And then because I messed up the box flailing with some combination of
service to get it to take… I rebooted the thing and everything worked.
I changed the add-on to take out the IP address repositories and I was able to
apk add to my heart’s content and
curl on any domain name.
So yeah. That’s the moral of the story: Your HA device needs a real IP and DNS set statically into it, no DHCP reservation, and can’t use itself as a DNS server via Adguard Home. If you make that mistake, you will have an impossible time building add-ons.