YAMS Forum

Hey @rogs !

Thanks for your patience, I had to rerun the rm command because it took very long the first time. The second time as well but I just let it process for an hour or longer. Anyways it got rid of it and created Plex from scratch as you predicted when I executed yams start. Unfortunately nothing has changed.

I'm trying to learn more about docker in general so that I can become more self-reliant. Do you see any issues with keeping yams on my server? You said it was a docker compose wrapper but I'm not sure what that means. I'm just curious if certain typical docker commands will not work because of yams or stuff like that. In that case, I'm thinking yams might get in the way of my docker learnings/experimenting.

I really want to get this to work and I suspect if I completely delete yams and reinstall, Plex will be updated but that'll probably be a manually triggered update and it won't update automatically.

Okay short update and change of plans (you may ignore the previous message)

After troubleshooting a version mismatch issue with my Plex container, I’ve confirmed that the original container is likely corrupted or stuck with stale metadata.

We verified:

• The container logs report the correct updated version (1.41.7).

• But the Web UI and API still show 1.40.0.

• We tested by spinning up a second clean container with the same image, and that one displayed the correct version immediately.

We’d now like to replace the old Plex container from YAMS with this new, working one — but we want to make sure we don’t lose:

• Libraries

• Watch history

• Users

• Metadata

The current /opt/yams/config/plex folder contains everything, and was reused in the working test container, so nothing is lost yet.

How should we best transition YAMS to use this fixed container setup? Ideally, I’d like YAMS to start the working container moving forward, but preserve all my Plex data and keep other containers (Sonarr, Radarr, qBittorrent, etc.) connected smoothly.

For the record, I've created the second container outside of YAMS so just using docker

docker run --rm -it -p 32411:32400 -v /tmp/plextest:/config lscr.io/linuxserver/plex

What I mean by "YAMS is just a wrapper around Docker and Docker Compose" is that whenever you run yams something, you're just interacting with Docker or Docker Compose under the hood. You can check the code for the yams script here: https://gitlab.com/rogs/yams/-/blob/master/yams

If you're interested in learning more about Docker, you can ditch the yams script entirely and use Docker Compose directly, it’ll work just the same.

If you want to use your "fixed" Docker container within YAMS, you’ll need to follow this guide: https://yams.media/advanced/add-your-own-containers/. Make sure to point your volumes to the same paths, and then remove the old container.

Just a heads-up: you probably don’t need to do this. I’m pretty sure you’re just missing a few steps with your current container and it’s not being updated properly. If you still want to go this route, that’s totally fine, just keep in mind that you might run into the same issue again if the root cause isn't addressed.

Cheers!

Roger.

I've gone through seemingly everything and it seems to be that my container is corrupted. I really couldn't find what's wrong so that's why I'm trying this now. The only thing that matters to me is that I can update my Plex Server without losing metadata.

So I've updated my custom yaml

I've added the ports since I couldn't find where to find the new one. I didnt want to delete the old one before seeing the other works.

How can I see where the new container lives?

Also, how can I safely remove the old container without losing said metadata? Do I do 'docker rm plex', remove the plex entry from the main compose yaml and then do a yams restart?

To verify that everything is working, you have to stop the old one and start the new one, since you are using the same ports. Once you confirm the new one works while the old one is stopped, then it's safe to remove the old one. Use docker rm <your-container-id> to remove it.

Cheers!

Roger.

Very interesting, so I stopped the old container and kept the new one on. However it seems I can still access Plex and my libraries even though the container is not running anymore.

Something else I noticed, the new container is definitely running but I can't find my directories there when I try to create the libraries. It was installed on a different directory so I created a third Plex container in the same yams directory /opt/yams/config/plexnew. That instance also wasn't able to find the directories under /srv/media. I assume I'm skipping a step here?

Did you mount the volumes correctly? It sounds like they are different