Self-host AdGuard Home with Levelrail
Network-wide ad and tracker blocking with a DNS server and a friendly admin dashboard.
- AuthorAdguardTeam
- LicenceGPL-3.0
- Memory128 MiB
- Archarm64
- Services1
How to self-host AdGuard Home
-
Pull the images
One image is pulled on your server.
Show images
adguard/adguardhome:v0.107.55
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 3000.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
AdGuard Home requirements
- Memory
- About 128 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 3000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then AdGuard Home. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the AdGuard Home docs page.
Deploy AdGuard Home your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy AdGuard Home from the CLI
levelrail-cli templates deploy adguard-home --name my-adguard-home Deploy AdGuard Home with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/adguard-home/deploy AdGuard Home configuration
AdGuard Home services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| adguard | adguard/adguardhome:v0.107.55 | 3000 | adguard_work -> /opt/adguardhome/workadguard_conf -> /opt/adguardhome/conf |
AdGuard Home environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 3000
- Volumes
- 2 named mounts: adguard_work -> /opt/adguardhome/work, adguard_conf -> /opt/adguardhome/conf
AdGuard Home FAQ
How much memory does AdGuard Home need?
The catalog lists about 128 MiB of memory for AdGuard Home.
Does AdGuard Home run on arm64?
For AdGuard Home, an arm64 image is published; amd64 is image published.
What licence is AdGuard Home under?
AdGuard Home is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does AdGuard Home need configuration before it starts?
No. The template fills in its own defaults.
Which ports does AdGuard Home use?
AdGuard Home listens on port 3000 inside the stack.
Where does AdGuard Home keep its data?
In named volumes: adguard_work mounted at /opt/adguardhome/work and adguard_conf mounted at /opt/adguardhome/conf.
Can I deploy AdGuard Home on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id adguardhome for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image adguard/adguardhome:v0.107.55 is what you deploy there.