A Docker image for running Pi-hole with integrated Unbound DNS resolver in a single container.
This is the official and maintained successor repository of the original cbcrowe/pihole-unbound image by @chriscrowe
TL;DR: The image changed. chriscrowe/pihole-unbound is deprecated and no longer receives updates. Change your setup to use the new image mpgirro/pihole-unbound.
The base image for the container is the official Pi-Hole container, with an extra build step added to install the Unbound resolver directly into to the container based on instructions provided directly by the Pi-Hole team.
- Automated Builds: The Docker image is automatically built and published using GitHub Actions and Renovate, ensuring you always have access to the latest version.
- Unbound integration: The Unbound DNS resolver is directly integrated and configured within this image. No need for setting up and linking a separate Unbound container.
- Multi-Registry Publishing: Images are published to both Docker Hub and GitHub Container Registry (GHCR), giving you flexibility in where you pull your images from.
- Consistent Tagging: Images are tagged with the same version tags as the official Pi-hole images.
The example Docker Compose file demonstrates how this image can be used.
Important: If you have an old setup using cbcrowe/pihole-unbound, you need to migrate to one of the image locations mentioned below.
- Docker Hub:
docker pull mpgirro/pihole-unbound - GitHub Container Registry:
docker pull ghcr.io/mpgirro/docker-pihole-unbound
You can use all environment variables supported by the official Pi-hole container. Some examples are listed below. Vars and descriptions are replicated from the official documentation:
| Variable | Default | Value | Description |
|---|---|---|---|
TZ |
UTC | <Timezone> |
Set your timezone to make sure logs rotate at local midnight instead of at UTC midnight. |
FTLCONF_webserver_api_password |
random | <Admin password> |
http://pi.hole/admin password. Run docker logs pihole | grep random to find your random password. |
FTLCONF_dns_upstreams |
127.0.0.1#5335 |
IPs delimited by ; |
Upstream DNS server(s) for Pi-hole to forward queries to, separated by a semicolon. Supports non-standard ports with: #[port number], e.g 127.0.0.1#5053;8.8.8.8;8.8.4.4.Supports Docker service names and links instead of IPs, e.g upstream0,upstream1 where upstream0 and upstream1 are the service names of or links to docker services.Note: The existence of this environment variable assumes this as the sole management of upstream DNS. Upstream DNS added via the web interface will be overwritten on container restart/recreation. |
FTLCONF_[SETTING] |
unset | As per documentation | Customize pihole.toml with settings described in the API Documentation. Replace . with _, e.g for dns.dnssec=true use FTLCONF_dns_dnssec: 'true'.Array type configs should be delimited with ;. |
Alternatively you can use an .env file in the same directory as your compose.yaml file:
TZ=America/Los_Angeles
WEBPASSWORD=ChangeMe!
REV_SERVER=true
REV_SERVER_DOMAIN=local
REV_SERVER_TARGET=192.168.1.1
REV_SERVER_CIDR=192.168.0.0/16
HOSTNAME=pihole
DOMAIN_NAME=pihole.local
PIHOLE_WEBPORT=80
WEBTHEME=default-light
WEB_PORT=80
Please file issues as follows:
- Pi-hole: For issues related to Pi-hole itself, please report them directly in the Pi-hole repository.
- Unbound: For issues related to the Unbound DNS resolver, please use the Unbound repository.
- Image Publishing: For issues specifically related to the image publishing (e.g., missing tags, images not being updated or published correctly), report them here in this repository.