![]() ![]() You may notice I am using $(PUID),$(PGID) and $(USERDIR). The only things that might seem different to other compose files is the number of ports that you need to define for Plex to work properly, as well as the “PLEX_CLAIM” entry. If you’re familiar with Portainer, most of this would seem pretty self explanatory. The image I’ll be using is plexinc/pms-docker. This server will be direct access play only, so I don’t have any concerns about needing to transcode. I can use both in Proxmox, so see no issue here before you flame me in the comments :)).įor those interested, I’m currently running all of this on my beelink GK mini, which continues to perform like a champion. (I know there are LXC’s out there already, but I’m a fan of docker, and prefer to work with it. In this article I’ll take you through a quick docker compose set up of Plex, including getting the appropriate token and how to configure it using Portainer, sitting on Proxmox. Personally, I find them easier to manage. I am a fan of docker compose and using stacks on Portainer. ![]() Whilst searching through various Plex articles I found that whilst there was plenty of documentation about how to get it up and running, there were very few methods using compose. So continuing with my Proxmox / docker journey, I decided it was time to fire up Plex and get some kind of media server up and running. ![]()
0 Comments
Leave a Reply. |