← Directory

pihole-v6-unbound

This Docker deployment runs both Pi-Hole version 6 and Unbound in a single container.

  • Network Services
  • Security
  • Tools & Utilities
This Docker deployment runs both Pi-Hole version 6 and Unbound in a single container. The base image for the container is the official Pi-Hole docker 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.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

71/100 Good

Maintained
84last commit 16 days ago
Popular
631,335 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
95512 MB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 3 days ago

GitHub stars
1,335
Open issues
81
Last commit
2026-09-26
Latest release
2026.09.0-unbound1.25.2-r2
Activity
rising

Checked 4 days ago - source: GitHub (mpgirro/docker-pihole-unbound)

Resources & Compatibility

Minimum requirements: 512 MB RAM, 2 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 14 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install with Helm and a values file Use Helm (Kubernetes' package installer) to install the Pi-hole chart and attach your values file, for example: helm install pihole mojo2600/pihole -f values.yaml. If you skip the values file, Pi-hole may start with defaults and miss your network, storage, or DHCP settings. source
  • Keep Pi-hole data on a saved volume Set persistentVolumeClaim.enabled to true and give it a size, such as 500Mi, so Pi-hole's database, logs, and ad lists survive restarts. Without a saved volume, restarting or updating the container can make you lose settings and start over. source
  • Set DHCP range only if you use DHCP If Pi-hole will assign IP addresses, set DHCP_ACTIVE to "1" and fill in DHCP_START, DHCP_END, DHCP_ROUTER, and DHCP_LEASETIME. Wrong or missing DHCP values can stop devices from getting an IP or send them to the wrong router. source

Fetched 14 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which image should I use if I previously used cbcrowe/pihole-unbound?

Use mpgirro/pihole-unbound from Docker Hub or GitHub Container Registry. The old cbcrowe image is deprecated and no longer receives updates.

Do I need a separate Unbound container for this image?

No. The image includes and configures Unbound directly inside the Pi-hole container, so you do not need to set up and link another Unbound container.

How do I update the container?

Run docker compose pull and docker compose up -d. A weekly rebuild overwrites latest and the Pi-hole version tag to pick up new packages.

Answers sourced from github.com

Community

Collected 9 days ago - public community threads