- docker-pi-hole VS Nginx Proxy Manager
- docker-pi-hole VS docker-pihole-unbound
- docker-pi-hole VS crowdsec
- docker-pi-hole VS caddy-docker-proxy
- docker-pi-hole VS watchtower
- docker-pi-hole VS docker-wireguard
- docker-pi-hole VS docker-icloudpd
- docker-pi-hole VS log2ram
- docker-pi-hole VS Portainer
- docker-pi-hole VS docker
Docker-pi-hole Alternatives
Similar projects and alternatives to docker-pi-hole
-
Nginx Proxy Manager
Docker container for managing Nginx proxy hosts with a simple, powerful interface
-
-
Scout APM
Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.
-
-
watchtower
A process for automating Docker container base image updates.
-
crowdsec
CrowdSec - the open-source and participative IPS able to analyze visitor behavior & provide an adapted response to all kinds of attacks. It also leverages the crowd power to generate a global CTI database to protect the user network.
-
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
-
-
-
-
docker-icloudpd
An Alpine Linux 3.13.5 container for the iCloud Photos Downloader command line utility
-
Docker Compose
Define and run multi-container applications with Docker
-
-
-
node-red-docker
Repository for all things Node-RED and Docker related
-
-
-
-
awesome-selfhosted
A list of Free Software network services and web applications which can be hosted on your own servers
-
docker-pi-hole reviews and mentions
-
Thousands of unknown requests
I've installed pi-hole using docker following this page https://github.com/pi-hole/docker-pi-hole and right after installing I noticed many requests from domains I don't recognize. I didn't even setup my computer to use pi-hole(localhost) as a DNS server.
-
Pihole with Recursive DNS
I don't use Unraid, but if it supports docker then yes you can run Pihole in a container (I use this): https://github.com/pi-hole/docker-pi-hole
-
Is it possible to install Pi-hole on Docker free version?
Absolutely, there is an official Github which contains much of the information you will require if you're already familiar with Docker and Docker-compose which you can find here.
-
Can't Start DHCP Server
I assume you've seen this?
- Issue: Pihole dashboard shows negative domains on Adlists
-
Assistance setting up unbound docker container alonside Pihole docker container
version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ services: pihole: container_name: pihole image: pihole/pihole:latest # For DHCP it is recommended to remove these ports and instead add: network_mode: "host" #ports: #- "53:53/tcp" #- "53:53/udp" #- "67:67/udp" # Only required if you are using Pi-hole as your DHCP server #- "80:80/tcp" network_mode: "host" environment: TZ: 'Canada/Eastern' WEBPASSWORD: *REDACTED* WEB_PORT: 8008 # Volumes store your data between container upgrades volumes: - '/home/*REDACTED*/docker/pihole/pihole:/etc/pihole' - '/home/*REDACTED*/docker/pihole/dnsmasq.d:/etc/dnsmasq.d' # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities cap_add: - NET_ADMIN # Required if you are using Pi-hole as your DHCP server, else not needed restart: unless-stopped
-
Dockerized pihole tcp and udp ports in use
#version: "2.1" services: #PIHOLE pihole: container_name: pihole hostname: piholedocker image: pihole/pihole:latest ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" - "80:80/tcp" networks: macvlan1: ipv4_address: 192.168.178.8 environment: TZ: Europe/Berlin WEBPASSWORD: 'secret you know' # Volumes store your data between container upgrades volumes: - /home/docker/pihole0:/etc/pihole - /home/docker/pihole0/dnsmasq.d:/etc/dnsmasq.d - /home/docker/pihole0/resolve.conf:/etc/resolv.conf #for dns-server # Recommended but not required (DHCP needs NET_ADMIN) # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities cap_add: - NET_ADMIN restart: always #NETWORKS networks: macvlan1: external: name: macvlan1
-
Unable to run Pi-Hole with Nginx because both use port 80
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
-
Docker Pihole wrong IP
Hey guys, I'm finishing the configuration of my pihole using docker-compose on a Windows host, and I noticed that internally the IP doesn't match with my local network address, it is a totally random address that changes every time I boot up the compose. I am not using my pihole as DHCP server, I'll set manually the DNS on my devices, and for that this thread fix won't work for me: DHCP server does not respect ServerIP variable · Issue #932 · pi-hole/docker-pi-hole · GitHub
-
ERROR Port 53 already in use, using ODROID N2+ and Docker.
pihole: container_name: pihole image: pihole/pihole:latest hostname: pihole # For DHCP it is recommended to remove these ports and instead add: network_mode: "host" ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server - "80:80/tcp" - "443:443/tcp" environment: TZ: 'Asia/Dubai' WEBPASSWORD: 'MyPassword' # Volumes store your data between container upgrades volumes: - '/opt/pihole/pihole:/etc/pihole' - '/opt/pihole/dnsmasq:/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) restart: unless-stopped
-
how to reverse proxy localhost to https localhost
so now you need someway to reddirect your url requests to the nginx proxy machine. Since you dont want to open ports, this will mean that you'll need to use an internal DNS. Basically something internal that catches these url requests (ie. app.domain.cc) and forwards it to the ip address of your nginx proxy manager. PiHole is just the easiest ways i know of doing that internal provate DNS https://github.com/pi-hole/docker-pi-hole
-
Got my hands on a poweredge r720 from r/homelabsales! This is my goal setup for the next few months. I'm learning Docker & Kubernetes right now on pluralsight.
Is this the source? https://github.com/pi-hole/docker-pi-hole
-
Wireguard + Pi-hole DNS broken on GL.iNet router
version: "2.1" networks: backend: driver: bridge ipam: config: - subnet: "172.19.0.0/24" services: wireguard: image: lscr.io/linuxserver/wireguard:1.0.20210914 container_name: wireguard cap_add: - NET_ADMIN - SYS_MODULE environment: - PUID=1000 - PGID=1000 - TZ=America/New_York - SERVERURL=redacted.duckdns.org #optional - SERVERPORT=51820 #optional - PEERS=redacted #optional - PEERDNS=auto #optional - INTERNAL_SUBNET=10.13.13.0 #optional - ALLOWEDIPS=192.168.4.0/24, 10.13.13.1 # this allows for split tunneling volumes: - /home/redacted/docker_data/wireguard/config:/config - /lib/modules:/lib/modules ports: - 51820:51820/udp sysctls: - net.ipv4.conf.all.src_valid_mark=1 # https://github.com/linuxserver/docker-wireguard/issues/106 dns: # https://github.com/linuxserver/docker-wireguard/issues/106 - 172.19.0.10 networks: backend: ipv4_address: 172.19.0.11 restart: unless-stopped pihole: container_name: pihole image: pihole/pihole:2022.02.1 # For DHCP it is recommended to remove these ports and instead add: network_mode: "host" ports: - "53:53/tcp" - "53:53/udp" # - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server - "80:80/tcp" environment: TZ: 'America/New_York' WEBPASSWORD: redacted # Volumes store your data between container upgrades volumes: - /home/redacted/docker_data/pihole/pihole:/etc/pihole # - /home/redacted/docker_data/pihole/resolv.conf:/etc/resolv.conf - /home/redacted/docker_data/pihole/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) # https://github.com/linuxserver/docker-wireguard/issues/106 dns: - 127.0.0.1 networks: backend: # https://github.com/linuxserver/docker-wireguard/issues/106 ipv4_address: 172.19.0.10 restart: unless-stopped
-
Pihole with Unbound and IPv6 Support in Docker
version: "3" networks: dns_net: driver: bridge enable_ipv6: true ipam: config: - subnet: 172.20.0.0/16 - subnet:*taken from my randomly generated subnet in /docker/daemon.json*:1:/64 # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ services: pihole: container_name: pihole image: pihole/pihole:latest networks: - dns_net ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server - "80:80/tcp" environment: TZ: 'America/Denver' WEBPASSWORD: '*password*' PIHOLE_DNS_: 'unbound' CUSTOM_CACHE_SIZE: '0' FTLCONF_REPLY_ADDR4: '*host IPv4*' FTLCONF_REPLY_ADDR6: '*host IPv6*' # Volumes store your data between container upgrades volumes: - './etc-pihole:/etc/pihole' - './etc-dnsmasq.d:/etc/dnsmasq.d' unbound: container_name: unbound image: mvance/unbound-rpi:latest networks: - dns_net ports: - "5053:53/tcp" - "5053:53/udp" volumes: - './etc-unbound:/etc/unbound' - './crontabs:/var/spool/cron/crontabs' restart: unless-stopped
- Cron using 100% CPU on PI
Stats
Popular Comparisons
Are you hiring? Post a new remote job listing for free.