unbound failing to work about wirehole

[jhedd]

I noticed something similar. Unfortunately, the unbound used (wireguard and pihole are fine) only supports AMD64.
Try an alternate distribution (eg. klutchell/unbound) and see if you can get it to work?

[IAmStoxe]

According to unbound simply pulling klutchell/unbound should retrieve the correct image for your arch.

Run this

# build a local image
docker build . -t klutchell/unbound

# cross-build for another platform (eg. arm64)
export DOCKER_CLI_EXPERIMENTAL=enabled
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
docker buildx create --use --driver docker-container
docker buildx build . --platform linux/arm64 --load -t klutchell/unbound

Then try again?

This is taken from https://hub.docker.com/r/klutchell/unbound

[jhedd]

Unlike Rovoska, I'm on Debian Buster (Armbian) not Raspbian, so not if my testing would apply to him.

Anyways, tried pulling klutchell/unbound but it ran into the following:

Creating network "wirehole_private_network" with the default driver
Creating unbound ... done
Creating pihole ... done
Creating wireguard ... done
Attaching to unbound, pihole, wireguard
unbound | [1601347858] unbound[1:0] error: can't bind socket: Permission denied for 0.0.0.0 port 53
unbound | [1601347858] unbound[1:0] fatal error: could not open ports

looks like it's running into the systemd's dns stub resolver, but given it's on a private network, it shouldn't be?

[IAmStoxe]

It still binds to the host port. Remove the ports designation for Unbound that way it doesn't bind to host ports.

…

On Mon, Sep 28, 2020, 8:02 PM jhedd ***@***.***> wrote: Unlike Rovoska, I'm on Debian Buster (Armbian) not Raspbian, so not if my testing would apply to him. Anyways, tried pulling klutchell/unbound but it ran into the following: Creating network "wirehole_private_network" with the default driver Creating unbound ... done Creating pihole ... done Creating wireguard ... done Attaching to unbound, pihole, wireguard unbound | [1601347858] unbound[1:0] error: can't bind socket: Permission denied for 0.0.0.0 port 53 unbound | [1601347858] unbound[1:0] fatal error: could not open ports looks like it's running into the systemd's dns stub resolver, but given it's on a private network, it shouldn't be? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5UPI6IZHFLTUC2KE6DMDTSIFE3RANCNFSM4R2V6DKA> .

[IAmStoxe]

Closing due to inactivity

[jhedd]

Sorry, didn't have a chance to get back to this.

Alternate version of unbound should work, but change the docker-compose to account for:
"Please note that chroot and username configuration fields are not supported as the service is already running as nobody:nogroup."

Thanks for the support IAmStoxe, but I ended up just using your existing x86 version.