docker-pi-hole
netplan
Our great sponsors
docker-pi-hole | netplan | |
---|---|---|
203 | 32 | |
7,809 | 621 | |
2.9% | 9.2% | |
7.8 | 9.4 | |
5 days ago | 5 days ago | |
Shell | Python | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
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?
netplan
- Trunk/VLAN tags question
-
AWS to start charging for IPv4 usage, but critical services don't support IPv6
For Netplan-based stuff, this looks similar:
* https://github.com/canonical/netplan/blob/main/examples/dire...
I recently had to switch ISPs to one that doesn't do IPv6 for FTTH (but their smart offerings are (AFAICT) IPv6-only), but my previous IPv6 did, and activating it for my home network was a couple clicks on my Asus router.
-
Am I the only one who hates netplan?
I'm not sure how far back you want to go, but you can install the ifupdown package and remove netplan.io. But, even in Ubuntu 16, they were starting to phase it out. So, you're going to hit some bugs here.
-
Ubuntu 22.04 Netplan gateway4 deprecated
I was working with my Ubuntu 22.04 server and configuring my network with Netplan. After executing the Netplan apply command, I got an error message like the following:
-
Why even bother??
Doesn't Ubuntu server use netplan.io by default?
-
Can't connect to wifi
The interfaces on omv are managed by netplan. https://netplan.io/
-
Setting up private network with a gateway
This is because Ubuntu Desktop uses NetworkManager to manage all the network interfaces by default. It is the application responsible for network management via UI. This is not the case in Ubuntu Server which I will be using. The documentation can be found here NetworkManager It can be completely turned off by choosing a different renderer or a specific networking interface can be excluded from under management of NetworkManager. The configuration is in the file /etc/NetworkManager/NetworkManager.conf. On UI less versions like Ubuntu Server there is no NetworkManager installed. The default network renderer is systemd-networkd. In both flavours of Ubuntu the networking configuration is done via Netplan and the configuration for Netplan is stored in yaml file in the location /etc/netplan/*.yaml. There could be more than one configuration file. More information on this are to be found in the provided link.
-
Trying to upgrade 18.04 to 22.04; stuck at 20.04 with errors... please help
nautilus-extension-gnome-terminal nautilus-gtkhash nautilus-sendto nemo-fileroller neofetch net-tools netcat-openbsd netplan.io network-manager network-manager-config-connectivity-ubuntu network-manager-gnome
-
Why BSD over Linux?
https://netplan.io/, yes?
- Ethernet Con Problem On Ubuntu Server 20.04
What are some alternatives?
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
wireguard-vyatta-ubnt - WireGuard for Ubiquiti Devices
docker-pihole-unbound - Run Pi-Hole + Unbound on Docker
containerd - An open and reliable container runtime
crowdsec - CrowdSec - the open-source and participative security solution offering crowdsourced protection against malicious IPs and access to the most advanced real-world CTI.
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
watchtower - A process for automating Docker container base image updates.
docs - Repo for documents
caddy-docker-proxy - Caddy as a reverse proxy for Docker
session-manager-plugin - This plugin helps you to use the AWS Command Line Interface (AWS CLI) to start and end sessions to your managed instances
docker-wireguard
fck-nat - Feasible cost konfigurable NAT: An AWS NAT Instance AMI