docker-pi-hole
unbound-docker
Our great sponsors
docker-pi-hole | unbound-docker | |
---|---|---|
203 | 13 | |
7,809 | 509 | |
2.9% | - | |
7.8 | 6.3 | |
4 days ago | 5 days ago | |
Shell | Shell | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker-pi-hole
-
Problem - Pi-Hole not getting many DNS requests
Yesterday I deployed the official pi hole docker container on my raspberry pi 3 and set a custom DNS address on my phone addressing to the pi.
-
Help with container seeing gateway as the return address
#pihole pihole: container_name: pihole image: pihole/pihole:latest ports: - target: 53 published: 53 protocol: tcp mode: host - target: 53 published: 53 protocol: udp mode: host - "67:67/udp" - "8070:80/tcp" - "8073:443/tcp" environment: TZ: 'America/Indianapolis' WEBPASSWORD: #'TEMP_PASSWORD' #'set a secure password here or it will be random' WEBPASSWORD_FILE: '/etc/pihole/adminpw.txt' # Volumes store your data between container upgrades volumes: - '~/pihole/etc-pihole:/etc/pihole' - '~/pihole/etc-dnsmasq.d:/etc/dnsmasq.d' # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities cap_add: - NET_ADMIN # Recommended but not required (DHCP needs NET_ADMIN) #network_mode: host restart: unless-stopped #UPTIME KUMA uptime_kuma: image: louislam/uptime-kuma:1 container_name: uptime-kuma volumes: - uptime-kuma:/app/data ports: - 8060:3001 restart: always
-
No internet access for containers co-hosted with pihole
version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ networks: dns_net: driver: bridge ipam: config: - subnet: 10.2.0.0/24 services: pihole: depends_on: [unbound] container_name: pihole image: pihole/pihole:latest hostname: pihole networks: dns_net: ipv4_address: 10.2.0.100 ports: - "5335:53/tcp" - "5335:53/udp" - "7000:80/tcp" environment: TZ: ${TZ} WEBPASSWORD: ${PWD} FTLCONF_LOCAL_IPV4: ${HOST_IP} # Set to server's LAN IP, used by web block modes. PIHOLE_DNS_: 10.2.0.200 # Upstream DNS server(s) for Pi-hole to forward queries to, separated by a semicolon DNSMASQ_LISTENING: all # "Listen on all interfaces, permit all origins" # Volumes store your data between container upgrades volumes: - /var/lib/docker/volumes/pihole/etc-pihole:/etc/pihole - /var/lib/docker/volumes/pihole/etc-dnsmasq.d:/etc/dnsmasq.d healthcheck: disable: true restart: unless-stopped unbound: # https://github.com/MatthewVance/unbound-docker container_name: unbound image: mvance/unbound:latest hostname: unbound networks: dns_net: ipv4_address: 10.2.0.200 ports: - "${HOST_IP}:53:53/udp" - "${HOST_IP}:53:53/tcp" healthcheck: disable: true restart: unless-stopped
-
Synology/MACVLAN/BRIDGE help
services: pihole: container_name: pihole image: pihole/pihole:latest hostname: pihole # Container hostname (optional) domainname: mynetwork.local # Container domain (optional) mac_address: f7:55:63:b0:68:83 # Random MAC address (optional) networks: virtualnet: # Name of macvlan ipv4_address: 192.168.100.249 # Desired IP for pihole dns: - 127.0.0.1 - 1.1.1.1 ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" - "80:80/tcp" - "443:443/tcp" volumes: - ./pihole-configs/:/etc/pihole/ - ./dnsmasq.d-configs/:/etc/dnsmasq.d/ # DNSMASQ_USER # https://github.com/pi-hole/docker-pi-hole/issues/963 # https://github.com/pi-hole/docker-pi-hole/blob/master/README.md#upgrade-notes environment: FTLCONF_LOCAL_IPV4: 10.59.0.6 # Desired IP for pihole VIRTUAL_HOST: pihole.mynetwork.local DNSMASQ_USER: root PIHOLE_DNS_: 1.1.1.1;1.0.0.1;2606:4700:4700::1111;2606:4700:4700::1001 restart: unless-stopped # Set container to always restart
- Need a totally updated guide for setting up pi-hole on Synology DSM 7.1.1+
-
How does one create an OS image for Jetson Nano B01 4GB for Ubuntu 23.04?
You could have a look at docker and try to run a more recent Ubuntu image on the Nano https://github.com/pi-hole/docker-pi-hole
-
Error Question
My advice would be either use the docker-pi-hole documentation/quick start, or contact the content creator.
- Phiole in docker
- PiHole via docker compose on a Proxmox VM having issue with DNS on the VM
- Can OMV6 do DHCP and DNS?
unbound-docker
-
No internet access for containers co-hosted with pihole
version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ networks: dns_net: driver: bridge ipam: config: - subnet: 10.2.0.0/24 services: pihole: depends_on: [unbound] container_name: pihole image: pihole/pihole:latest hostname: pihole networks: dns_net: ipv4_address: 10.2.0.100 ports: - "5335:53/tcp" - "5335:53/udp" - "7000:80/tcp" environment: TZ: ${TZ} WEBPASSWORD: ${PWD} FTLCONF_LOCAL_IPV4: ${HOST_IP} # Set to server's LAN IP, used by web block modes. PIHOLE_DNS_: 10.2.0.200 # Upstream DNS server(s) for Pi-hole to forward queries to, separated by a semicolon DNSMASQ_LISTENING: all # "Listen on all interfaces, permit all origins" # Volumes store your data between container upgrades volumes: - /var/lib/docker/volumes/pihole/etc-pihole:/etc/pihole - /var/lib/docker/volumes/pihole/etc-dnsmasq.d:/etc/dnsmasq.d healthcheck: disable: true restart: unless-stopped unbound: # https://github.com/MatthewVance/unbound-docker container_name: unbound image: mvance/unbound:latest hostname: unbound networks: dns_net: ipv4_address: 10.2.0.200 ports: - "${HOST_IP}:53:53/udp" - "${HOST_IP}:53:53/tcp" healthcheck: disable: true restart: unless-stopped
-
I've created a simple 2 container Pihole + Unbound Docker Setup for you to use
I'm not an unbound expert, but as far as I understand MatthewVance's image, unbound is already configured properly: https://github.com/MatthewVance/unbound-docker/blob/master/1.17.1/data/unbound.sh. I didn't want to go into detail how pi-hole or unbound works, since I think there is enough documentation on that.
-
Problems with unbound
I am successfully running pihole on a different machine, but am planning to migrate to a new docker host. I figured this would be a good time to configure pihole with unbound. I am attempting to run unbound in a docker container running on Opensuse leap and I am using this docker image.
- Need help w/ unbound
-
Pihole with Recursive DNS
You can also use Unbound for recursive DNS in a docker container: https://github.com/MatthewVance/unbound-docker
- Pihole & Unbound Docker?
- Starting Unbound in a Docker Container
-
When using Unbound can’t connect to any site?
https://github.com/MatthewVance/unbound-docker/blob/master/1.14.0/data/unbound.sh
- Nothing but issues with unbound and dont know what to do.
-
Radarr installation fails on fresh Ubuntu install
# https://github.com/MatthewVance/unbound-docker unbound: container_name: unbound environment: PGID: $PGID PUID: $PUID TZ: $TZ image: mvance/unbound networks: smarthome: ipv4_address: 172.18.0.6 restart: always
What are some alternatives?
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
docker-pihole-unbound - Run Pi-Hole + Unbound on Docker
dnscrypt-server-docker - A Docker image for a non-censoring, non-logging, DNSSEC-capable, DNSCrypt-enabled DNS resolver
crowdsec - CrowdSec - the open-source and participative security solution offering crowdsourced protection against malicious IPs and access to the most advanced real-world CTI.
unbound-config - fragmented configuration files for unbound recursive dns resolver
watchtower - A process for automating Docker container base image updates.
unbound-docker-rpi - Run Unbound with latest version of OpenSSL on Raspberry Pi with Docker.
caddy-docker-proxy - Caddy as a reverse proxy for Docker
docker-radarr
docker-wireguard
dns-server-setup - Ansible playbook to easily deploy new, fully configured, DNS servers.