I’m new to Unraid PMS (migrated from Windows/FlexRaid) so I’m asking this since I’m not sure…
Is this normal, this delay between the moment when new PMS version is available (Windows, etc…) and when the docker versions are updated?
From what I can see, there’s been no delays and the latest version is used.
Have you configured yours using the correct tags?
If there’s delays, those are usually mentioned in the release announcements (e.g. here, when PMS 1.15.0 is not immediately available on Nvidia Shields).
ok ok, after reading a bit, I realized when there is an update, the docker doesn’t need to be updated, just a docker restart and the update is applied… I was waiting for an update from the docker image itself… but never actually restarted it…
Still new to Unraid to dockers… In my mind, update = docker update… guess not…
What’s the difference between when the docker image is updated and a PMS update?
Last updates were applied when restarted the PMS but the actual Docker image never was updated…
Restarted and pulled the latest image. Still on 1.14.1.5488.
My recollection from last update is that you do need to pull the updated image and Plex has not yet updated the image. If you scroll down in the tags you can see the 1.15 release is not present.
Anyone know how we get the attention of Plex to push the updated image?
I was just able to update by changing the image tag from latest to public. Previously I had been experiencing the same thing, no update after restart, but I’m now on the most recent version. Hopefully this will work for you too.
I don’t understand the logic of it but the docker image doesn,t need to be updated, when there is a PMS update available, restart the unraid docker and it gets updated…
Once, it didn’t work and after seeing issue in the docker logs, I restarted it again and it updated…
Just updated to 1.15.3.835
latest has Plex preinstalled. It is on version 1.14.1.5488 right now and needs to be updated by the Plex team.
beta and public (and plexpass which is the old name for beta) don’t have Plex preinstalled. They install/update Plex on every start of the container.
I hope they update latest soon. I don’t want to use a container that updates itself (could break things), but I’d like to update to the new version now.
Note: If you don’t use the official image (plexinc/pms-docker) then of course your container might behave differently.
So, based on this info, the latest tag “should” be update every time there is a new stable release, right?
So the stable tag is now 6 days behind from what I can see…
Back to my original question, is this expected or this would be an exception and usually gets updated faster?
Because sounds like beta will always be up to date if it updates/reinstall on every restart no matter what the Docker image version is…
Am I making sense?
You’re slightly off. What you say is correct about the beta/plexpass.
I believe what you’re looking for is the public tag – which will automatically update to the latest available public release if you properly configure your container.
I currently use the ‘latest’ tag as well and am waiting for 1.15. If I switch to the ‘public’ tag what happens if my internet is down when I start the container? Will it fail to start or does it store the app in the config folder and use that instead? If it fails to start then I think I’ll stick with the ‘latest’ tag so that I can still use plex locally without internet.
I feel the same. I contemplated creating a separate Plex container using the “latest” tag with all the same mappings. That way I could spin up Plex if the internet was down. However, I’m just going to use one container with the public tag. Hopefully I don’t regret that
I had the same thought, but wasn’t sure what would happen if I fired up the ‘latest’ tag that could potentially be an older version than the ‘public’ tag. Probably wouldn’t be good considering there are likely some database changes between versions.
I really don’t want to switch to the ‘public’ tag, but it kind of seems like that’s the route they want us to take.
Part of moving to our new build system is moving a bunch of CI tasks. One of these was building the docker images. Now our new image building job will allow us to actually create test images so we can test different branches in the pms-docker repository. Previously we had to push them to everyone and hope it still works. This will enable us to make modifications/updates to the image and have widespread testing without affecting everyone else.
1.15.3.876-ad6e39743 was just manually pushed from our CI and subsequent versions should be automatically pushed.
