PMS on ProxMox LXC Docker container unable to see content in remote NAS

Hi all.
For a long time I’ve been running Plex as an package in Synology NAS.
We also have docker on there running multiple containers, but as that’s expanding I’m looking to migrate some if not all over to a Proxmox machine running a dedicated LXC (container) for all docker tasks. This should take some of the load off the NAS as well as be a handy backup if the NAS was to die and be replaced with an alternate NAS solution.

There were issues mapping to the NAS over the network and I worked through them all, but for some reason PMS isn’t showing a list of my content on the NAS and I don’t know why.

Proxmox: 8.1.4
LXC : Ubuntu 23.0.4 Standard (up to date) unprivileged
Plex: latest (1.32.8.7639)


To get the NAS share into the container I had to first map it to the proxmox host and then pass that through to the docker LCX container. This guide showed me how to do that:

With the mapping in place I created a local user with the same credentials and added them to the lxc_shares group

From the Proxmox host I can cd to the /mnt/Plex folder and create, rename and delete files and folders no problem. From the LXC container the same. cd to the /mnt/Plex folder and create, rename and delete files and folders, so everything is mapped and passing through properly.

Tested with metube and confirmed that I could create volumes to the mounted path in the container and see all contents no problem.

With Plex I set the same -e PUID/GUID as radarr and while I see the /Plex volume when trying to add the library, I don’t see the contents from the GUI.

If I connect into the plex container (docker exec -it plex bash) then I can browse to the /Plex folder and see everything. Same add, rename and delete as host+lxc, but for some reason I can’t see anything within Plex itself.

I tried multiple mappings in case it was sensitive to that as well as PUID/GUID:0 (root) but all results were the same. I also added --privileged to the plex container, but still no contents.

I can’t think why it can’t see the same content as the terminal unless the app runs as an alternate user within the container. Inside the container I see a plex user in the /etc/passwd file, so in case there were inconsistencies I created a 10000 lxc-shares group and added plex user to it (as well as to root and sudo groups).
Still no contents.

I’m out of ideas at this point


docker run -d \
--name plex \
--cpuset-cpus="0-3" \
--network=host \
-p 32400:32400/tcp \
-p 3005:3005/tcp \
-p 8324:8324/tcp \
-p 32469:32469/tcp \
-p 1900:1900/udp \
-p 32410:32410/udp \
-p 32412:32412/udp \
-p 32413:32413/udp \
-p 32414:32414/udp \
-e PUID=1000 \
-e PGID=10000 \
-e TZ="Europe/London" \
-e ADVERTISE_IP="http://192.168.1.99:32400" \
-h CSWPLEX3 \
-v /opt/docker/plex:/config \
-v /mnt/Plex:/Plex \
-v /tmp/:/tmp \
plexinc/pms-docker:latest

image

Example docker metube that has no problem writing to the same LXC share proving it works

docker run -d \
--name=metube \
--net mylocalproxy\
--ip 172.21.0.05 \
-p 8081:8081 \
-e PUID=1026 \
-e PGID=10000 \
-e TZ=Europe/London \
-v /mnt/Plex/Media/YouTube:/downloads \
--restart=unless-stopped \
alexta69/metube:latest

metube

Just follow this guide, you do the SMB mounts via systemd:

1 Like

Ta
I’d backed up/restored my docker LXC so it would be privileged before, but it had weird issues after that. Services wouldn’t start like ssh and docker, so I gave up on that as an option and restored it back as unprivileged and it was back to normal.

It didn’t like changing state, but I followed the steps using the link you provided to create it privileged from the start and I had no problems with the LXC container.

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