docker-plex VS pms-docker

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

From what I can tell Plex can't see /dev/dri at all, as I get 45-plex-hw-transcode-and-connected-tuner: exited 0. in the logs which according to the source code means it did not see an existing device. Going into the container shows there isn't a /dev/dri folder at all though it does exist on my local machine.

I originally started using Docker because I wanted to run WireGuard alongside Pi-Hole and knew I would be wanting to add other containers and Docker's a good way to make everything play nicely. I originally wanted to install WireGuard immediately alongside Pi-Hole but that got shelved. The Plex Docker container can't be installed on Pi OS, there is an Plex docker container tough which is also causing me problems. IE: every time I update PMS (which is apparently a lot) it recreates the container, in addition to a lot of install errors.

I have a Raspberry Pi 4 8 GB Extreme running 64-bit Pi OS with Docker and Portainer. I'm trying to deploy the following image: https://github.com/plexinc/pms-docker. I'm creating a stack and then using a docker-compose file.

From what I can tell, there's even an official repository, and github repository.

Found it. The Docker container has a health check script. This script runs every 5 seconds. You can see this in the Plex console. Filter on "/identity".

The issue seems to be more that the container I'm trying to run is trying to chown a directory and runs into "Operation not permitted" issues. Specifically, this script is being executed and is failing, no matter which combination of user/namespace commands I am feeding it.

This looks like the official docker. Look through that and make sure you are using the correct docker.

So I'm run Plex server on my OMV server in docker container (this)[https://github.com/plexinc/pms-docker]. And my quality settings in win app looks like this (Show all do nothing)

The closest I can think of is the docker. If OP likes docker in their docker then they can start with RancherOS.