search

losuler / pihole-dnscrypt-docker

A docker-compose for Pi-hole and DNSCrypt, daemonized with a systemd service file.
GNU General Public License v3.0
55 stars 14 forks source link

Pihole not resolving DNS requests #4

Open dcale opened 3 years ago

dcale commented 3 years ago

While using your docker-compose it seems like the Pihole container is not starting properly (it does however bind to 53). Here the logs is see in the container (repeating over and over again):

pihole      | Stopping pihole-FTL
pihole      | kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
pihole      | Starting pihole-FTL (no-daemon) as root
losuler commented 3 years ago

I'm not having the same issue on the same machine I'm running this docker-compose on (Debian 10). Are the images up to date? (sudo docker-compose pull)

Knowing what distro and release you're running this on might be helpful too.

dcale commented 3 years ago

It's a Ubuntu 20.04.1 LTS Host. The images are up to date. It's also worth mentioning that it was working for a short amount of time.

losuler commented 3 years ago

I apologise for not being able to look into this sooner (I personally don't run any Ubuntu hosts), but someone else here had an issue with a port conflict on Ubuntu 20.04.1 LTS, of which steps I tested in a reply that resolved the issue.

I'm not sure if you're still having issues or whether you're still using this docker-compose, but I suggest you try this if you haven't.

I did note you said the PiHole container does seemingly bind to port 53 in your case, but I thought I'd mention this in case it helps. I wasn't able to reproduce your issue otherwise.