im new to all this. got a pi a few months ago (got it the day trixie came out) and installed pihole on it. pihole on its own works without any issues.
When omv 8 came out i added it to the install also. no docker straight to pi. but this seems to be causing some dns issues with pihole, i believe this is due to a pirt conflict (80, and 53) im not sure what the best way to resolve this is. do i docker pihole, or can i docker omv?? is there. way to run them both nativly w/o docker?
pihole and omv on one pi?
-
- OMV 8.x
- skullkidrae
-
chente
Approved the thread. -
If you've repaired Pihole, you've broken OMV. They can't coexist because they both need port 53.
The way to make them coexist is to configure Pihole in a container and use a VLAN. Read here --> https://wiki.omv-extras.org/do…te_a_vlan_pi-hole_adguard
However, this has a limitation: OMV won't be able to use the DNS server provided by Pihole, since the container can't communicate with the host.
-
-
If you've repaired Pihole, you've broken OMV. They can't coexist because they both need port 53.
The way to make them coexist is to configure Pihole in a container and use a VLAN. Read here --> https://wiki.omv-extras.org/do…te_a_vlan_pi-hole_adguard
However, this has a limitation: OMV won't be able to use the DNS server provided by Pihole, since the container can't communicate with the host.
good to know. im not curently using omv just yet. so i need to docker pihole from omv.
-
If you've repaired Pihole, you've broken OMV. They can't coexist because they both need port 53.
The way to make them coexist is to configure Pihole in a container and use a VLAN. Read here --> https://wiki.omv-extras.org/do…te_a_vlan_pi-hole_adguard
However, this has a limitation: OMV won't be able to use the DNS server provided by Pihole, since the container can't communicate with the host.
ok. iv got omv running again and docker working..... i think. as far as i understand the article is getting me to setup vlan with a copy of my network info. appending config to the pihole docker file allowing it to use the same port on a different ip asif it was a separate device (ip from the vlan not my network) . but i cant get pihole running in docker. when im running it im getting an error <
time="2026-01-10T22:22:25Z" level=warning msg="No services to build"
network mynet declared as external, but could not be found*** ERROR #1 ***
END OF LINE
█>help
-
Publish your compose file.
-
-
please create mynet in Compose webGUI First.
-
please create mynet in Compose webGUI First.
how do i do that. is it a file under compose?
-
Publish your compose file.
Code
Display Moreservices: pihole: container_name: pihole image: pihole/pihole:latest ports: # DNS Ports - "53:53/tcp" - "53:53/udp" # Default HTTP Port - "80:80/tcp" # Default HTTPs Port. FTL will generate a self-signed certificate - "443:443/tcp" # Uncomment the below if using Pi-hole as your DHCP Server #- "67:67/udp" # Uncomment the line below if you are using Pi-hole as your NTP server #- "123:123/udp" environment: # Set the appropriate timezone for your location from # https://en.wikipedia.org/wiki/List_of_tz_database_time_zones, e.g: TZ: 'Europe/London' # Set a password to access the web interface. Not setting one will result in a random password being assigned FTLCONF_webserver_api_password: 'correct horse battery staple' # If using Docker's default `bridge` network setting the dns listening mode should be set to 'ALL' FTLCONF_dns_listeningMode: 'ALL' # Volumes store your data between container upgrades volumes: # For persisting Pi-hole's databases and common configuration file - './etc-pihole:/etc/pihole' # Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you should keep it enabled for the first v6 container start to allow for a complete migration. It can be removed afterwards. Needs environment variable FTLCONF_misc_etc_dnsmasq_d: 'true' #- './etc-dnsmasq.d:/etc/dnsmasq.d' cap_add: # See https://github.com/pi-hole/docker-pi-hole#note-on-capabilities # Required if you are using Pi-hole as your DHCP server, else not needed - NET_ADMIN # Required if you are using Pi-hole as your NTP client to be able to set the host's system time - SYS_TIME # Optional, if Pi-hole should get some more processing time - SYS_NICE restart: unless-stopped networks: mynet: ipv4_address: 192.168.4.241 networks: mynet: external: true -
-
The compose file looks correct. Except you can skip all the port mappings. This is because you're using a VLAN, so all the ports are exposed on that IP address.
So the only thing that might be missing is what raulfg3 already pointed out. Did you follow the steps here to create mynet? --> https://wiki.omv-extras.org/do…erface_with_ip_in_our_lan
-
I have deactivated the DNSStubListener like described here for my OMV a long time ago:
RE: systemd-resolver get port 53 how should i change that safely to use that for pi-holeWith this systemd-resolved completely stops listening on port 53 and I run a DNS in Docker on port 53.
-
I have deactivated the DNSStubListener like described here for my OMV a long time ago:
RE: systemd-resolver get port 53 how should i change that safely to use that for pi-hole
With this systemd-resolved completely stops listening on port 53 and I run a DNS in Docker on port 53.As ryecoaaron already mentioned in that old thread, "this is a gray area". So, I wouldn't recommend that configuration since it modifies the OMV settings, unless something has changed in the last few years. But it's up to you how you configure your server.
-
-
The compose file looks correct. Except you can skip all the port mappings. This is because you're using a VLAN, so all the ports are exposed on that IP address.
So the only thing that might be missing is what raulfg3 already pointed out. Did you follow the steps here to create mynet? --> https://wiki.omv-extras.org/do…erface_with_ip_in_our_lan
ahh ok. yes i did. whither its correct or not is undetermined. my access points ip for some reason is 192.168.4.0 and my pi is ~.~.~.60
Code
Display More[ { "Name": "docker", "Id": "5bdcf22d4ac9638aaba51ae1d5d5b57cc143869c4d6b90eeff542d99a1af80e8", "Created": "2026-01-10T21:47:02.404170306Z", "Scope": "local", "Driver": "macvlan", "EnableIPv4": true, "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.4.0/24", "IPRange": "192.168.4.240/29", "Gateway": "192.168.4.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Options": { "parent": "end0" }, "Labels": {}, "Containers": {}, "Status": { "IPAM": { "Subnets": { "192.168.4.0/24": { "IPsInUse": 3, "DynamicIPsAvailable": 8 } } } } } ] END OF LINE █ -
"Name": "docker",
You called it "docker", not "mynet". Change the compose file to use the "docker" network.
-
You called it "docker", not "mynet". Change the compose file to use the "docker" network.
ahh. ok. i tryed changing the network to dsocker but it didnt work so did the inverse and redid the network info to mynet. getting the following error
Codetime="2026-01-11T14:04:58Z" level=warning msg="No services to build" Container pihole Starting Error response from daemon: failed to set up container networking: network 3b4e2c8063f902397af28f4a95d773d0a0f6e4f4fe010921751566589b3e76df not found *** ERROR #1 *** END OF LINE █ -
-
If you want to create a new interface, first delete the existing one. You should not create two network interfaces with the same network range.
-
If you want to create a new interface, first delete the existing one. You should not create two network interfaces with the same network range.
thats what i did. deleated the docker interface and recreated it as mynet
-
-
Restart the server (or the service)
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!
