Plex Docker not updating automatically

Plex Media Server
1

So, as of this morning, Plex will not automatically update. I am running in Docker Desktop 4.33.0 on Ubuntu 22.04.4. I’m new to Docker, and everyone said it was a hassle free way to run Plex, but I don’t see it. I don’t want to delete the container every time there’s an update, just to have to reinstall my server. I want it to update automatically, or with some input would be fine.

All the posts I’m finding say to just restart the container, but that doesn’t work. Any help?

Server Version#: Version 1.40.4.8679
Player Version#: Version 1.99.0.210-2d92b948

2

Look into Watchtower to keep your containers auto updated. That said, you still want to make sure you have your containers looking for the latest image, so make sure you use the correct tag on your container.

This is my compose file, it runs at 01:00 and deletes the old images when finihed.

version: "3"
services:
  watchtower:
    image: containrrr/watchtower
    container_name: watchtower 
    restart: always 
    environment: 
      WATCHTOWER_SCHEDULE: "0 0 1 * * *" 
      TZ: America/Los_Angeles 
      WATCHTOWER_CLEANUP: "true" 
      WATCHTOWER_DEBUG: "true"      
    volumes: 
      - /var/run/docker.sock:/var/run/docker.sock
3

Thanks for this, I’ll look into it. But as long as it looks like I have to publish a whole new install in order to get this running, why would I want to keep Docker in the first place? Why not just migrate to bare metal, as I probably should have in the first place?

4

If you mapped the directories and folders correctly, you stop the container, and do a “docker-compose up” and it will download and recreate the new container losing nothing. Watchtower does this all automatically for me.

I started with Plex in docker on a mini pc and took the same Plex, moved it to my nas, fixed the drive mappings, recreated the container and it operates fine, with no loss. If you have the ability to install bare metal and are more comfortable with that, go for it. That said I have been running two Plex Docker servers for almost a year with few problems that weren’t of my own doing.

5

What I’m getting at is that each time I start a new container, I have to set up the server all over again, as if I were a fresh install and that isn’t what I want.

6

It’s not setup correctly then. Can you post your install process? Compose file? Run command? Or are you going to switch to Bare metal?

7

I don’t know how to get either of those. I’m using Docker Desktop, I pulled the official image from the repository and hit run, added the variables and arguments, then set up Plex. Was I wrong?

8

Wrong, no, but I use yaml files and docker-compose with the command line because I find it easier. During the setup process it probably asked you to map VOLUMES for the config folder, that is where it stores all the database files so you don’t need to redo the server every time. Hopefully someone familiar with docker desktop will come along, or if you followed a set of instructions you wanted to link I can point to where you need to change things.

This is my docker-compose and under volumes you need to have constant folders for the docker container to write the settings too, (/home/user/plex) if you don’t map these, they will get deleted every time you start the container. I’m sure you can do this on Docker Desktop, but don’t know which step.

version: '2'
services:
  plex:
    container_name: plex
    image: plexinc/pms-docker:latest
    restart: unless-stopped
    environment:
      - TZ=America/Los_Angeles
      - PLEX_CLAIM=<claimToken>
    network_mode: host
    volumes:
      - /volume1/data:/data
      - /volume1/docker/plex:/config
      - /volume1/docker/plex:/transcode
      - /etc/localtime:/etc/localtime:ro
      - /etc/timezone:/etc/timezone:ro
    devices:
      - /dev/dri:/dev/dri
9

I don’t remember specifically specifying any config or transcode volumes, I guess I have to set it up the right way now unless anybody else speaks up and can tell me how to fix what I’ve already got.

10

The /config volume is absolutely essential if you want to retain your configuration in docker. The volumes you setup here are the pieces which live outside the container and all your preferences/data is stored in the /config location. /transcode is less important but generally you want to set it up so you can dictate where the transcode temp data is stored.

Docker is often suggested and often used by those who don’t understand it. It is convenient if you know what it is doing but it is also very easy to do something drastically wrong and get yourself into trouble. TBH I don’t see the argument about docker being easier than setting up the APT repository in Ubuntu when it comes to updates, especially if you aren’t running a bunch of containers already.

11

This is my boat in a nutshell.

Is there any way to back up my configuration and migrate it to a new install, one done properly?

12

Ok, so I’ve borked my install. I get it, that’s on me. But before I start from scratch, can anyone tell me if it’s possible to migrate what I already have?

13

I don’t know of a way to backup what you have without knowing the directory where the container is storing everything. Maybe try a system search for a folder named: “Plex Media Server” on your hard drive, that is what my docker container has all the settings. Make a copy of that and then you can try to fix your install. Contents structure should look like this.

Screenshot 2024-08-15 at 09.41.26
Screenshot 2024-08-15 at 09.41.26526×950 34.9 KB

14

This is the section it shows when I inspect the container:

			"Type": "volume",
			"Name": "4bbd3cfe3c72f9ec8337ca31c1079eda5343a6c166f32c14228f1524ca07fe67",
			"Source": "/var/lib/docker/volumes/4bbd3cfe3c72f9ec8337ca31c1079eda5343a6c166f32c14228f1524ca07fe67/_data",
			"Destination": "/config",
			"Driver": "local",
			"Mode": "",
			"RW": true,
			"Propagation": ""
		},
		{
			"Type": "volume",
			"Name": "0c3e2104803b9f6f48cb0cf71c4196c1bca855fd69950f613b8b90d50164ca50",
			"Source": "/var/lib/docker/volumes/0c3e2104803b9f6f48cb0cf71c4196c1bca855fd69950f613b8b90d50164ca50/_data",
			"Destination": "/transcode",
			"Driver": "local",
			"Mode": "",
			"RW": true,
			"Propagation": ""

The directory /var/lib/docker is restricted, I can’t access it. Maybe I can do it via CLI, I’ll check it out.

15

That means docker created a separate volume for the data stored in /config. There are instructions on how to deal with volumes here, but it may not be that helpful. Perhaps the part about how to backup a volume near the end may be helpful but it involves dealing with docker on the CLI in some less-than-typical means.

16

Alright, I figured out how to backup the entire Application Support directory. Now, I need to know: What out of this do I need to restore to a new installation? Will I have the same token?

In Docker Desktop there is an Exec tab in the container, from here I just # cp -R /config /Media/backup and it’s backing up now. I’ll take a look at it when it’s done. /Media is the mounted directory where I store my media (obviously), but right now it’s also going to hold a backup for a minute.

17

Were you going to try and move your install to ubuntu and skip docker? I think I’ve seen a thread on how to migrate here before. Or maybe @ChuckPa could tell you how to restore/keep everything.

18

I’m probably going to go with the direct install and skip Docker. I’ll look for the thread, see if I can find it.

19

I found the article, followed it and all is working. Good thing is, I found out how to access and copy directories from a running Docker container, so maybe that will help someone else.

Thanks for the help and @gbooker02 thank you also.

1 Like
20

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