Problems with setting up Adguard Home via Docker Compose

retikulum · May 3rd 2025

Hi there

after a fresh install of OMV 7 I was able to get up my containers except for adguard home

The error and yml are:

invalid IP address: 54

Code

services:
  adguardhome:
    image: adguard/adguardhome
    container_name: adguardhome
    ports:
      - 54:53/tcp # unverschlüsseltes DNS
      - 54:53/udp # unverschlüsseltes DNS
      - 67:67/udp # DHCP
      - 68:68/tcp # DHCP
      - 68:68/udp # DHCP
      - 853:853/tcp # DNS over TLS
      - 81:80/tcp #change this to something like 81:80 if port 80 is already in use
      - 3000:3000/tcp # Ersteinrichtung
    volumes:
      - /Daten/Docker/AdGuard/workdir:/opt/adguardhome/work
      - /Daten/Docker/AdGuard/confdir:/opt/adguardhome/conf
    restart: unless-stopped

Display More

How can I fix this?

jata1 · May 4th 2025

I would start with a simple config - see by example below.

You are using a default bridge network approach rather than macvlan - this is fine but...

I think you need to bind the ip address of the omv server for your dns ports as I have done in the example below.

I see you are mapping port 54 on the host to 53 in the container. That might be a problem as dns uses port 53.

Hope this helps a bit...

Code

services:
  adguard:
    container_name: adguard
    image: adguard/adguardhome:latest
    hostname: adguard
    restart: unless-stopped
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
    ports:
      - 192.168.1.4:53:53/udp
      - 192.168.1.4:53:53/tcp
      - 8083:80/tcp 
##      - 443:443/tcp
##      - 853:853/tcp 
##      - 3000:3000/tcp ## needed for initial setup  
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /symlinks/omv-system/appdata/adguard/conf:/opt/adguardhome/conf
      - /symlinks/omv-system/appdata/adguard/work:/opt/adguardhome/work

Display More

retikulum · May 4th 2025

Well this did'nt work unfortunately : invalid IP address: 192.168.0.22:54

Soma · May 4th 2025

Quote from retikulum

Well this did'nt work unfortunately : invalid IP address: 192.168.0.22:54

The port is 53, NOT 54

retikulum · May 4th 2025

OMV causes you to change the port because of the WebGUI.

It doesn't matter either, stilkl not able to start the Docker-Container: invalid IP address: 192.168.0.22:53

chente · May 4th 2025

OMV uses port 53, as you've already been told in this thread. Adguard also requires port 53. The best way to solve this problem is to use a VLAN. You can see how to do it here. https://wiki.omv-extras.org/do…te_a_vlan_pi-hole_adguard

Soma · May 4th 2025

Quote from retikulum

OMV causes you to change the port because of the WebGUI.
It doesn't matter either, stilkl not able to start the Docker-Container: invalid IP address: 192.168.0.22:53

Put those 2 addresses inside ""

Like

Code

    ports:
      - "192.168.1.4:53:53/udp"
      - "192.168.1.4:53:53/tcp"

belierzz · May 4th 2025

You may have a look here:

ryecoaaron provided a simple solution regarding the port 53 conflict.

retikulum · May 4th 2025

Well it looks like a problem of the Docker Compose Plugin. After setting up a new Portainer-Container I was able to set up the AdGuard Container with the aforementioned script without any problems.

ryecoaaron · May 4th 2025

Quote from retikulum

t looks like a problem of the Docker Compose Plugin

I disagree. I don't see anything in this thread that the plugin is doing wrong.

retikulum · May 4th 2025

I don't know either. But somehow is Portainer able to use the script without any error message while Docker Compose from the OMV Extras Repo isn't.

ryecoaaron · May 4th 2025

Quote from retikulum

But somehow is Portainer able to use the script without any error message while Docker Compose from the OMV Extras Repo isn't.

Is a "script" a compose file? All I can think is you are doing something different with network settings or Portainer defaults to doing something different with networking. I don't use portainer but this isn't a bug with the compose plugin. You just need to be more explicit in your settings like Soma mentions.

retikulum · May 4th 2025

When I inspect the container from Portainer these are the network settings which obviously are working. In the Docker Compose Plugin I miss the option to inspect the container.

Code

NetworkSettings:{
Bridge:"",
EndpointID:"",
Gateway:"",
GlobalIPv6Address:"",
GlobalIPv6PrefixLen:0,
HairpinMode:false,
IPAddress:"",
IPPrefixLen:0,
IPv6Gateway:"",
LinkLocalIPv6Address:"",
LinkLocalIPv6PrefixLen:0,
MacAddress:"",
Networks:{
adguard_default:{
Aliases:[
"adguardhome",
"2d25ebecefee"
],
DNSNames:[
"adguardhome",
"2d25ebecefee"
],
DriverOpts:null,
EndpointID:"20ed46e4e9cd01a8b4509110c9d70b458c85846e20d71051def815794be87688",
Gateway:"172.21.0.1",
GlobalIPv6Address:"",
GlobalIPv6PrefixLen:0,
GwPriority:0,
IPAMConfig:null,
IPAddress:"172.21.0.2",
IPPrefixLen:16,
IPv6Gateway:"",
Links:null,
MacAddress:"36:5f:65:f7:b1:2e",
NetworkID:"ae116f85fccf5dc623b1dd63b6beca2dc2d8b50ae8afb60f8fa19cccc2d0511b"
}
},

Display More

ruudm · May 4th 2025

Anoother suggestion: create a MacVlan inside OMV/services/compose/networks. I.e. "Subnet": "192.168.188.0/24", "IPRange": "192.168.188.6/32", "Gateway": "192.168.188.1". Depends on your config.

It finally ends up in a fixed IP-address which can be used on your router.

My working yml:

Code

services:
  adguardhome:
    image: adguard/adguardhome:latest
    hostname: adguard
    container_name: adguard
    networks:
      lokaal: 
        ipv4_address: 192.168.188.6
        # mac_address: 12:34:56:78:90:12 #sample, not always needed - for me it does
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
    volumes:
      - ${DOCKER}/adguard/work:/opt/adguardhome/work
      - ${DOCKER}/adguard/conf:/opt/adguardhome/conf
    restart: always

networks:
  lokaal:
    external: true

Display More

Zafkiel · May 4th 2025

What a coincidence, I just happened to test adguard home on April 28. Before setting it up, I checked out its docker hub and github pages and looked through this forum for any tips or warnings. I followed Soma’s method, like he mentioned in post #7, and it worked fine with the compose plugin.

My compose file looks like this:

Code

services:
  adguardhome:
    image: adguard/adguardhome
    container_name: adguardhome
    volumes:
      - /docker/docker-data/adguardhome/work:/opt/adguardhome/work
      - /docker/docker-data/adguardhome/conf:/opt/adguardhome/conf
    ports:
      - "192.168.1.4:53:53/tcp"
      - "192.168.1.4:53:53/udp"
      - "3000:3000/tcp"
      #- "67:67/udp"
      #- "68:68/udp"
      #- "80:80/tcp"
      #- "443:443/tcp"
      #- "443:443/udp"
      #- "853:853/tcp"
      #- "784:784/udp"
      #- "853:853/udp"
      #- "8853:8853/udp"
      #- "5443:5443/tcp"
      #- "5443:5443/udp"
    environment:
      - TZ=Asia/Shanghai
    restart: unless-stopped

Display More

Soma · May 4th 2025

Quote from Zafkiel

. I followed Soma’s method, like he mentioned in post #7,

You should use the IP of the host.

The one I used is just an example,

retikulum · May 4th 2025

Yeah, I tried that with the asterix and the Docker Compose Plugin still returned the error. With Portainer there is no problem in running this stack.

jata1 · May 4th 2025

Works for me in compose using ip address-port with and without quotes. Very strange it’s not working for the op

Zafkiel · May 4th 2025

Quote from Soma

You should use the IP of the host.

The one I used is just an example,

No problem, I know what that means.

This happens to be the IP address of my test machine as well.

Problems with setting up Adguard Home via Docker Compose

retikulum May 4th 2025

Participate now!