Hi,
I'm running Pi-Hole in a Docker container and I've configured it as DNS. I'd like to use https://pi.hole/admin/login to login into the web interface. It works, when I try it from the host of the Docker container, but it doesn't work from other computers. I've checked with nslookup:
$ nslookup pi.hole
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: pi.hole
Address: 172.27.0.3
172.27.0.3 is the internal Docker IP address, which can only be accessed from the Docker host.
How can I configure it to something like 192.169.178.123?
I've read about ServerIP in some older threads, but it doesn't seem to work anymore.
My docker-compose.yml:
services:
pihole:
container_name: pihole
image: pihole/pihole:2025.06.2
ports:
# DNS Ports
- "127.0.0.1:53:53/tcp"
- "127.0.0.1:53:53/udp"
- "192.168.178.28:53:53/tcp"
- "192.168.178.28:53:53/udp"
# Default HTTP Port
- "127.0.0.1:80:80/tcp"
- "192.168.178.28:80:80/tcp"
# Default HTTPs Port. FTL will generate a self-signed certificate
- "127.0.0.1:443:443/tcp"
- "192.168.178.28:443:443/tcp"
# Uncomment the line below if you are using Pi-hole as your DHCP server
#- "67:67/udp"
# Uncomment the line below if you are using Pi-hole as your NTP server
#- "123:123/udp"
environment:
# Set the appropriate timezone for your location (https://en.wikipedia.org/wiki/List_of_tz_database_time_zones), e.g:
TZ: 'Europe/Berlin'
# Set a password to access the web interface. Not setting one will result in a random password being assigned
FTLCONF_webserver_api_password: 'correct horse battery staple'
# If using Docker's default `bridge` network setting the dns listening mode should be set to 'all'
FTLCONF_dns_listeningMode: 'all'
ServerIP: 192.168.178.28
# Volumes store your data between container upgrades
volumes:
# For persisting Pi-hole's databases and common configuration file
- /etc/pihole
# Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you should keep it enabled for the first v6 container start to allow for a complete migration. It can be removed afterwards. Needs environment variable FTLCONF_misc_etc_dnsmasq_d: 'true'
#- './etc-dnsmasq.d:/etc/dnsmasq.d'
cap_add:
# See https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
# Required if you are using Pi-hole as your DHCP server, else not needed
- NET_ADMIN
# Required if you are using Pi-hole as your NTP client to be able to set the host's system time
- SYS_TIME
# Optional, if Pi-hole should get some more processing time
- SYS_NICE
restart: unless-stopped