{"id":1525,"date":"2017-02-06T10:00:17","date_gmt":"2017-02-06T09:00:17","guid":{"rendered":"https:\/\/www.nico-maas.de\/?p=1525"},"modified":"2017-02-04T17:27:33","modified_gmt":"2017-02-04T16:27:33","slug":"how-to-run-pi-hole-in-a-docker-container","status":"publish","type":"post","link":"https:\/\/www.nico-maas.de\/?p=1525","title":{"rendered":"How to run pi-hole in a Docker container"},"content":{"rendered":"

Pihole is an awesome little DNS Server with Blacklists for Ad Sites and the ideal tool to install a small and powerful ad filter for the whole network (Intro Video here<\/a>).<\/p>\n

As diginc designed an Docker Image around the Pihole server (which was normally run on a RPi :)) - and made it x86, you can also run it on your normal Homeserver :)!<\/p>\n

Important things just before we start: The Docker container needs to bind to ports 53 (DNS) and 80 (HTTP) - so, if you need to run your own DNS - that could interfere. If you need port 80 for some other website - you'll have to make an reverse proxy.<\/p>\n

To make the setup easier, I wrote an little docker-compose.yml:<\/p>\n

pihole:\r\n  restart: unless-stopped\r\n  container_name: pihole\r\n  image: diginc\/pi-hole:alpine\r\n  volumes:\r\n    - \/var\/pihole:\/etc\/pihole\r\n  environment:\r\n    - ServerIP=YOURLANIPHERE\r\n  cap_add:\r\n    - NET_ADMIN\r\n  ports:\r\n    - \"53:53\/tcp\"\r\n    - \"53:53\/udp\"\r\n    - \"80:80\"<\/pre>\n
You'll need to change the YOURLANIPHERE to the IP Address of your Servers LAN Interface - and you'll need to create the folder \/var\/pihole and make it writable for your Docker User.<\/p>\n
sudo mkdir \/var\/pihole\r\nsudo chown -R MYLINUXUSER:MYLINUXUSER \/var\/pihole<\/pre>\n
After that, we can start the service via docker-compose up -d.<\/p>\n
You'll have access to the Web interface of pihole on YOURLANIPHERE\/admin<\/p>\n
However, this interface is NOT protected - so we'll do this now:<\/p>\n
docker exec -it pihole \/bin\/bash\r\n# create an password protection for your pihole web interface\r\npihole -a -p somepasswordhere\r\n# You can also remove the password by not passing an argument.\r\npihole -a -p\r\n<\/pre>\n
Also, pihole does create a lot of log files, which should be removed from time to time, the block lists should be updated and pihole itself should be updated. This can also be achieved via an cron file, available here<\/a>.<\/p>\n
# [...]\r\n\r\n# Your container name goes here:\r\nDOCKER_NAME=pihole\r\nPATH=\/usr\/local\/sbin:\/usr\/local\/bin:\/sbin:\/bin:\/usr\/sbin:\/usr\/bin\r\n\r\n# Pi-hole: Update the ad sources once a week on Sunday at 01:59\r\n#          Download any updates from the adlists\r\n59 1    * * 7   root    PATH=\"$PATH:\/usr\/local\/bin\/\" docker exec $DOCKER_NAME pihole updateGravity > \/dev\/null\r\n\r\n# Update docker-pi-hole by pulling the latest docker image ane re-creating your container.\r\n# pihole software update commands are unsupported in docker!\r\n30 2    * * 7   root    PATH=\"$PATH:\/usr\/local\/bin\/\" docker exec $DOCKER_NAME pihole updatePihole > \/dev\/null\r\n\r\n# Pi-hole: Flush the log daily at 00:00 so it doesn't get out of control\r\n#          Stats will be viewable in the Web interface thanks to the cron job above\r\n00 00   * * *   root    PATH=\"$PATH:\/usr\/local\/bin\/\" docker exec $DOCKER_NAME pihole flush > \/dev\/null<\/pre>\n
I actually did just open\u00a0my cron with crontab -e and entered the last lines into there - so that should work. You can now test your new Adblocker by entering the IP of your Server as DNS on your Clients - and if you're happy with it, just replace the DNS server entry on your DHCP server with that IP - to rollout pihole to your complete network :).<\/p>\n
 <\/p>\n
More Info:<\/p>\n
https:\/\/github.com\/diginc\/docker-pi-hole<\/a><\/p>\n
https:\/\/discourse.pi-hole.net\/t\/how-do-i-set-or-reset-the-web-interface-password\/1328<\/a><\/p>\n
https:\/\/www.reddit.com\/r\/pihole\/comments\/5rudb3\/running_pihole_in_a_docker_container\/<\/a><\/p>\n