Run AdGuardHome rootless and distroless.
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 won't need any client-side software for that.
What can I do with this? This image will run AdGuard-Home rootless and distroless, for maximum security and performance.
Why should I run this image and not the other image(s) that already exist? Good question! Because ...
Important
- ... this image runs rootless as 1000:1000
- ... this image has no shell since it is distroless
- ... this image has a health check
- ... this image runs read-only
- ... this image is automatically scanned for CVEs before and after publishing
- ... this image is created via a secure and pinned CI/CD process
- ... this image is very small
If you value security, simplicity and optimizations to the extreme, then this image might be for you.
Below you find a comparison between this image and the most used or original one.
| image | 11notes/adguard:0.107.63 | adguard/adguardhome:latest |
|---|---|---|
| image size on disk | 15.2MB | 74.2MB |
| process UID/GID | 1000/1000 | 0/0 |
| distroless? | ✅ | ❌ |
| rootless? | ✅ | ❌ |
dns:
bind_hosts:
- 0.0.0.0
ratelimit: 0
aaaa_disabled: true
all_servers: true
upstream_dns:
- 9.9.9.10
bootstrap_dns:
- 9.9.9.10
cache_size: 1073741824
max_goroutines: 1024
hostsfile_enabled: false
dhcp:
enabled: false
http:
address: 0.0.0.0:3000
session_ttl: 720h
querylog:
enabled: true
file_enabled: true
size_memory: 8
dir_path: /adguard/var
users:
- name: admin
password: $2b$12$xzIFiVMrq2jv5NH5pNNQSuEK84FDNI4PoiJbKIhZqUe1Ld/v1BI9W
auth_attempts: 3
block_auth_min: 60
filtering:
blocking_mode: nxdomain
cache_time: 1440
filters_update_interval: 24
blocked_response_ttl: 3660
protection_enabled: true
clients:
persistent:
- name: dnslookup
ids:
- 127.0.0.1
ignore_querylog: true
ignore_statistics: true
log:
enabled: true
file: ""
max_backups: 0
max_size: 100
max_age: 3
compress: false
local_time: true
verbose: false
schema_version: 29The default configuration contains no special settings, except ignoring the dnslookup health check in the statistics and as a client to not pollute your UI or statistics. Consider replacing it with your own or start the container with the default one and start changing what you need. The configuration will be updated with your settings if you use the mentioned volumes below. It is recommended to always add the exception for dnslookup.
clients:
persistent:
- name: dnslookup
ids:
- 127.0.0.1
ignore_querylog: true
ignore_statistics: true- /adguard/etc - Directory of the configuration file
- /adguard/var - Directory of database and query log files
name: "adguard"
services:
adguard:
image: "11notes/adguard:0.107.63"
read_only: true
environment:
TZ: "Europe/Zurich"
volumes:
- "etc:/adguard/etc"
- "var:/adguard/var"
tmpfs:
# tmpfs volume because of read_only: true
- "/adguard/run:uid=1000,gid=1000"
ports:
- "53:53/udp"
- "53:53/tcp"
- "3000:3000/tcp"
networks:
frontend:
sysctls:
# allow rootless container to access ports < 1024
net.ipv4.ip_unprivileged_port_start: 53
restart: "always"
volumes:
etc:
var:
networks:
frontend:| Parameter | Value | Description |
|---|---|---|
user |
docker | user name |
uid |
1000 | user identifier |
gid |
1000 | group identifier |
home |
/adguard | home directory of user docker |
login |
admin // adguard | login using default config |
| Parameter | Value | Default |
|---|---|---|
TZ |
Time Zone | |
DEBUG |
Will activate debug option for container image and app (if available) |
These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.
It is of my opinion that the :latest tag is dangerous. Many times, I’ve introduced breaking changes to my images. This would have messed up everything for some people. If you don’t want to change the tag to the latest semver, simply use the short versions of semver. Instead of using :0.107.63 you can use :0 or :0.107. Since on each new version these tags are updated to the latest version of the software, using them is identical to using :latest but at least fixed to a major or minor version.
If you still insist on having the bleeding edge release of this app, simply use the :rolling tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!
docker pull 11notes/adguard:0.107.63
docker pull ghcr.io/11notes/adguard:0.107.63
docker pull quay.io/11notes/adguard:0.107.63
Important
This image is not based on another image but uses scratch as the starting layer. The image consists of the following distroless layers that were added:
- 11notes/distroless - contains users, timezones and Root CA certificates
- 11notes/distroless:dnslookup - app to execute DNS queries
Tip
- Use a reverse proxy like Traefik, Nginx, HAproxy to terminate TLS and to protect your endpoints
- Use Let’s Encrypt DNS-01 challenge to obtain valid SSL certificates for your services
Caution
- This image comes with a default configuration with a default password for the admin account. Please set your own password or provide your own configuration.
This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the releases for breaking changes. If you have any problems with using this image simply raise an issue, thanks. If you have a question or inputs please create a new discussion instead of an issue. You can find all my other repositories on github.
created 04.07.2025, 14:27:10 (CET)