docker-plex VS docker-qbittorrent

I've tried with couple of repositories but I'm mainly using this one now: lscr.io/linuxserver/plex I gave up on this sometime ago but would now like to get at least RAM transcode working for Plex. The GPU transcode can wait.

I found this, but don't see anything similar for ghcr.io in the images list in the docker UI.

I'm facing a similar issue. I reported it to the linuxserver team (publisher of that docker image), they think it's a plex issue. https://github.com/linuxserver/docker-plex/issues/357

I've messed with Plex in docker quite a lot though, so if you put your code in GitHub I should be able to point out an option for getting it done. Might not make sense for Plexamp for some reason, I've usually started with this repo https://github.com/linuxserver/docker-plex and forked when I was making my own Plex containers. I was thinking of doing that for Plexamp, but I've not looked at what's needed to map sound devices properly. It has an example of where to run a Plex claim script before starting up Plex to run as a service.

FWIW it's probably not a great idea to use the Plex or Jellyfin (or any really) images from lsio. They do stupid shit like this which is not needed with Kubernetes. You can add a security context with those GIDs as supplemental groups. Also all their containers start as root which is not considered best practice.

These are their historical container versions - https://github.com/linuxserver/docker-plex/releases

The linuxserver plex image can actually check for updates when the container starts. It's a bit of an anti-pattern. Here's the script: https://github.com/linuxserver/docker-plex/blob/master/root/etc/s6-overlay/s6-rc.d/init-plex-update/run

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)