docker-synclounge VS docker-pihole-unbound

# https://github.com/linuxserver/docker-synclounge synclounge: container_name: synclounge environment: # AUTH_LIST: plexuser1,plexuser2,email1,machineid1 AUTOJOIN_ENABLED: "true" AUTOJOIN_ROOM: $AUTOJOIN_ROOM # AUTOJOIN_PASSWORD: password EXTERNAL_URL: $EXTERNAL_URL PGID: $PGID # PUID: $PUID App is stateless TZ: $TZ image: ghcr.io/linuxserver/synclounge networks: smarthome: ipv4_address: 172.18.0.8 restart: always

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.