unbound-docker-stats VS unbound-docker

You are absolutely right!

Anyway, I bit the pill and moved from chroot'ing to distroless and I didn't regret it. The image is so much more secure now and since I try to work smart, I've also implemented workflows to automatically update my image when an Unbound update was released by NLnet Labs.

Some users were expecting issues regading the changed config parameters but so far it looks nice and I had less to do than I was expecting.

One perfect addition was flanging redis as cachedb onto unbound. The performance is extraordinary via UnixSocket which I made possible by using a proxy image which holds the redis.sock to make it available to the limited _unbound user.

Another thing is that you can set environment variables in your compose file, so the uid and gid ain't hardcoded anymore. Yes @kernbug is a MVP to me.

If you use Zabbix and like graphs in Grafana like I do, check out my unbound-docker-stats: <https://github.com/madnuttah/unbound-docker-stats> which should be usable with any unbound-docker image with my 'frankensteined' healthcheck script.

I hope you like what I do and I'm keen to hear your constructive criticism.

You'll find the image's sources here: <https://github.com/madnuttah/unbound-docker-stats>

Cheers and all the best,

Zabbix Unbound Statistics

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'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.

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.

You can also use Unbound for recursive DNS in a docker container: https://github.com/MatthewVance/unbound-docker

https://github.com/MatthewVance/unbound-docker/blob/master/1.14.0/data/unbound.sh

# 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