Run AdGuardHome rootless and distroless.
50K+

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 ...
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 | size on disk | init default as | distrolessโ | supported architectures |
|---|---|---|---|---|
| 11notes/adguard | 17MB | 1000:1000 | โ | amd64, arm64, armv7 |
| adguard/adguardhome | 81MB | 0:0 | โ | 386, amd64, arm64, armv6, armv7, ppc64le |
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: 29
The 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. If using the default config, the container will set a new random password for the user admin at start and print it to the log only once!
clients:
persistent:
- name: dnslookup
ids:
- 127.0.0.1
ignore_querylog: true
ignore_statistics: true
name: "dns"
x-lockdown: &lockdown
# prevents write access to the image itself
read_only: true
# prevents any process within the container to gain more privileges
security_opt:
- "no-new-privileges=true"
services:
adguard:
image: "11notes/adguard:0.107.79"
<<: *lockdown
environment:
TZ: "Europe/Zurich"
volumes:
- "adguard.etc:/adguard/etc"
- "adguard.var:/adguard/var"
tmpfs:
# needed for read-only
- "/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:
adguard.etc:
adguard.var:
networks:
frontend:
To find out how you can change the default UID/GID of this container image, consult the RTFMโ .
| Parameter | Value | Description |
|---|---|---|
user | docker | user name |
uid | 1000 | user identifierโ |
gid | 1000 | group identifierโ |
home | /adguard | home directory of user docker |
| Parameter | Value | Default |
|---|---|---|
TZ | Time Zoneโ | |
DEBUG | Will activate debug option for container image and app (if available) | |
ADGUARD_CONFIG (optional) | Will overwrite the default config with the value of this variable if set (inline configโ ) |
These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.
It is my opinion that the :latest tag is a bad habbit and should not be used at all. Many developers introduce breaking changes in new releases. This would messed up everything for people who use :latest. 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.79 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. Which in theory should not introduce breaking changes.
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.79
docker pull ghcr.io/11notes/adguard:0.107.79
docker pull quay.io/11notes/adguard:0.107.79
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:
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 12.10.2026, 08:52:05 (CET)
Content type
Image
Digest
sha256:fb2c1778fโฆ
Size
14.3 MB
Last updated
about 1 hour ago
docker pull 11notes/adguard:0.107.79-unraid