Pi hole running in docker compose "No IPv4 address(es) found on the eth0"

Help
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

I am running the latest debian system and installed pi hole in docker compose, according to the log file there is no No IPv4 address(es) found on the eth0. I have set DHCP reserve for my server in the router setup page but still no luck.

Another question I have is when setting DHCP in asus router, I am suppose to change the LAN DNS to the pi hole server, but in ASUS's latest guide it is saying to change the WAN DNS also to the pi hole server.

Debug Token:

[https://tricorder.pi-hole.net/hSwSUXeC]

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.

[✗] No IPv6 address(es) found on the eth0 interface.

[i] Default IPv4 gateway(s):
[i] Default IPv6 gateway(s):

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] kitten-396.frge.io is 0.0.0.0 on lo (127.0.0.1)
[✗] Failed to resolve kitten-396.frge.io on enp1s0 (192.168.50.157)
[✗] Failed to resolve kitten-396.frge.io on docker0 (172.17.0.1)
[✗] Failed to resolve kitten-396.frge.io on br-59032a7d110b (172.18.0.1)
[✓] doubleclick.com is 142.251.33.174 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] inpost-polska-din.order1191966.info is :: on lo (::1)
[✗] Failed to resolve inpost-polska-din.order1191966.info on enp1s0 (fdd5:7550:60:942f:9bee:38f9:5307:e8a2)
[✗] Failed to resolve inpost-polska-din.order1191966.info on enp1s0 (fdd5:7550:60:942f:6a1d:efff:fe2d:abfc)
[✗] Failed to resolve inpost-polska-din.order1191966.info on enp1s0 (fe80::6a1d:efff:fe2d:abfc)
[✓] No IPv6 address available on docker0
[✗] Failed to resolve inpost-polska-din.order1191966.info on br-59032a7d110b (fe80::42:57ff:fe5e:fa12)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)
2

Please share your docker compose file - redact passwords as required.

4 
pihole:
    container_name: pihole
    image: pihole/pihole:latest
    # For DHCP it is recommended to remove these ports and instead add: network_mode: "host"
    network_mode: host
    # 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:
      TZ: 'America/Chicago'
      WEBPASSWORD: 'PASSWORD'
    # Volumes store your data between container upgrades
    volumes:
      - './etc-pihole:/etc/pihole'
      - './etc-dnsmasq.d:/etc/dnsmasq.d'
    #   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
    cap_add:
      - NET_ADMIN # Required if you are using Pi-hole as your DHCP server, else not needed
    restart: unless-stopped
5

You are running your container in host network mode.

Your host machine does not have an eth0 network interface.
Your debug log shows it is using enp1s0.

Try configuring your Pi-hole container for enp1s0 by adding an INTERFACE variable to your environment: section:

      INTERFACE: enp1s0

In addition, you should check your Pi-hole's Interface settings on Settings | DNS.

The recommended default Allow only local requests usually works.
Your debug log shows that you had opted for Respond only on interface eth0, which has contributed to your observation (as eth0 doesn't exist on your host machine).

6

Thank you so much, the problem has now been solved.

7

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.