libnetwork
docker-pi-hole
Our great sponsors
libnetwork | docker-pi-hole | |
---|---|---|
8 | 203 | |
2,120 | 7,809 | |
0.5% | 2.9% | |
3.3 | 7.8 | |
6 months ago | 6 days ago | |
Go | Shell | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
libnetwork
-
Docker Networking: A Step-by-Step Guide for Developers
Container network model is a standard proposed by Docker that provides a well-defined interface or API that helps in establishing connections between containers and network plugins. Libnetwork is the native Go implementation of the CNM for connecting containers. It provides an interface between the Docker engine and network drivers. It is built on 3 main components: Sandbox, Endpoint, Network
-
Podman 4.0.0
Thanks! It seems that netavark uses macvlan to avoid creating bridge devices. Although it can also use bridges, and it seems that Docker is adding macvlan support too: https://github.com/moby/libnetwork/blob/master/docs/macvlan....
- The docker plugin API documentation is basically nonexistent
- Dedicated Ipv6 to each container
-
Is Docker Swarm broken?
I'm having an issue with docker daemon crashing only when using overlay networks. May 21 05:54:59 svr dockerd[13153]: time="2021-05-21T05:54:59.535581254-03:00" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint e8t3rwhuv3r0llsv43rup41vr ab46637f5a936ecc74bc6216601b4df118e758c02512e31a477466cd72c99526], retrying...." this error deleted my network and then crashed all the containers that were using it, container State: "Error": "failed to get network during CreateEndpoint: network e8t3rwhuv3r0llsv43rup41vr not found", "ExitCode": 128, sometimes it exits with code 0 and 143 too I found this similar issue, but it seems abandoned https://github.com/moby/libnetwork/issues/2341
- Pihole DNS does not work in WireGuard when both are in separate docker containers on the same machine
- Docker breaks IPv6 binding in patch update
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?
What are some alternatives?
compose-spec - The Compose specification
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
podman-desktop-companion - Podman desktop companion
docker-pihole-unbound - Run Pi-Hole + Unbound on Docker
cri-dockerd - dockerd as a compliant Container Runtime Interface for Kubernetes
crowdsec - CrowdSec - the open-source and participative security solution offering crowdsourced protection against malicious IPs and access to the most advanced real-world CTI.
firebuild - Convenience of containers, security of virtual machines
watchtower - A process for automating Docker container base image updates.
mariadb-podman-socket-activat
caddy-docker-proxy - Caddy as a reverse proxy for Docker
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
docker-wireguard