The original post: /r/pihole by /u/IAmMoonie on 2025-02-01 10:28:46.

Hey folks, I have my pihole and caddy set up via Portainer.

My pihole stack looks like:

services:
 pihole:
 container*name: pihole
 image: pihole/pihole:latest
 hostname: pihole
 restart: unless-stopped
 networks:
 - public-proxy
 ports:
 - "53:53/tcp"
 - "53:53/udp"
 - "853:853/tcp" # DNS-over-TLS 
 - "8081:80/tcp"
 environment:
 TZ: "${TZ}"
 WEBPASSWORD: "${WEBPASSWORD}"
 PIHOLE\_DNS*: "${PIHOLE\_DNS}"
 DNSMASQ\_LISTENING: "${DNSMASQ\_LISTENING}"
 VIRTUAL\_HOST: "${VIRTUAL\_HOST}"
 FTLCONF\_LOCAL\_IPV4: "${FTLCONF\_LOCAL\_IPV4}"
 volumes:
 - /mnt/nvme/docker-persistent/pihole/external.conf:/etc/lighttpd/external.conf:ro
 - pihole\_data:/etc/pihole
 - dnsmasq\_data:/etc/dnsmasq.d
 # cap\_add:
 # - NET\_ADMIN
 dns:
 - "127.0.0.1"
 - "1.1.1.1"

volumes:
 pihole\_data:
 dnsmasq\_data:

networks:
 public-proxy:
 driver: bridge

As we can see, my network is set as public-proxy. Caddy as well as some other applications have been set up in the same way. However if I do some checking:

docker inspect pihole | grep "Networks" -A 5
 "Networks": {
 "pihole\_public-proxy": {
 "IPAMConfig": null,
 "Links": null,
 "Aliases": [
 "pihole",

Is this normal? pihole_public-proxy. I can’t find any documentation showing that this would happen?