No address range available for DHCP request via docker0

Help Community Help
1

The issue I am facing:
From time-to-time pihole is reporting:
no address range available for DHCP request via docker0
If it happens it is after a restart of the pihole docker container.

The container is started via docker-cli:

docker run -d \
  --name pihole-v6 \
  --network host \
  -v /opt/docker/pihole/v6/etc-pihole:/etc/pihole \
  -v /opt/docker/pihole/v6/etc-dnsmasq.d:/etc/dnsmasq.d \
  -v /opt/docker/pihole/v6/var-log-pihole:/var/log/pihole \
  -e TZ=Europe/Amsterdam \
  -e FTLCONF_dns_queryLogging=false \
  -e FTLCONF_webserver_port="192.168.139.235:88" \
  -e FTLCONF_webserver_interface_theme=default-light \
  -e FTLCONF_misc_etc_dnsmasq_d=true \
  -e FTLCONF_dns_listeningMode=all \
  -e PIHOLE_UID=900 \
  -e PIHOLE_GID=900 \
  --cap-add=NET_ADMIN \
  --cap-add=CAP_CHOWN \
  --restart unless-stopped \
  pihole/pihole

Is it save to exclude this docker0 interface from dhcp with

no-dhcpv4-interface=docker0
no-dhcpv6-interface=docker0

For those who are interested and have access:
https://tricorder.pi-hole.net/6NqNCG6V/

Details about my system:
Latest pihole v6 running as a docker container with network host mode.

What I have changed since installing Pi-hole:
Added vlans and some other config details.

2

Yes (unless you'd want other containers on Docker's default bridge to acquire leases through Pi-hole).

3

Nope - I just use the host network with Docker containers - good enough for a home lab.

If I 'm running out of tcp ports I start a new LXC container or VM. If that is not possible I may consider the docker mac-vlan network - but never needed this.