docker-prowlarr VS docker-qbittorrent

Gotcha. I was going by Linuxserver's documentation on it since i mainly use their images.

# https://github.com/linuxserver/docker-prowlarr prowlarr: image: lscr.io/linuxserver/prowlarr:develop container_name: prowlarr environment: - PUID=13004 - PGID=13000 - UMASK=002 - TZ=${TIMEZONE} volumes: - ${ROOT_DIR}/docker/prowlarr-config:/config ports: - 9696:9696 restart: unless-stopped ``` From my googling I thought it might be a permissions issue but after checking that doesn't seem to be the case.

Wireguard VPN and Prowlerr

Prowlarr

Prowlarr for index management

I have it running in a docker container. I use the LinuxServer image. The image is well documented and gives docker run and docker-compose examples. It is still in beta stage, can contain bugs.

Say I wanted to run this container on k3s. How do I specify PUID, PGID, WEBUI_PORT, and the volumes? This is literally the only thing keeping me from jumping headfirst into k3s. I have no intention of running anything docker in the near future and onwards, but I need to know how I can switch without using something like kompose (I don't want to trust a script with my deployment options, I want to do it by hand like I used to with Docker).

Here is a link to an issue I found on the linuxserver/docker-qbittorrent repo discussing the issue I'm currently having.

# https://github.com/linuxserver/docker-qbittorrent qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent network_mode: service:nordvpn environment: - PUID=13002 - PGID=13000 - TZ=${TIMEZONE} - UMASK=002 volumes: - ${ROOT_DIR}/docker/qbittorrent-config:/config - ${ROOT_DIR}/data/torrents:/data/torrents restart: unless-stopped depends_on: - vpn

In "docker ps" you'll see the EXPOSE Ports defined in the Dockerfile of your Image. They are only accessable in their own networks unless you just bridge your container to your host's network (not recommended).

My only issue is the the linuxserver/qbittorrent container doesn't always start up after a server reboot, I've just filed a github issue about this: https://github.com/linuxserver/docker-qbittorrent/issues/167

Check out the GitHub... Nine times out of ten the info is there: https://github.com/linuxserver/docker-qbittorrent

qBittorrent

Stuck on the Login page · Issue #109 · linuxserver/docker-qbittorrent (github.com)