docker-compose pihole -> DNS service is not running and stopping lighttpd

Meadows · Dec 20th 2023

I am new to docker and couldn’t figure out howto proceed with troubleshooting. I would appreciate to be pointed in the right direction.

Test_System:

Version: 6.9.10-5 (Shaitan)
Prozessor: AMD Turion(tm) II Neo N40L Dual-Core Processor
Kernel: Linux 6.2.16-20-bpo11-pve
DHCP Server using pihole running on a Raspi 1b with a DHCP range from 192.168.1.120 - 192.168.1.239
/dev/md0 formatted with ext4

I followed the howto of:

omv-extras.org docker / compose
The Jellyfin container installation works fine according to the howto
The syntax check of the pihole compose file passed
apparmor is disabled at boot time, nor installed
The pihole container is up and running, but the pihole service is not running, nor lighttpd
The compose file is taken from raulfg3 and customized

docker_logs.txt

Variables I used:

#PUID=1001

#PGID=100

TZ=Europe/Berlin

URL=fritz.box

Password2=super_secret

DATA=/srv/dev-disk-by-uuid-64145f7e-a1fa-4ee2-b2d0-9007ebc5f053/data

macvlan

"Subnet": "192.168.1.0/24", "IPRange": "192.168.1.240/29", "Gateway": "192.168.1.1"

Parent : eth0 corresponding to omv network settings

Code

[
  {
    "Name": "mynet",
    "Id": "f688f0b76f40d4ad2e096e025fcc05c214839a499e4156bdeb3827318e29f595",
    "Created": "2023-12-20T09:11:26.144069624+01:00",
    "Scope": "local",
    "Driver": "macvlan",
    "EnableIPv6": false,
    "IPAM": {
      "Driver": "default",
      "Options": {},
      "Config": [
        {
          "Subnet": "192.168.1.0/24",
          "IPRange": "192.168.1.240/29",
          "Gateway": "192.168.1.1"
        }
      ]
    },
    "Internal": false,
    "Attachable": false,
    "Ingress": false,
    "ConfigFrom": {
      "Network": ""
    },
    "ConfigOnly": false,
    "Containers": {
      "df675a6b0d77f20cd1ccf19bb7ba051ebfa7765ffa0553d84083d6dfad93049a": {
        "Name": "pihole",
        "EndpointID": "22d1c0a779f2e149113f56ccffe1972bef14519b3eda975a1bbf59302ecdd7fe",
        "MacAddress": "02:42:c0:a8:01:f1",
        "IPv4Address": "192.168.1.241/24",
        "IPv6Address": ""
      }
    },
    "Options": {
      "parent": "eth0"
    },
    "Labels": {}
  }
]

END OF LINE
█

Display More

compose file:

Code

# Note: 192.168.1.xxx is an example network, you must update all these to match your own.
# Thanks to http://tonylawrence.com/posts/unix/synology/free-your-synology-ports/ for your reference post
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
version: "3"
services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    hostname: pihole
    domainname: '${URL}'                    # <-- Update on enviromen.env file
    networks:
      mynet:                        # <-- MACVlan Name You need to create first in Portainer WebGUI.
        ipv4_address: 192.168.1.241       # <-- Update to your desired Pihole IPv4
# https://www.youtube.com/watch?v=4741-YR31fM
# https://www.youtube.com/watch?v=o7nn6Tv-PAw
    cap_add:
      - NET_ADMIN # Recommended but not required (DHCP needs NET_ADMIN)  
    ports: 
      - "53:53/tcp"
      - "53:53/udp"
      - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server
      - "80:80/tcp"
    environment:
      #ADMIN_EMAIL: $email
      FTLCONF_LOCAL_IPV4: 192.168.1.241   # <-- Update (match ipv4_address of PiHole)
      VIRTUAL_HOST: 'pihole.${URL}'    # <-- Update (match hostname + domainname)
      WEBPASSWORD: '${Password2}'           # <-- Add password (if required)
      PIHOLE_DNS_: 8.8.8.8;8.8.4.4      # <-- Change by your prefered DNS service like 1.1.1.1
      TZ: '${TZ}'                 # <-- Your Time Zone here
      IPv6: "false"
# Volumes store your data between container upgrades
    volumes:
      - '${DATA}/pihole:/etc/pihole'
      - '${DATA}/pihole/dnsmasq.d:/etc/dnsmasq.d'    
#   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
    restart: unless-stopped

networks:
  mynet:
    external: true

Display More

compose settings:

chente · Dec 20th 2023

Hello. I am trying to find the error. I would appreciate if you can edit your post and put the code in code boxes using the </> button in the forum window bar, respect the indentations, copy and paste. It is difficult to analyze the published code as you have done.

chente · Dec 20th 2023

Quote from Meadows

networks:
mynet:
external: true

The indentations of the yaml file are probably failing in this part, but if you do not edit your publication respecting the indentations we cannot see the error.

raulfg3 · Dec 20th 2023

do you create a macvlan on omv-compose webGUI?.

Is mandatory to create first to use on your pihole.yml file

see my signature: RE: [HOWTO] install PIHOLE on OMV using portainer WEBGUI on a MacVlan

Meadows · Dec 20th 2023

Quote from chente

The indentations of the yaml file are probably failing in this part, but if you do not edit your publication respecting the indentations we cannot see the error.

OK. I try. When I use source code + copy paste I can't send it, what I am missing?

Meadows · Dec 20th 2023

Quote from raulfg3

do you create a macvlan on omv-compose webGUI?.

Is mandatory to create first to use on your pihole.yml file

see my signature: RE: [HOWTO] install PIHOLE on OMV using portainer WEBGUI on a MacVlan

Display More

yes I created it in the webgui and it was created first

chente · Dec 20th 2023

Quote from Meadows

OK. I try. When I use source code + copy paste I can't send it, what I am missing?

In the forum create the code box with the </> button

From the plugin GUI edit the compose file and simply select the text and copy it with the mouse.

Paste it in the forum code box.

Meadows · Dec 20th 2023

compose file:

sorry for the delay, it seems something is blocked by my browser, but I send you the screenshots for the moment

Meadows · Dec 20th 2023

and as a text file

chente · Dec 20th 2023

Code

# Note: 192.168.1.xxx is an example network, you must update all these to match your own.
# Thanks to http://tonylawrence.com/posts/unix/synology/free-your-synology-ports/ for your reference post
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
version: "3"
services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    hostname: pihole
    domainname: '${URL}'                    # <-- Update on enviromen.env file
    networks:
      mynet:                        # <-- MACVlan Name You need to create first in Portainer WebGUI.
        ipv4_address: 192.168.1.241       # <-- Update to your desired Pihole IPv4
# https://www.youtube.com/watch?v=4741-YR31fM
# https://www.youtube.com/watch?v=o7nn6Tv-PAw
    cap_add:
      - NET_ADMIN # Recommended but not required (DHCP needs NET_ADMIN)  
    ports: 
      - "53:53/tcp"
      - "53:53/udp"
      - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server
      - "80:80/tcp"
    environment:
      #ADMIN_EMAIL: $email
      FTLCONF_LOCAL_IPV4: 192.168.1.241   # <-- Update (match ipv4_address of PiHole)
      VIRTUAL_HOST: 'pihole.${URL}'    # <-- Update (match hostname + domainname)
      WEBPASSWORD: '${Password2}'           # <-- Add password (if required)
      PIHOLE_DNS_: 8.8.8.8;8.8.4.4      # <-- Change by your prefered DNS service like 1.1.1.1
      TZ: '${TZ}'                 # <-- Your Time Zone here
      IPv6: "false"
# Volumes store your data between container upgrades
    volumes:
      - '${DATA}/pihole:/etc/pihole'
      - '${DATA}/pihole/dnsmasq.d:/etc/dnsmasq.d'    
#   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
    restart: unless-stopped

networks:
  mynet:
    external: true

Display More

ok, I see special variables defined, I assume you are sure they are correct, the rest seems to be correct. If you have created a vlan you can skip the entire part regarding ports, it is not necessary.

Please in the GUI go to Services>Compose>Networks Select the macvlan network "mynet" that you have created and click edit. Take a screenshot and post it here.

raulfg3 · Dec 20th 2023

Quote from Meadows

and as a text file

all variables need to be writen on global.env in omv-compose

eg: ${Password2} you need to write something like Password2=mysecretpassWord

and same for all variables, like : $TZ etc..

and please learn how to post her using this:

I need that post something like this to see that create a macvlan:

and use lupe to post here the result, something like this:

Code

[
  {
    "Name": "MyMacVlan",
    "Id": "07f9a1fefe5ed2f3bae66ea3c0db82193b0955a4d7bdca22d7a8fd4671de0305",
    "Created": "2023-09-12T10:33:22.826114272+02:00",
    "Scope": "local",
    "Driver": "macvlan",
    "EnableIPv6": false,
    "IPAM": {
      "Driver": "default",
      "Options": {},
      "Config": [
        {
          "Subnet": "192.168.1.0/24",
          "IPRange": "192.168.1.1/29",
          "Gateway": "192.168.1.1",
          "AuxiliaryAddresses": {
            "adguard": "192.168.1.3",
            "host": "192.168.1.10"
          }
        }
      ]
    },
    "Internal": false,
    "Attachable": false,
    "Ingress": false,
    "ConfigFrom": {
      "Network": ""
    },
    "ConfigOnly": false,
    "Containers": {},
    "Options": {
      "parent": "eno1"
    },
    "Labels": {}
  }
]

END OF LINE

Display More

Meadows · Dec 20th 2023

here you go and the password is of course not shared

Meadows · Dec 20th 2023

Quote from raulfg3

all variables need to be writen on global.env in omv-compose

eg: ${Password2} you need to write something like Password2=mysecretpassWord

and same for all variables, like : $TZ etc..

and please learn how to post her using this:

I need that post something like this to see that create a macvlan:

and use lupe to post here the result, something like this:

Code

[
  {
    "Name": "MyMacVlan",
    "Id": "07f9a1fefe5ed2f3bae66ea3c0db82193b0955a4d7bdca22d7a8fd4671de0305",
    "Created": "2023-09-12T10:33:22.826114272+02:00",
    "Scope": "local",
    "Driver": "macvlan",
    "EnableIPv6": false,
    "IPAM": {
      "Driver": "default",
      "Options": {},
      "Config": [
        {
          "Subnet": "192.168.1.0/24",
          "IPRange": "192.168.1.1/29",
          "Gateway": "192.168.1.1",
          "AuxiliaryAddresses": {
            "adguard": "192.168.1.3",
            "host": "192.168.1.10"
          }
        }
      ]
    },
    "Internal": false,
    "Attachable": false,
    "Ingress": false,
    "ConfigFrom": {
      "Network": ""
    },
    "ConfigOnly": false,
    "Containers": {},
    "Options": {
      "parent": "eno1"
    },
    "Labels": {}
  }
]

END OF LINE

Display More

mynet:

Display Spoiler

chente · Dec 20th 2023

For my part, I'm out of ideas, everything I'm seeing seems correct. I can only think of a problem with the fritzbox, it wouldn't be the first time that this router has caused a problem and as a consequence a long thread in the forum.

Meadows · Dec 20th 2023

Quote from chente

For my part, I'm out of ideas, everything I'm seeing seems correct. I can only think of a problem with the fritzbox, it wouldn't be the first time that this router has caused a problem and as a consequence a long thread in the forum.

OK chente and raulfg3, that helps. Thanks you very much. I will proceed with the fritz.box and pihole's DHCP on my Raspi 1b.

raulfg3 · Dec 20th 2023

revise name of your lan on omv-webGUI , eth0 is not desire, mine is en0 for example (in the parent section)

and configure macvlan with apropiate name

Meadows · Dec 20th 2023

Quote from raulfg3

revise name of your lan on omv-webGUI , eth0 is not desire, mine is en0 for example (in the parent section)

and configure macvlan with apropiate name

ifconfig shows eth0, within the webgui - network I don't have the option other then eth0

Code

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:5d:29:c2:1f  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.15  netmask 255.255.255.0  broadcast 192.168.1.255
        ether a0:b3:cc:e2:52:b4  txqueuelen 1000  (Ethernet)
        RX packets 439111  bytes 557661764 (531.8 MiB)
        RX errors 0  dropped 15750  overruns 0  frame 0
        TX packets 73075  bytes 7997474 (7.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 18  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 54161  bytes 34449545 (32.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 54161  bytes 34449545 (32.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Display More

raulfg3 · Dec 20th 2023

at this point , i am out of ideas, sorry.

Meadows · Dec 20th 2023

Quote from raulfg3

at this point , i am out of ideas, sorry.

anyway thank you very much for your efforts, I appreciate it.

Meadows · Dec 20th 2023

Code

from another network client
$ ping -c 4 192.168.1.241
PING 192.168.1.241 (192.168.1.241) 56(84) bytes of data.
64 bytes from 192.168.1.241: icmp_seq=1 ttl=64 time=6.48 ms
64 bytes from 192.168.1.241: icmp_seq=2 ttl=64 time=0.415 ms
64 bytes from 192.168.1.241: icmp_seq=3 ttl=64 time=0.446 ms
64 bytes from 192.168.1.241: icmp_seq=4 ttl=64 time=0.413 ms

from host
$ sudo docker exec -ti pihole ping -c 4 192.168.1.241
[sudo] password for omv: 
PING 192.168.1.241 (192.168.1.241) 56(84) bytes of data.
64 bytes from 192.168.1.241: icmp_seq=1 ttl=64 time=0.070 ms
64 bytes from 192.168.1.241: icmp_seq=2 ttl=64 time=0.063 ms
64 bytes from 192.168.1.241: icmp_seq=3 ttl=64 time=0.065 ms
64 bytes from 192.168.1.241: icmp_seq=4 ttl=64 time=0.061 ms

--- 192.168.1.241 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3075ms
rtt min/avg/max/mdev = 0.061/0.064/0.070/0.003 ms

Display More

I would exclude issues from the fritz.box or DHCP server (raspi-pihole). Is this also a confirmation that the macvlan is OK? If so I could proceed and ask in the pihole forum.

docker-compose pihole -> DNS service is not running and stopping lighttpd

Participate now!

Tags