Update docker server install that was initiated without update tag

[mtrpires]

Server Version#: Version 1.16.1.1291
Player Version#: n/a

Hi everyone, I’ve spent the last couple of days searching for this topic and couldn’t find anything specific to my case. Apologies if there’s another topic that addresses this, I really wasn’t able to find it.

I’ve installed the Plex Media Server using Docker (plexinc/pms-docker), as per instructions here. I’ve followed instructions for host networking. I use Docker in a Debian 9.0 remote server.

Now, a few weeks later, I’ve been getting a notification that there’s an update for my plex server, and I wanted to proceed with the update. I’ve found through other topics in the forum that the update process should happen automatically when you restart the container. However, if I understand correctly, that should happen PROVIDED you added the appropriate tag (public, latest, beta, etc) when you run the container for the first time, as explained here.

Nevertheless, the install instructions to run the container for the first time come before the section about the tags, and unfortunately they don’t include any tag, which means I installed my container without it.

Now, expectedly, even as I restart the container, it does not get updated automatically, since I don’t have the appropriate tag. I’ve been searching for instructions around how to update the plex server in this case but couldn’t find anything solid. Is there a way to add this tag to the configuration of the container without restarting the whole process? What would be the best fix for this?I decided to reach out to the forum in order to get a few tips and directions lest I may break the current install

Thanks in advance!

[Krazeh]

What command did you use to originally start up the docker container?

[mtrpires]

this:

docker run \
-d \
--name plex \
--network=host \
-e TZ="<timezone>" \
-e PLEX_CLAIM="<claimToken>" \
-v <path/to/plex/database>:/config \
-v <path/to/transcode/temp>:/transcode \
-v <path/to/media>:/data \
plexinc/pms-docker

[Krazeh]

As long as you use the same paths as previously it should be fine to just stop the existing container then use the same command but with the addition of a tag on the last line e.g. “plexinc/pms-docker:latest”.

You shouldn’t need the plex claim token, but I can’t imagine it’d hurt to leave it in.

[mtrpires]

thank you! I’m gonna try that

edit: worked after I added plexinc/pms-docker:public and readded the container. Thanks!