search

chriscrowe / docker-pihole-unbound

Run Pi-Hole + Unbound on Docker
1.04k stars 270 forks source link

Issues with spinning up container #235

Closed louis-manabat closed 6 months ago

louis-manabat commented 6 months ago

Hi hi, I'm working on trying to spin up a dedicated Pi-hole server on a separate RPi4 I have, which is running Raspberry Pi OS.

I am able to spin up the container with no issues, but after going through the logs on Portainer, I get the following error ([✗] DNS resolution is currently unavailable). This error also appears if I try to update gravity via Pi-hole's UI. I ran the exact docker-compose config on my other RPi4 and it wasn't giving me these errors.

Another issue I am having is that I'm trying to set-up bind mounts as well for gravity-sync (snippet below) - I get the following error when trying to compare servers Hashing the remote Gravity Databasemd5sum: ~/.pihole/pihole/gravity.db: No such file or directory

volumes:
          - type: bind
            source: ~/.pihole/pihole
            target: /etc/pihole:rw
          - type: bind
            source: ~/.pihole/dnsmasq.d
            target: /etc/dnsmasq.d:rw

Any help would be greatly appreciated! Thanks

louis-manabat commented 6 months ago

Update: It seems I missed this reply: possible solution

I will have a look at that once I get home, but it looks promising. But will still need a better understanding with why gravity.db is not being created. Thanks!

Edit: The solution worked for me. Just the issue of gravity.db is left. Thanks!