How pi-hole/docker-pi-hole works
Docker Pi-hole packages Pi-hole as a container for network-wide DNS blocking. The main workflow is an operator starting the image, which exposes Pi-hole DNS and web access to the network; optional DHCP and NTP roles are also documented. A baked-in cron job periodically refreshes ad lists and flushes logs. The repository tree shows the container entrypoint and cron configuration, but no source excerpts were provided, so internal call relationships and implementation details are not inferred.
Main entry points: Dockerfile Pi-hole image · crontab.txt Cron schedule
Components 12
Container runtime
- Pi-hole image
src/Dockerfile - Container startup
src/start.sh
Scheduled maintenance
- Cron schedule
src/crontab.txt - Ad-list refresh
- Log flush
Network services
- DNS blocking
- Web interface
- DHCP service
- NTP service
Other components
- Operator
- Network clients
- Persistent volumes
Connections 11
- Operator → Pi-hole image: starts with Compose
README.md - Pi-hole image → DNS blocking: provides DNS
README.md - Pi-hole image → Web interface: exposes web access
README.md - Network clients → DNS blocking: queries
README.md - Operator → Web interface: configures access
README.md - Pi-hole image → Persistent volumes: mounts volumes
README.md - Pi-hole image → Cron schedule: includes cron
README.md - Cron schedule → Ad-list refresh: schedules weekly
README.md - Cron schedule → Log flush: schedules weekly
README.md - Pi-hole image → DHCP service: optionally provides
README.md - Pi-hole image → NTP service: optionally provides
README.md