WARNING: dnsmasq: no address range available for DHCP request via eth0

Expected Behaviour:

I expect Pi-hole's DHCP server to assign IP addresses in the range 192.168.1.50-192.168.1.150 to devices on my network. When a device requests an IP via DHCP.

I had it setup correctly previously but i recently did a full homelab reset and i cant seem to get it working again.

Operating System: Ubuntu 26.04
Hardware: HP EliteDesk
Docker Version: Docker version 29.1.3, build 29.1.3-0ubuntu4

Docker Compose File:

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
      - "5353:53/tcp"
      - "5353:53/udp"
      - "81:80/tcp"
      - "444:443/tcp"
      - "67:67/udp"
    environment:
      TZ: 'Europe/London'
      FTLCONF_dns_listeningMode: 'ALL'
    volumes:
      - './etc-pihole:/etc/pihole'
      - './etc-dnsmasq.d:/etc/dnsmasq.d'
    cap_add:
      - NET_ADMIN
      - SYS_TIME
    restart: unless-stopped

Debug Token:

https://tricorder.pi-hole.net/kzpp73jW/

You are using the default network mode (bridge) for Pi-hole container.

Please read the documentation: Docker DHCP and Network Modes - bridge networking

Or use a different network mode (also on the same documentation page).

Unrelated to your issue:

The devices on your network will always send DNS queries to port 53.

Ports 5353 won't work (unless you are redirecting all DNS queries to 5353 using some other service).

If your container is complaining about "port already in use", the correct solution is to disable the other service using port 53.

Check the Tips and Tricks, from our docker documentation.

Thank you ill try this out now im quite new to homelabbing let alone anything with networks so i was assuming it was a rookie mistake thank you for the help!