docker
By linuxserver
docker-plex
By linuxserver
docker | docker-plex | |
---|---|---|
1 | 44 | |
- | 1,199 | |
- | 2.6% | |
- | 8.3 | |
- | 11 days ago | |
Dockerfile | ||
- | GNU General Public License v3.0 only |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker
Posts with mentions or reviews of docker.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-06-28.
-
Linuxserver.io
Btw They have a homeassistant image now https://github.com/linuxserver/docker homeassistant
docker-plex
Posts with mentions or reviews of docker-plex.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-12.
-
Use RAM for Plex transcoding
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.
-
Upgrade Plex in Docker not working
I found this, but don't see anything similar for ghcr.io in the images list in the docker UI.
- DSM 99% CPU. Lot of CrashUploader processes
-
Plex Docker hardware transcoding issue
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
-
Plexamp headless: passing the claim as an environment variable
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.
- Should I use Proxmox on my home server?
-
Using Intel eGPU QuickSync with Kubernetes for transcoding with Plex/Jellyfin etc...
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.
- Benefits of Different Plex Options on UnRaid?
-
Bad Plex Version?
These are their historical container versions - https://github.com/linuxserver/docker-plex/releases
-
Clarification on updating Plex via docker on Synology
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