Linuxserver/plex:latest stuck on Version 1.14.1.5488

Hello,

My docker container doesn’t update the plex server (linuxserver/plex:latest) any longer on restart.
It’s still running on Version 1.14.1.5488. Not sure where to start to debug this.

The docker log shows this as the first thing it did on startup:
[cont-init.d] 50-plex-update: exited 0.

My PLEX_INSTALL var is set as default:
PLEX_INSTALL=https://plex.tv/downloads/latest/1?channel=8&build=linux-ubuntu-x86_64&distro=ubuntu

Docker is running on a Synology NAS.

Where should I be looking to find out what’s wrong?

Thanks,
Alexandre

You need to delete and recreate the container according to the directions on the hub page.

Via Docker Run/Create

  • Update the image: docker pull linuxserver/plex
  • Stop the running container: docker stop plex
  • Delete the container: docker rm plex
  • Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
  • Start the new container: docker start plex
  • You can also remove the old dangling images: docker image prune

Via Docker Compose

  • Update all images: docker-compose pull
    • or update a single image: docker-compose pull plex
  • Let compose update all containers as necessary: docker-compose up -d
    • or update a single container: docker-compose up -d plex
  • You can also remove the old dangling images: docker image prune

Thank you.

I was hopping I wouldn’t have to remove and recreate the container. It’s a pain to re-add all the libraries, get the media re-analyzed, do the manual corrections, …

I will need to save some time to do it, cause I know it will take a while.

After I wrote that I saw you were on Synology and I wasn’t sure if the Plex meta data was stored with the container. Most other systems don’t do it this way.

Actually, you can extract it outside of the container and override the PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR variable to point to a mounted directory. It worked for me.

My container is still not upgrading to the new version. I’m stuck on the one version I upgraded to last time.
I used to just have to restart the container to get the upgrade (linuxserver/plex:latest). Not sure why that’s not the case anymore.

I am sure I could redo what I did last time (i.e. delete the container and recreate the container), but it’s heavy.

@RadYoHeaD did you ever get this sorted out?

Seems I’m having the same issue with my linuxserver docker image. Stuck on 1.14.1.5488. Version is on public and I’m a plex pass subscriber. It used to update on restart, now it’s stuck on this version.

Not really. I just made it easy to download the new version and re-deploy the image without losing any of the Plex user files. But I still have to do it manually.

How did you do it exactly? I’ve tried and keep getting 1.14. I downloaded both the “latest” image and the “1.18.xxx” image. Stopped the 1.14 container. Setup the new container using the same volume and environment variable information. But when I start the new container, it still shows as 1.14. Kind of stumped. Unless I have to not use the /Docker/Plex directory from the old version. If that’s so, what do I need to backup and restore once the new container is setup fresh?

Any help appreciated.

I’m not home right now, just working from memory. But I think I have to go in the docker registry and download the container completely again. Just recreating a new image won’t do it.

And all of my Plex user files are stored on a separate filesystem, so I just have to redefine the environment variable to point to it.

Not sure what you mean by a different file system. Is the plex folder (under docker volume) mapped to /config on a volume on your NAS?

Edit for clarity.

Yes. That’s the one. I just meant that all the config files are outside the container so I don’t lose any data after I recreate a new container.

Ok. So I’m doing what you did, I think. Ugh. Thanks, anyway.

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