Are the container Nextcloud and Adguard compatible in the same installation?

# Note: 192.168.1.xxx is an example network, you must update all these to match your own.
version: "2.1"
services:
  adguard:
    container_name: adguard
    image: adguard/adguardhome:latest
    mac_address: 00:19:99:99:19:09           # <-- Update
    cap_add:
      - NET_ADMIN
    networks:
      macvlan_NET:                      # <-- MACVlan Name no need to change, but do not exist previosly.
        ipv4_address: 192.168.1.3       # <-- Update, must be not in use
    volumes:
      - /srv/dev-disk-by-label-DATA/dockers/adguard/Work:/opt/adguardhome/work
      - /srv/dev-disk-by-label-DATA/dockers/adguard:/opt/adguardhome/conf
    restart: unless-stopped

networks:
  macvlan_NET:
    driver: macvlan
    driver_opts:
      parent: eno0                      # <- Update to match your NIC see your OMV WebGUI
    ipam:
      config:
        - subnet: 192.168.1.0/24            # <-- Update
          gateway: 192.168.1.1              # <-- Update
          ip_range: 192.168.1.2/28          # <-- Update

this is my working adguardhome.yaml file.

please modify at your own, and use on stack portainer to deploy adguad in 192.168.1.3 IP

Make sure the ip_range is outside the dhcp range of your router and not in ise by any other device with static IP on the network.

If you need to calculate a different addresss /CIDR you can use this link

If you need help with this, post

• your netmask in the router,
• the IP of your roter and
• the dhcp address range

192.168.1.2/28 used above is 192.168.1.1 - 192.168.1.15

Zitat von Pietrogramma

Hi raulfg3, thanks for share with m your adguardhome.yaml file, I changed it for my scope, now can I create a stack with it ad deploy or I must make some operations before deploy the stack?

I suppose that I musto create the macvlan network first, it's right?

Thanks again

NO need to create macvlan, is created by yaml file, in fact you need to delete macvlan if need to redeploy

raulfg3

Thank you very much for the tutorial.

i just followed it by changing x my network data but i can't access the web interface with port 3000.

Do you know what could be due?

Thank you

please post your yaml file to revise and your adguard log.

if http://192.168.1.3:3000 do not work this means that docker is not deployed good, perhaps 192.168.1.3 was in use for other machine in your LAN so you can assing it to adguard

Zitat von raulfg3

please post your yaml file to revise and your adguard log.

if http://192.168.1.3:3000 do not work this means that docker is not deployed good, perhaps 192.168.1.3 was in use for other machine in your LAN so you can assing it to adguard

version: "2.1"

services:

adguard:

container_name: adguard

image: adguard/adguardhome:latest

mac_address: 00:99:99:99:19:99

cap_add:

- NET_ADMIN

networks:

macvlan_NET:

ipv4_address: 192.168.2.195

volumes:

- /datoszfs/docker/configuraciones/adguard/data:/opt/adguardhome/work

- /datoszfs/docker/configuraciones/adguard/conf:/opt/adguardhome/conf

restart: unless-stopped

networks:

macvlan_NET:

driver: macvlan

driver_opts:

parent: br0

ipam:

config:

- subnet: 192.168.2.0/24

gateway: 192.168.2.1

the .195 is not in use

Ok, please go to portainer and delete previous adguard stack

delete macvlan in portainer webGUI, so when try to create it on yaml file, works.

and copy & paste this yaml file,

# Note: 192.168.1.xxx is an example network, you must update all these to match your own.
version: "2.1"
services:
  adguard:
    container_name: adguard
    image: adguard/adguardhome:latest
    mac_address: 00:19:99:99:19:07           # <-- Update
    cap_add:
      - NET_ADMIN
    networks:
      macvlan_NET:                      # <-- MACVlan Name no need to change, but do not exist previosly.
        ipv4_address: 192.168.2.195       # <-- Update
    volumes:
      - /datoszfs/docker/configuraciones/adguard/Work:/opt/adguardhome/work
      - /datoszfs/docker/configuraciones/adguard/conf:/opt/adguardhome/conf
    restart: unless-stopped

networks:
  macvlan_NET:
    driver: macvlan
    driver_opts:
      parent: br0                       # <- Update to match your NIC see your OMV WebGUI
    ipam:
      config:
        - subnet: 192.168.2.0/24            # <-- Update
          gateway: 192.168.2.1              # <-- Update
          ip_range: 192.168.2.1/24          # <-- Update

I asume that "br0" is your NIC name that appears on OMV webGUI.

here the file adguard.yaml ( delete the txt extension) adguard.yaml.txt

Zitat von raulfg3

Ok, please go to portainer and delete previous adguard stack

delete macvlan in portainer webGUI, so when try to create it on yaml file, works.

and copy & paste this yaml file,

Code

# Note: 192.168.1.xxx is an example network, you must update all these to match your own.
version: "2.1"
services:
  adguard:
    container_name: adguard
    image: adguard/adguardhome:latest
    mac_address: 00:19:99:99:19:07           # <-- Update
    cap_add:
      - NET_ADMIN
    networks:
      macvlan_NET:                      # <-- MACVlan Name no need to change, but do not exist previosly.
        ipv4_address: 192.168.2.195       # <-- Update
    volumes:
      - /datoszfs/docker/configuraciones/adguard/Work:/opt/adguardhome/work
      - /datoszfs/docker/configuraciones/adguard/conf:/opt/adguardhome/conf
    restart: unless-stopped

networks:
  macvlan_NET:
    driver: macvlan
    driver_opts:
      parent: br0                       # <- Update to match your NIC see your OMV WebGUI
    ipam:
      config:
        - subnet: 192.168.2.0/24            # <-- Update
          gateway: 192.168.2.1              # <-- Update
          ip_range: 192.168.2.1/24          # <-- Update

Alles anzeigen

I asume that "br0" is your NIC name that appears on OMV webGUI.

here the file adguard.yaml ( delete the txt extension) adguard.yaml.txt

Alles anzeigen

Yes

in the omv gui and with ip addr br0

I have made a bridge with eno2 because I have supervised homeassistant in a VM in kvm

the container works and the log does not give errors, what happens is that I scan the ports of that ip the .195 and no open port appears

I can not access via web to port 3000

Zitat von moretty

Yes

in the omv gui and with ip addr br0

I have made a bridge with eno2 because I have supervised homeassistant in a VM in kvm

the container works and the log does not give errors, what happens is that I scan the ports of that ip the .195 and no open port appears

I can not access via web to port 3000

perhaps the bridge with eno2 interfiere.

sorry I can't help more.

My suggest, test adguar as only docker on a test machine (witout bridges) to test if work, if not, still you can use pihole instead of adguard

PD: Is not really usefull to use a hight Ip like 192.168.2.195 as a DNS server, please consider to use 192.168.2.10 as DNS (Adguard) instead.

In that case you need to modify this line: ipv4_address: 192.168.2.195 according.

And remember , YOU NEED TO DELETE the previosly created macVLAN prior to restart the stack every time so a new MacVLAN can be created, otherwise do not work

Zitat von raulfg3

perhaps the bridge with eno2 interfiere.

sorry I can't help more.

My suggest, test adguar as only docker on a test machine (witout bridges) to test if work, if not, still you can use pihole instead of adguard

PD: Is not really usefull to use a hight Ip like 192.168.2.195 as a DNS server, please consider to use 192.168.2.10 as DNS (Adguard) instead.

In that case you need to modify this line: ipv4_address: 192.168.2.195 according.

And remember , YOU NEED TO DELETE the previosly created macVLAN prior to restart the stack every time so a new MacVLAN can be created, otherwise do not work

Alles anzeigen

indeed br0 causes problems.

my yaml configuration was always correct.

create the container with eno1 and it works