docker-autocompose VS docker-plex

But there is this little tool docker-autocompose that can read the configuration of your current containers and export that into a docker-compose.yml. It probably wont work 100% perfect for every possible container config, but its worth a try and it might save a lot of time when making the switch from run to compose. Good luck!

You can try to use docker-autocompose to read the configs of your currently deployed containers and write them into a compose file for you.

There are different registries, Docker Hub, Quay (quay.io), GitHub (ghcr.io), Linuxserver (lscr.io). Then there is the image name and then the tag (//:; for example lscr.io/linuxserver/plex:latest). The tag and the registry won't matter too much for you (tag I guess you use latest), because most maintainers like Linuxserver push the same image to different registries. So it doesn't really matter if you use lscr.io/linuxserver/plex:latest or just linuxserver/plex:latest or ghcr.io/linuxserver/plex:latest. What does matter is if you use the linxserver or the plexinc image. If you run docker container ls in your terminal, you can see which image you are using. You could then run docker container inspect to get a json config of your plex container and volume mounts etc. to use that to create a docker compose file for it. There are also tools that do that automatically for you, like this: https://github.com/Red5d/docker-autocompose/blob/master/README.md This way, you can use docker compose to start/stop/update and have a permanent config which you can easily migrate to a new NAS/server.

Run this https://github.com/Red5d/docker-autocompose

Here is the link to docker-autocompose for those that might be able to help. https://github.com/Red5d/docker-autocompose

I converted existing docker run via https://www.composerize.com/ (since I had them written down in text file) , you can also use https://github.com/Red5d/docker-autocompose (examples on very bottom) to convert existing containers to YML file.

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