pi-hole/docker-pi-hole

The official Pi-hole Docker image from pi-hole.net

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 5th, 2026
Created on February 2nd, 2016
Open Issues & Pull Requests: 12 (+0)
GitHub issues: Enabled
Number of forks: 1,247
Total Stargazers: 11,533 (+0)
Total Subscribers: 115 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.3 hours
Mean response time: 20.5 days
90th percentile: 13.2 days
Tracked items: 180

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 7% of issues opened in the past year have been closed. Three people close 54% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,208 days
Stale 30+ days: 6
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (33)
  • never-stale (11)
  • v6 (9)
  • Submitter Attention Required (6)
  • bug (5)
  • documentation (5)
  • Fixed in next release (4)
  • Help Wanted (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Docker Pi-hole is a Docker container image that runs Pi-hole, a network-wide ad blocker using DNS filtering.

The tool solves the problem of intrusive advertisements and tracking across all devices on a network by intercepting DNS queries and blocking requests to known ad-serving domains. It works by running Pi-hole as a containerized service that acts as a DNS server for your network, filtering queries before they reach the internet. The container includes built-in cron jobs that automatically update ad-blocking lists weekly, keeping defenses current without manual intervention.

Developers and network administrators managing home or small office networks should choose this tool if they want centralized ad blocking without dedicated hardware. It suits any environment where Docker is already deployed, as it simplifies installation and updates compared to running Pi-hole on bare metal. The tool is particularly valuable for those who want to avoid the `--privileged` flag and prefer explicit capability configuration for security. Users relying on automatic container updates via Watchtower should consult the documentation for specific considerations before deploying.

The project maintains multiple release channels to serve different needs: stable releases tagged by date, a latest tag for the most recent version, and nightly builds from the development branch for those testing experimental features. Release notes consistently document changes across all Pi-hole components, providing transparency about what each version includes. The development activity shows active maintenance with attention to user-reported issues, such as documented problems with certain Docker configurations that led to updated guidance.