Container is not self-updating like I thought it should be

Plex Media Server
1

Server Version#: Version 1.31.1.6733

When I deployed my Plex server on Docker, I did so with the understanding that the image doesn’t need to be updated and that the PMS instance itself in the container would self-update. Is that still true? I’m seeing currently where PMS is stuck on the version listed above, and reports that an update is available but the logs in the container appear to show that it’s not doing anything to update itself:

[cont-init.d] 50-plex-update: executing…
[cont-init.d] 50-plex-update: exited 0.

The time between those two log events in Docker is nearly instantaneous. Can I invoke the update from within the container manually via a script or tool or something? Or do I need to go ahead and pull the image? If so, can I just continue to use my docker compose with the claim in it? I reeeeeeally don’t want to have to rebuild my Plex configuration like I have so many times in the years past from a sketchy update.

2

The upgrade behavior is determined by the image tag you use when creating the container. Specifically, if you use the ‘plexpass’ or ‘public’ tags, Plex Media Server will be automatically upgraded when the container is started/restarted. If you don’t specify a tag, or specify ‘latest’ the image doesn’t automatically update; you’ll need to pull the updated image manually.

You can find more information here (in the tags section):
https://hub.docker.com/r/plexinc/pms-docker

(All of the above pertains to the official Plex, Inc. docker image).

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.