Remotely VS docker-pihole-unbound

Following the comments in this thread, I should see an input for Server URL when building the client application with GitHub actions, however it's not there. Yes I forked the official GitHub repo.

Are you sure? It seems to be thriving under new management.

Site to site VPN if you have access to your locations' firewalls, otherwise some raspberry pis and https://github.com/immense/Remotely or any RMM.

I have another suggestion, have a look at Remotely. I only just looked into this and spun up a container to play around with. It's very similar to TeamViewer in that:

The closets open source alternative to Tactical RMM, I would say it's Immense Networks Remotely. It offers unattended remote access, as well as quicksupport feature like Teamviewer. It also has limited support for running scripts on one or many hosts which in effect allows doing some functions like that of Tactical RMM, however it doesn't give your same detailed device inventory as Tactical RMM, it doesn't monitor performance and you can't setup alarms as you can in TRMM. https://github.com/immense/Remotely

if you feel comfortable self hosting: https://github.com/immense/Remotely

Edit: For anyone who wants to follow: https://github.com/immense/Remotely/issues/553

I'm running the chriscrowe 'one container' build for pihole for ad-blocking (https://github.com/chriscrowe/docker-pihole-unbound), and unbound for private recursive DNS which is running great on my Zima board.

I believe my problem stems from when I tried to install the pihole-unbound container (https://github.com/chriscrowe/docker-pihole-unbound)

I've got lucky enough that I could get in Nov-19 a Raspberry Pi 4 with 4GB of RAM that I use as a NAS+Pi-Hole + Unbound +Other stuff (running Void MUSL of course) and instead of an SD I use an HDD for the OS + a 5TB HDD for the data and even fully loaded all cores it barely consumes more than 22W.

I was only able to get pihole macvlan approach working with an ssh access + docker-compose approach. I used the crowe one-container approach Still had to enable Open vSwitch for the network in Synology first.

You can follow the doc to do those install steps within your own Dockerfile. Or you can use the commonly recommended chriscrowe image, which does what I’m describing.

When I started experimenting with this topic chriscrowe's was a baseline for stuff that I tryed out, so kudos to chris!

It seems you’re looking at a wrong file. Here is a docker file for one-container solution: https://github.com/chriscrowe/docker-pihole-unbound/blob/55c88afaf8d76958923adc38f4c12a80e1cb9084/one-container/pihole-unbound/Dockerfile

2) you can use something like this maintained GitHub repo. Just decide if you want to use 1 or 2 containers and modify the ip and gateways, etc accordingly.