Allow to bind to other ports

[Quintasan]

I have seen and read #30, but it has one big assumption - using Docker.

According to Podman docs:

By definition, all containers in a Podman pod share the same network namespace. This fact means that they will have the same IP address, MAC addresses, and port mappings. You can conveniently communicate between containers in a pod by using localhost.

This means, that if I put Pi-hole and Unbound in the same Podman network, they will fight over port 53 (and it's the problem I'm running into now).

This means that the only way to make this work would be to put them in separate networks, expose their ports and have them communicate over the host instead of talking each other in the same network.

@MatthewVance do you think Podman support is a good enough reason to customize the port?

[Jason-Keller]

running into this issue as well -- have a pihole running in portainer alongside unbound and they are fighting over port 53

[mjurksa]

Just edit the unbound.conf in /opt/unbound/etc/unbound