I’m a plexpass owner, have been for some time. I use Plex via the official docker image. The problem I have is that although plex notifies me of new updates, the image only gets updated every 30 days or so, so sometime I have to wait 2-3 weeks to get an update. Yes I can apply the update inside the existing container, but I deploy in kubernetes so changing a version number automatically gets the new image and is easier to maintain than logging in and pulling a .deb.
Thanks!
What image are you using? I’m using “plexinc/pms-docker:plexpass” in my Kubernetes cluster and it downloads the latest version of Plex every time the pod is recreated. The “plexinc/pms-docker:plexpass” image doesn’t have Plex installed at all, there’s a script that runs at start up that downloads the latest .deb and installs it before starting up the Plex server. So to update to the latest version of Plex you just delete the old pod and when Kubernetes creates a new pod you’ll get the latest version available.
Note that this can backfire sometimes. If there are problems downloading the .deb when the pod starts up the script doesn’t retry very hard (if at all) and the container will be stuck in an infinite loop trying to execute the server that doesn’t exist.
I’m using https://hub.docker.com/r/plexinc/pms-docker, but I have always used the build numbers in my deployments, so current tag is “1.13.9.5456-ecd600442”. I’ll have to try plexpass tag and see if it pulls 1.14.0.5468. This would explain why the “plexpass” tagged image is only 66MB, but the 1.13.9 tag is 172MB.
Thanks
Edit: kubectl edit deployment pms and changing 1.13.9… to “plexpass” and it successfully pulled down 1.14.0. Now I just need to add meta such as a date value or something so I can increment to get the pod to redeploy in the future since the build number won’t change
Thanks @jcollie
I just manually delete the old pod “kubectl -n plex delete pod plex-XXXXXX-YYYY” and Kubernetes deploys a new one for me. It’s a bit “how ya doin” but it’s quick and easy. Having command-completion set up for kubectl definitely makes it easier. Using the plexpass Docker tag is the only way to get the Plex Pass-only versions AFAIK, which is why there isn’t a tagged image with the 1.14.x versions yet.
makes sense. I for some reason thought the plexpass was tied to my login/credentials, not the image…I’m working on setting up CI/CD with gitlab, where I can have it re-kick pods when they need to be updated…I’ll figure something out but your way works too 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
