rlabinc/pihole-unbound

pihole-unbound

!https://img.shields.io/docker/pulls/rlabinc/pihole-unbound.svg?style=flat&label=pulls&logo=docker !https://img.shields.io/docker/image-size/rlabinc/pihole-unbound/latest?style=flat&logo=docker&label=pihole-unbound !https://img.shields.io/docker/image-size/pihole/pihole/latest?style=flat&logo=docker&label=pihole-official !https://img.shields.io/github/stars/origamiofficial/docker-pihole-unbound?style=social https://img.shields.io/endpoint?label=Support&style=flat&url=https%3A%2F%2Fmogyo.ro%2Fquart-apis%2Ftgmembercount%3Fchat_id%3Dpihole_unbound]([***] !https://img.shields.io/badge/we%20stand%20with-%F0%9F%87%B5%F0%9F%87%B8%20palestine-white.svg

Level up your network with cutting-edge tech. This Docker container effortlessly combines https://github.com/pi-hole/pi-hole and https://github.com/NLnetLabs/unbound, giving you the ultimate privacy and performance combo in a single package. It's the future of network management, available today.

!https://raw.githubusercontent.com/origamiofficial/docker-pihole-unbound/main/banner.png

[!NOTE] Development for the development tag is currently ongoing, there could be some bugs. The development tag uses Alpine Linux. If you're familiar with Alpine, we encourage you to check out the https://github.com/origamiofficial/docker-pihole-unbound/blob/main/Dockerfile-Dev-V6 file. Your contributions are highly appreciated!

Supported Architectures

We utilise the docker buildx for multi-platform awareness. More information is available from docker https://docs.docker.com/buildx/working-with-buildx/.

Simply pulling rlabinc/pihole-unbound:latest should retrieve the correct image for your arch, but you can also pull specific arch images via --platform.

The architectures supported by this image are:

Usage

Docker run

Here are the commands you'll need:

bash
docker run -d \
  --name=pihole-unbound \
  -e TZ=Europe/London `#optional` \
  -p 53:53/tcp -p 53:53/udp \
  -p 80:80/tcp `#Pi-hole web interface port` \
  -e WEBPASSWORD='qwerty123' `#better to use single quotes` \
  --restart=always \
  rlabinc/pihole-unbound:latest

Docker Compose

To deploy this project using Docker Compose, you can use the following example docker-compose.yml:

yaml
version: '3'

services:
  pihole-unbound:
    image: rlabinc/pihole-unbound:latest
    container_name: pihole-unbound
    environment:
      - TZ=Europe/London # Adjust timezone as needed
      - WEBPASSWORD=qwerty123 # Set a secure password
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "80:80/tcp" #Pi-hole web interface port
    restart: always

This example configuration will run Pi-hole with Unbound, listening on port 53 for DNS queries and port 80 for the web interface. Make sure to adjust the environment variables, password, and timezone according to your setup.

To start the container, use:

bash
docker-compose up -d

To stop the container, use:

bash
docker-compose down

[!TIP] Mikrotik users: Facing cp: cannot create special file, the solution was letting RouterOS create the mounted volume itself, and not manually creating a "directory" beforehand. As result, the mount appears as "container store" (so not a "directory"), accessible via SFTP (and not via Winbox/WebFig) for pushing custom Unbound config. - https://github.com/origamiofficial/docker-pihole-unbound/issues/30#issuecomment-2526363715

Docker Tags

The Docker tags supported by this image are:

[!NOTE] The development has been entirely redesigned from the ground up and contains many https://github.com/pi-hole/docker-pi-hole/blob/development-v6/README.md, for more info regarding development visit here.

Installing on Ubuntu

Modern releases of Ubuntu (17.10+) include http://manpages.ubuntu.com/manpages/bionic/man8/systemd-resolved.service.8.html which is configured by default to implement a caching DNS stub resolver. This will prevent pi-hole from listening on port 53. The stub resolver should be disabled with: sudo sed -r -i.orig 's/#?DNSStubListener=yes/DNSStubListener=no/g' /etc/systemd/resolved.conf

This will not change the nameserver settings, which point to the stub resolver thus preventing DNS resolution. Change the /etc/resolv.conf symlink to point to /run/systemd/resolve/resolv.conf, which is automatically updated to follow the system's netplan: sudo sh -c 'rm /etc/resolv.conf && ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf' After making these changes, you should restart systemd-resolved using systemctl restart systemd-resolved

Once pi-hole is installed, you'll want to configure your clients to use it (see here). If you used the symlink above, your docker host will either use whatever is served by DHCP, or whatever static setting you've configured. If you want to explicitly set your docker host's nameservers you can edit the netplan(s) found at /etc/netplan, then run sudo netplan apply. Example netplan:

yaml
network:
    ethernets:
        ens160:
            dhcp4: true
            dhcp4-overrides:
                use-dns: false
            nameservers:
                addresses: [127.0.0.1]
    version: 2

Note that it is also possible to disable systemd-resolved entirely. However, this can cause problems with name resolution in s (https://bugs.launchpad.net/network-manager/+bug/). It also disables the functionality of netplan since systemd-resolved is used as the default renderer (http://manpages.ubuntu.com/manpages/bionic/man5/netplan.5.html#description). If you choose to disable the service, you will need to manually set the nameservers, for example by creating a new /etc/resolv.conf.

Users of older Ubuntu releases (circa 17.04) will need to disable dnsmasq.

Parameters

Container images are configured using parameters passed at runtime (such as those above).

This Docker container supports all Pi-hole official Docker container environment variables available https://github.com/pi-hole/docker-pi-hole/#environment-variables.

Quick Links

• *** Support
• https://github.com/pi-hole/docker-pi-hole
• https://github.com/NLnetLabs/unbound
• https://github.com/origamiofficial/docker-pihole-unbound
• https://hub.docker.com/r/rlabinc/pihole-unbound

Acknowledgements

The code in this image is heavily influenced by MatthewVance's unbound-docker with the help of chriscrowe's docker-pihole-unbound server Docker image configs, However, the upstream projects most certainly also deserve credit for making this all possible.

• https://github.com/pi-hole.
• https://github.com/NLnetLabs.
• https://github.com/MatthewVance.
• https://github.com/chriscrowe.
• https://github.com/madnuttah.
• The many other devs who got me inspired!

Warning

I'm not responsible if your internet goes down using this Docker container. Use at your own risk.