
Synology NAS with Docker (20.10.3-1239) and pi-hole version v5.6 (in Docker the PIHOLE_VERSION environment variable is 2021. done!Īs I've been trying to fix this most of the day, I came across several possible solutions, none of which really seemed to work for me, and I didn't want to use some scheduled task either, when it should be possible without. ::: Adding adlist sources to the whitelist. ::: 110427 unique domains trapped in the event horizon. ::: 133946 domains being pulled in by gravity. ::: Formatting list of domains to remove comments. sending all processes the KILL signal and exiting. You can also access the IP address of the container by running the IP address command. sudo docker exec it (docker ps l q) env grep ADDR.

The above example outputs 192.168.99.100, but this might be a different IP address on your machine. The following command returns the IP address of the last running container. ::: Docker start setup complete - beginning s6 services Enter the following command to get the IP address of the Docker Toolbox virtual machine: host> docker-machine ip default 192. ::: Testing DNSmasq config: dnsmasq: syntax check OK. "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", Using default DNS servers: 8.8.8.8 & 8.8.4.4ĭNSMasq binding to default interface: eth0 ::: No changes detected, transport skipped! ::: Starting docker specific setup for docker diginc/pi-holeĮRROR: To function correctly you must pass an environment variables of 'ServerIP' into the docker container with the IP of your docker host from which you are passing web (80) and dns (53) ports from executing container initialization scripts.


ensuring user provided files have correct perms.exited 0. making user provided files available at /var/run/s6/etc.exited 0. Because the impact on networking is often overlooked for new technologies, I figured I’d get a head start to understand the basics of Docker Networking. "value": "/opt/pihole:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
