Latest docker image lost access to an entire media directory

Plex Media Server Metadata & Adding Files
1

Server Version#: 1.42.1.10060-4e8b05daf

I’m sure others are reporting similar issues with the latest docker image but I thought I’d report the specifics that I found.

I have the following directory structures:
-HDD/Videos

-HDD/Music

In my docker compose file, I have them defined as:

  - /mnt/HDD/Videos:/media3
  - /mnt/HDD:/music3

In Plex, I have video libraries pointed to the relevant subfolders (i.e. /media3/Movies). The Music library is pointed to /music3/Music.

After the latest update, everything still works the same except Plex can no longer see the Music folder inside /music3/. Rolled back 1 version for now. Hopefully the specifics of how my directories are structured can help get this resolved.

3

Check the puid and guid you’ve set for the docker, matches what the files and directories have.

Edit: to be clear I loaded that version a couple days ago and saw no issues with loaded libraries

4

I don’t think this is the issue since the other Video folder still works. I think it has something to do with my strange directory structure and the decision to reference the same drive twice, or the fact that one reference is inside the other. Obviously I can’t be sure, I just know all the previous versions worked until now.

I’m sure one fix would be to change/simplify my directory structure but the bug would persist and I would have to re-scan my music folder and likely start from scratch there.

5

Its a good question, why are you mapping your videos directory into music?

my strange directory structure and the decision to reference the same drive twice, or the fact that one reference is inside the other

Yea see, this is where it stops being a docker and plex bug.

6

I’m not doing that. You’ve replied twice without reading or understanding the directory structure that caused this.

I have everything correctly defined, the only version of Plex that can’t see my Music folder is the latest. You don’t know the reason, so there’s no reason for you to reply to this. The only appropriate response to this post is a Plex developer saying that it’s fixed.

7

Your linked snippet shows “Videos” directory mapped into both media3 and mapped into music3? Correct?

9

What is there to understand? You made a mistake with your initial mappings and are now suffering consequences?

A sensible mapping would have just been /mnt/HDD:/media and then map the libraries within Plex from within there.

“My broken stuff used to work and should now always work” is never a worthwhile argument.

10

Adding this as a second comment since my first has already received feedback.

When you have a common root for all of your media, there is never a reason to break it out in containers (very, very special considerations, which you have not mentioned, notwithstanding). Prefer a common root (treat it like a mounted drive in bare metal).

Your recursive scheme is going cause problems at some point.

However, I acknowledge this particular problem might not be caused by this. I’m only suggesting you get your house in order. Best practices are considered best practices for a reason.

11

I appreciate the replies but to be clear: I’m not asking for help on this matter. The fact that Plex can’t see a properly mapped directory is a bug and Plex’s development team is either going to address it, or (more likely) let it persist going forward (I’m still waiting for them to fix casting to the Xbox One X after the iOS app “update”).

I understand the directories could be cleaner but Plex isn’t the only thing using my media (and might soon get dropped altogether), so I have to compromise sometimes.

12

A suggestion: Open an interactive terminal to your container. Navigate to /music3/. Perform an ls -lah and see what is returned. Then navigate to /mnt/media3 and do the same. These types of issues are almost always related to permissions.

Will you post your Compose file (or your Docker “run” command-line)?

I ask because I’m just not seeing this issue on any of my PMS containers.

14

@nickdelardi, check your docker compose file for PUID and PGID variables and replace them for PLEX_UID and PLEX_GID.

PLEX_UID=1000

PLEX_GID=1000

This will solve your problem.

I talk more about this issue on my post on reddit:

https://www.reddit.com/r/PleX/comments/1mnhsmy/comment/n8ib87o/

15

@felpzrj

Interesting. This isn’t really new though, you can find an example I shared of my compose last month that specifies puid/guid. This was always a best practice. I mentioned to OP to check their puid/guid in the first post in this thread. OP wanted help but still skewered me shrug weird how they do that.

16

I see now how the conversation went in the mappings direction…
I agree 100% with @pshanew about mapping the root of the media folder and then mapping the libraries from there within Plex.

At first I thought it was similar to the issue I faced. I had variables PUID and PGID pointing to my user on the compose file and after the latest update Plex was not running with my user anymore and it broke mapped folders access due to permissions. I had to change it to PLEX_UID and PLEX_GID to make Plex run with my user again, solving the problem.

17

@felpzrj Sorry for the late reply, I was working. There was actually nothing wrong with the mappings. Your reply/comment was the correct answer: that this latest update doesn’t play nicely with “PUID” or “PGID” anymore.

Furthermore, I don’t think this should be considered obvious until they update the recommended docker compose file on the website https://hub.docker.com/r/linuxserver/plex

18

That’s a third party version from linuxserver.io of the the pms container. These are the official container versions:

https://hub.docker.com/r/plexinc/pms-docker/

19

Third party app sources will screw you every-time.

Major security issue, hard to delve in and figure out what they may be wedging in.