docker-jackett VS docker-pihole-unbound

I can't get this container to launch, in the logs the access error in repeatedly printed:

Where did you get the docker-compose.yml from? Post the link. Also, why are you not using the one from the linuxserver if you are using their container? https://github.com/linuxserver/docker-jackett

So I'm running docker with portainer and I'm having issues getting the port number right. I set up my VPN in a container then I set up jackett and qBitTorrent. I want jackett and qBitTorrent to run through my VPN but I'm having issues with the port numbers jackett needs port 9117 and qBitTorrent needs 8080 how do I set my VPN up so they both go through it?

# https://github.com/linuxserver/docker-jackett jackett: container_name: jackett environment: PGID: $PLEX_PGID PUID: $PLEX_PUID TZ: $TZ image: lscr.io/linuxserver/jackett networks: smarthome: ipv4_address: 172.18.0.16 restart: always volumes: - $USERDIR2/jackett:/config

I always sort of assumed it was related to my set up, but it looks like some folks have had a similar problem with Jackett docker images on their own here. Gonna try the suggested alternative image and see if that helps.

https://github.com/linuxserver/docker-jackett/issues/72#issuecomment-468859532

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.