aorvay
December 26, 2021, 3:01pm
1
Merry Christmas everybody!
First of all, sorry for my english skills!
After a full version upgrade, my DHCP clients couldn't retrieve IP from my pi-hole instance. Pi-hole diagnostics show DNSMASQ_WARN with message "Warning in dnsmasq core: no address range availabel for DHCP request via eth0"
And on the DHCP setting no clients listed.
With the previous version all worked perfectly. I have pihole with cloudflare for DNSSEC and dhcp-helper, all this on dockerized.
Please help.
Please provide a debug token and the docker-compose.yml file or the command you are using for docker run
.
aorvay
December 26, 2021, 7:33pm
3
Hi Dan,
This is the debug token:
https://tricorder.pi-hole.net/0gQQjMxi/
and the docker-compose.yml file:
version: "3.7"
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
cloudflared:
container_name: cloudflared_pihole
image: visibilityspots/cloudflared
restart: unless-stopped
networks:
backend:
ipv4_address: 172.31.0.200
pihole:
container_name: pihole
image: pihole/pihole:latest
hostname: Raspi3
restart: unless-stopped
ports:
- "53:53/tcp"
- "53:53/udp"
- "8053:80/tcp"
environment:
- TZ='Europe/Madrid'
- WEBPASSWORD='rXtvAtZb'
- ADMIN_EMAIL='antonio.orvay@gmail.com'
- DNSMASQ_LISTENING=all
# - INTERFACE=eth0
# - USER_UID=1000
# - USER-GID=1000
- PIHOLELOG=/dev/null
- DNS1=10.0.0.2#5054
- DNS2=8.8.8.8#53
- IPv6=false
extra_hosts:
- "tplink.local:192.168.1.6"
- "router.local:192.168.1.1"
dns:
- 127.0.0.1
- 1.1.1.1
# Volumes store your data between container upgrades
volumes:
- './etc-pihole:/etc/pihole'
- './etc-dnsmasq.d:/etc/dnsmasq.d'
# Recommended but not required (DHCP needs NET_ADMIN)
# https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
depends_on:
- dhcphelper
cap_add:
- NET_ADMIN
labels:
- traefik.enable=true
- traefik.docker.network=web
- traefik.http.routers.pihole.entrypoints=websecure
- traefik.http.routers.pihole.rule=Host(`pihole.orvay.duckdns.org`)
- traefik.http.routers.pihole.service=pihole
- traefik.http.services.pihole.loadbalancer.server.port=80
- traefik.http.routers.pihole.middlewares=pihole-prefix@file
networks:
backend:
ipv4_address: '172.31.0.100'
web: {}
dhcphelper:
build: ./dhcp-helper
restart: unless-stopped
container_name: Pihole_dhcp_helper
network_mode: "host"
command: -s 172.31.0.100
cap_add:
- NET_ADMIN
networks:
web:
external: true
backend:
ipam:
config:
- subnet: 172.31.0.0/16
The log is showing that the container is based on an image that is not tagged.
*** [ DIAGNOSING ]: Operating system
[i] Pi-hole Docker Container: PIHOLE_DOCKER_TAG is unset
Can you do a docker-compose pull && docker-compose up -d
and do a new debug run please?
aorvay
December 26, 2021, 8:52pm
5
I just killed the containers, run a docker-compose pull and docker-compose up -d. After all this done, I generate new debug log, looks like still not tagged!!
Your debug token is: https://tricorder.pi-hole.net/41Nx69VR/
Maybe I'm doing something wrong, but previous version works fine.
I have two raspberry pi, one is a pi3 version and the other pi4 version, the pi3 has the new pihole version for testing before update the pihole on pi4 docker system.
I'd generated the debug on pi4 if you want to compare:
pi4 with previos pihole version: Your debug token is: https://tricorder.pi-hole.net/XvzzGuaz/
aorvay
December 26, 2021, 8:54pm
6
Sorry, one more thing for the dhcp-helper I followed, more or less, the instructions on:
I had been running Pi-hole with docker-compose on a RaspberryPi 3 for quite some time and it worked flawlessly. Since I use built-in DHCP functionality the Pi-hole container had been running with network_mode: "host":
version: "3"
services:
pihole:
image: pihole/pihole:latest
restart: unless-stopped
network_mode: "host"
cap_add:
- NET_ADMIN
environment:
...
Some time ago I tried to use bridge networking but could not get it to work. Have a look here .
Two weeks ag…
Thank you