You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe alternatives you've considered
The above solution creates 2 containers, which would be fine.
I've previously used https://github.com/chriscrowe/docker-pihole-unbound which has everything in one container.
I'm content with performing manual updates for both components and don't require an all-in-one solution. Being self-reliant in managing updates is important to me.
Additional context
I'm very happy with the way I have everything configured now. This would be the cream on the cake. :-)
The text was updated successfully, but these errors were encountered:
shaft8472
changed the title
UDM Pro 3.x, nspawn-container: Pihole + Unbound
Feature request: UDM Pro 3.x, nspawn-container -> Pihole + Unbound
Jul 23, 2023
@shaft8472 I upgraded to UniFiOS 3.1 this weekend, and ended up installing both Pi-Hole and Unbound/Unbound-exporter in the same nspawn container (debian-dns). You can see the changes here: pedropombeiro/udm-pro@ca4643f
Is your feature request related to a problem? Please describe.
I would like to be able to use unbound with my Pi-hole installation on the UDM Pro.
UDM Information
I've installed an nspawn-container using an isolated MacVLAN network (Followed this guide: https://github.com/unifi-utilities/unifios-utilities/tree/main/nspawn-container#step-2a-configure-the-container-to-use-an-isolated-macvlan-network)
and
Installed Pi-hole (followed this guide: https://github.com/unifi-utilities/unifios-utilities/blob/main/nspawn-container/examples/pihole/README.md)
Describe the solution you'd like
Here's a guide: https://github.com/unifi-utilities/unifios-utilities/tree/main/unbound
This describes how to install unbound in an older configuration or with podman. I would like for this to be updated so I can use unbound again.
Describe alternatives you've considered
The above solution creates 2 containers, which would be fine.
I've previously used https://github.com/chriscrowe/docker-pihole-unbound which has everything in one container.
I'm content with performing manual updates for both components and don't require an all-in-one solution. Being self-reliant in managing updates is important to me.
Additional context
I'm very happy with the way I have everything configured now. This would be the cream on the cake. :-)
The text was updated successfully, but these errors were encountered: