đĄď¸AdGuard Home adblocker with config optimized for enhanced performance and usabilityđĄď¸
1M+
AdGuard Home is a network-wide software for blocking ads and tracking. After you set it up, it'll cover ALL your home devices, and you don't need any client-side software for that.
This docker image is based on the official adguard/adguardhome image with settings optimized for enhanced performance and usability.

By default DNS port 53 is used by resolved daemon so we need to disable it first:
sudo sh -c 'echo "DNS=127.0.0.1\nDNSStubListener=no" >> /etc/systemd/resolved.conf' && sudo systemctl restart systemd-resolved.service
Use the following command to create a new container and run AdGuard Home:
sudo docker run --name adguardhome\
--restart unless-stopped\
-v /my/own/workdir:/opt/adguardhome/work\
-v /my/own/confdir:/opt/adguardhome/conf\
-p 80:80/tcp\
-p 53:53/tcp -p 53:53/udp\
-d adam9999/adguardhome
Now you can open the browser and navigate to http://127.0.0.1/â â with default login credential admin/password.
All exposed ports are listed below:
-p 80:80/tcp: admin panel.
-p 53:53/tcp -p 53:53/udp: plain DNS.
-p 67:67/udp -p 68:68/tcp -p 68:68/udp: add if you intend to use AdGuard Home as a DHCP server.
-p 443:443/tcp -p 443:443/udp: add if you are going to use DNS-over-HTTPSâ server.
-p 853:853/tcp: add if you are going to run AdGuard Home as a DNS-over-TLSâ server.
-p 784:784/udp -p 853:853/udp -p 8853:8853/udp: add if you are going to run AdGuard Home as a DNS-over-QUICâ server. You may only leave one or two of these.
-p 5443:5443/tcp -p 5443:5443/udp: add if you are going to run AdGuard Home as a DNSCryptâ server.
If you want to use AdGuardHome's DHCP server, you should pass --network host argument when creating the container:
docker run --name adguardhome --network host ...
Content type
Image
Digest
sha256:bd658fa75âŚ
Size
24 MB
Last updated
about 2 years ago
docker pull adam9999/adguardhome