docker-jackett VS node-red-docker

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

Feb 14 16:16:31 podhost podman\3483]: 2023-02-14 16:16:31.053466474 -0300 -03 m=+0.071815344 container health_status 2177a7448029695a17a9c0c774b8f48875bda76f6bf6e100254532765c6005d7 ()image=docker.io/nodered/node-red:3.0.2-18, name=nodered, health\status=unhealthy, org.label-schema.build-date=2022-08-04T13:19:34Z, org.label-schema.docker.dockerfile=.docker/Dockerfile.alpine, org.label-schema.vcs-type=Git, org.label-schema.license=Apache-2.0, org.label-schema.name=Node-RED, authors=Dave Conway-Jones, Nick O'Leary, James Thomas, Raymond Mouthaan, org.label-schema.vcs-url=https://github.com/node-red/node-red-docker, org.label-schema.version=3.0.2, org.label-schema.arch=, org.label-schema.description=Low-code programming for event-driven applications., org.label-schema.url=https://nodered.org, org.label-schema.vcs-ref=))

I found that Nick O'Leary (founder of Node-RED and the great guy that he is..) already did some research on this, I just had to bring this all together.

I don't use node-red, but I guess they use the node-red user in shell and overriding the process owner causes some issues with that. You can add an issue to their repository if you want.

Standard practice with Node-Red lets the user add dedicated flows and dependencies via the npm install command-line. However within the Node-Red-Docker Repo Wiki, you can also add these flows/dependencies via a dedicated package.json.

# https://nodered.org/docs/getting-started/docker # https://community.home-assistant.io/t/node-red-get-homeassistant-error/53923 node-red: container_name: node-red depends_on: homeassistant: condition: service_started environment: PGID: $PGID PUID: $PUID TZ: $TZ image: nodered/node-red networks: smarthome: ipv4_address: 172.18.0.2 restart: always # https://github.com/node-red/node-red-docker/wiki/Permissions-and-Persistence # chown volume after first run volumes: - $USERDIR2/node-red:/data

Node Red - Flow programming, mainly for IOT