


docker run -name adguardhome -v /srv/config/AdguardHome/workdir:/opt/adguardhome/work -v /srv/config/AdguardHome/confdir:/opt/adguardhome/conf -net=host -p 67:67/udp -p 80:80/tcp -p 443:443/tcp -p 853:853/tcp -p 3000:3000/tcp -d -restart unless-stopped adguard/adguardhome Optional: If you have something running on port 3000 already, feel free to change it to a different port. It will also tell it to automatically restart unless you manually stop the container, which is very useful in case you ever restart your Docker VM. This docker command will automatically download the image in the specified path. To deploy Adguard Home as a docker container, simply SSH into your host and run the below command. Oh, and I also like the idea of running it in Docker instead of having to purchase another rasperry pi. The only reason I’m switching to Adguard Home is because I repuposed my raspberry pi to be used with home assistant. I’ve added PiHole to my Organizr, Heimdall, and Homer dashboards. I’ve been using PiHole for the last 6 months or so on a raspberry pi 3 B+ without any issues at all.

I’m not going to go into the details of whether or not Adguard Home or PiHole is better, but if you are curious, Adguard has created a comparison chart so you can make the decision yourself: Basically, once it’s setup you will add the IP address of your Adguard Home DNS server to the IP address settings of each computer in your house, or add it as primary DNS in your router – automatically blocking ads across all devices in your home. This guide assumes you already have Docker installed and have SSH access to your Ubuntu server.Īdguard Home is a network-wide ad and tracker blocker. Adguard Home is a great Pihole alternative for the self-hosted users who would rather setup DNS ad blocking via a container instead of a raspberry pi. Are you looking for a step by step guide to deploy Adguard Home in Docker? If so, then you’ve come to the right place.
