Skip to content
BranchesTags

Repository files navigation

AdGuard Home

Build Status Last Commit

Network-wide ad and tracker blocking DNS server. Covers all devices on your network with no client-side software — includes DoH, DoT, DoQ, and a built-in DHCP server.
Port 3000
Registry ghcr.io/daemonless/adguardhome
Source https://github.com/AdguardTeam/AdGuardHome
Website https://adguard.com/adguard-home.html

Version Tags

Tag Description Best For
latest FreeBSD Port. Built from FreeBSD packages. Most users — recommended.
pkg FreeBSD Quarterly. Uses stable, tested packages. Production stability.
pkg-latest FreeBSD Latest. Rolling package updates. Staying current.

Prerequisites

Before deploying, ensure your host environment is ready. See the Quick Start Guide for host setup instructions.

Deployment

Podman Compose

services:
  adguardhome:
    image: "ghcr.io/daemonless/adguardhome:latest"
    container_name: adguardhome
    environment:
      - PUID=1000  # User ID for the application process
      - PGID=1000  # Group ID for the application process
      - TZ=UTC  # Timezone for the container
    volumes:
      - "/path/to/containers/adguardhome/conf:/opt/adguardhome/conf"
      - "/path/to/containers/adguardhome/work:/opt/adguardhome/work"
    ports:
      - "3000:3000"
      - "53:53"
      - "53:53"
      - "67:67"
      - "68:68"
      - "80:80"
      - "443:443"
      - "443:443"
      - "784:784"
      - "853:853"
      - "853:853"
      - "5443:5443"
      - "5443:5443"
      - "6060:6060"
      - "8853:8853"
    # always (not unless-stopped) so FreeBSD's podman rc.d auto-starts it at boot
    restart: always

Save as compose.yaml, then run podman-compose up -d.

AppJail Director

.env:

# .env

DIRECTOR_PROJECT=adguardhome
PUID=1000
PGID=1000
TZ=UTC

appjail-director.yml:

# appjail-director.yml

options:
  - virtualnet: ':<random> default'
  - nat:
services:
  adguardhome:
    name: adguardhome
    options:
      - container: 'boot args:--pull'
      - expose: '3000:3000 proto:tcp'
      - expose: '53:53 proto:tcp'
      - expose: '53:53 proto:udp'
      - expose: '67:67 proto:udp'
      - expose: '68:68 proto:udp'
      - expose: '80:80 proto:tcp'
      - expose: '443:443 proto:tcp'
      - expose: '443:443 proto:udp'
      - expose: '784:784 proto:udp'
      - expose: '853:853 proto:tcp'
      - expose: '853:853 proto:udp'
      - expose: '5443:5443 proto:tcp'
      - expose: '5443:5443 proto:udp'
      - expose: '6060:6060 proto:tcp'
      - expose: '8853:8853 proto:udp'
    oci:
      user: root
      environment:
        - PUID: !ENV '${PUID}'
        - PGID: !ENV '${PGID}'
        - TZ: !ENV '${TZ}'
    volumes:
      - adguardhome_conf: /opt/adguardhome/conf
      - adguardhome_work: /opt/adguardhome/work
volumes:
  adguardhome_conf:
    device: '/path/to/containers/adguardhome/conf'
  adguardhome_work:
    device: '/path/to/containers/adguardhome/work'

Makejail:

# Makejail

ARG tag=latest

OPTION overwrite=force
OPTION from=ghcr.io/daemonless/adguardhome:${tag}

Save the files above, then run appjail-director up.

Note: Exposing ports in AppJail means that your service can be reached from remote hosts. If that is not your intention, do not expose the ports and communicate with the service using the IPv4 address assigned by the virtual network.

Podman CLI

podman run -d --name adguardhome \
  -p 3000:3000 \
  -p 53:53 \
  -p 53:53 \
  -p 67:67 \
  -p 68:68 \
  -p 80:80 \
  -p 443:443 \
  -p 443:443 \
  -p 784:784 \
  -p 853:853 \
  -p 853:853 \
  -p 5443:5443 \
  -p 5443:5443 \
  -p 6060:6060 \
  -p 8853:8853 \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=UTC \
  -v /path/to/containers/adguardhome/conf:/opt/adguardhome/conf \
  -v /path/to/containers/adguardhome/work:/opt/adguardhome/work \
  ghcr.io/daemonless/adguardhome:latest

Save as run.sh, then run sh run.sh.

AppJail

appjail oci run -Pd \
  -o overwrite=force \
  -o container="args:--pull" \
  -o virtualnet=":<random> default" \
  -o nat \
  -o expose="3000:3000 proto:tcp" \
  -o expose="53:53 proto:tcp" \
  -o expose="53:53 proto:udp" \
  -o expose="67:67 proto:udp" \
  -o expose="68:68 proto:udp" \
  -o expose="80:80 proto:tcp" \
  -o expose="443:443 proto:tcp" \
  -o expose="443:443 proto:udp" \
  -o expose="784:784 proto:udp" \
  -o expose="853:853 proto:tcp" \
  -o expose="853:853 proto:udp" \
  -o expose="5443:5443 proto:tcp" \
  -o expose="5443:5443 proto:udp" \
  -o expose="6060:6060 proto:tcp" \
  -o expose="8853:8853 proto:udp" \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=UTC \
  -o fstab="/path/to/containers/adguardhome/conf /opt/adguardhome/conf <pseudofs>" \
  -o fstab="/path/to/containers/adguardhome/work /opt/adguardhome/work <pseudofs>" \
  ghcr.io/daemonless/adguardhome:latest adguardhome

Save as run.sh, then run sh run.sh.

Note: Exposing ports in AppJail means that your service can be reached from remote hosts. If that is not your intention, do not expose the ports and communicate with the service using the IPv4 address assigned by the virtual network.

Bastille

Warning

Bastille's OCI support is experimental. It requires buildah, shares the host network stack (inherit), and persists image-declared volumes under --data-path.

services:
  adguardhome:
    image: "ghcr.io/daemonless/adguardhome:latest"
    container_name: adguardhome
    network_mode: host  # jail shares host networking
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=UTC

Save as podman-compose.yml, then run bastille up. Or via CLI:

bastille create -O \
  --env PUID=1000 \
  --env PGID=1000 \
  --env TZ=UTC \
  --data-path /path/to/containers/adguardhome \
  adguardhome ghcr.io/daemonless/adguardhome:latest inherit

Ansible

- name: Deploy adguardhome
  containers.podman.podman_container:
    name: adguardhome
    image: "ghcr.io/daemonless/adguardhome:latest"
    state: started
    restart_policy: always
    env:
      PUID: "1000"
      PGID: "1000"
      TZ: "UTC"
    ports:
      - "3000:3000"
      - "53:53"
      - "53:53"
      - "67:67"
      - "68:68"
      - "80:80"
      - "443:443"
      - "443:443"
      - "784:784"
      - "853:853"
      - "853:853"
      - "5443:5443"
      - "5443:5443"
      - "6060:6060"
      - "8853:8853"
    volumes:
      - "/path/to/containers/adguardhome/conf:/opt/adguardhome/conf"
      - "/path/to/containers/adguardhome/work:/opt/adguardhome/work"

Save as adguardhome-deploy.yaml, then run ansible-playbook adguardhome-deploy.yaml.

Parameters

Environment Variables

Variable Default Description
PUID 1000 User ID for the application process
PGID 1000 Group ID for the application process
TZ UTC Timezone for the container

Volumes

Path Description
/opt/adguardhome/conf Configuration files
/opt/adguardhome/work Work directory (database, logs, data)

Ports

Port Protocol Description
3000 TCP Web UI (Setup/Admin)
53 TCP DNS (TCP/UDP)
53 UDP DNS (TCP/UDP)
67 UDP
68 UDP
80 TCP HTTP
443 TCP HTTPS / DNS-over-HTTPS (TCP/UDP)
443 UDP HTTPS / DNS-over-HTTPS (TCP/UDP)
784 UDP
853 TCP DNS-over-TLS (TCP/UDP)
853 UDP DNS-over-TLS (TCP/UDP)
5443 TCP DNS-over-HTTPS (TCP/UDP)
5443 UDP DNS-over-HTTPS (TCP/UDP)
6060 TCP Admin API
8853 UDP

Architectures: amd64 User: bsd (UID/GID via PUID/PGID, defaults to 1000:1000) Base: FreeBSD 15

Need help? Join our Discord community.

About

Network-wide ad and tracker blocking DNS server. Covers all devices on your network with no client-side software — includes DoH, DoT, DoQ, and a built-in DHCP server.

daemonless.io/images/adguardhome/

Topics

adblockingadguardhomecontainerdaemonlessdnsfreebsdfreebsd-jailnetworkocioci-imagepodmanself-hosted

Resources

Readme
BSD-2-Clause license
Activity
Custom properties

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages