Plex Docker Container with NFS Mounts

preview_player
Показать описание

I put a lot of time in to these videos, and your support is appreciated to ensure I keep making high-quality content that’s helpful and educational to you!

This will get you out of the bad habit of mounting NFS mounts on the underlying host. Let your container define those mounts directly! PMS with NFS mounts is a good example to work with, since you need to mount your media library to it. This also covers read-only NFS mounts in containers!
Рекомендации по теме
Комментарии
Автор

This is great, thanks! I much prefer this way to mounting on the host. Hopefully restart: on-failure will catch any issues and plex will stay up eternally. If it doesn't though, I have a one press button in olivetin to run docker restart plex, which thanks to this method will also remount the shares. Glorious!

TombOfNazerick
Автор

This is exactly what I need. I have existing media on Truenas Scale Bluefin but I prefer to run apps on my ubuntu server with docker. I have run into a problem in running it with either docker compose or as a Portainer stack. My mapped smb shares are created but the run stops with the error: failed to deploy a stack: Network plex_default Creating Network plex_default Created Volume "tv-shows" Creating Volume "tv-shows" Created external volume "plex_plex-data" not found. Not sure where to go next. Advice would be appreciated.

jmikelong
Автор

Is anyone using NFS share for the Plex config? My media is accessed fine, but when I move my config from the local host disk to the NFS share it's unusable. Not sure if I'm just doing something wrong. I was trying to use a dataset on an SSD to maybe allow a better experience but resulted in the opposite.

ejkeebler
Автор

Thank you for putting this together. Can you mix and match regular format for storage in the Services section with the Volume section? You jump right in to the Media folders section without discussion the first three lines in the Volumes section. Are they all required? What if I wanted to keep my existing /config mount in my services section, like this: "- Also, what about the transcoding section: "- /dev/shm:/data/transcode". Is this ok left in its regular format in the Services section?

burnbrighter
Автор

Do you have any issues with your containers not starting after a hardware reboot? I have 6 (out of 16) containers with a Docker-based NFS mount just like yours and all 6 fail after a reboot. They sit there and keep retrying because of the restart=always setting, but never actually start. If I simply hop into Portainer and click "Start" on them, they all start immediately and work flawlessly until the next reboot. Driving me crazy! I really prefer the tidiness of this method over fstab, so I'd like to stick with it, but I've searched the internet up and down and nothing I've found has solved this.

jas
Автор

So I have plex up and the NFS share is available to add libraries. But when I scan, it shows Plex scanning each Movie (.., TV show, Song) then doesn't add any media. I know the share is good on the server side because I have another instance of Ubuntu running plex (not in docker) with not issues. This seems like a permission problem but I'm pulling my hair out. Also I'm only able to run NSF v3 on the server(NAS), is there a way to force v3 on the container or does it matter?

bobm
Автор

I seem to be having a lot of issues with trying to mount a share from my Synology NAS. Always ending up with not being able to mount due to permissions. I've created NFS permissions for map root user to admin, just so lost. Been working on this for two days now hah.

doctorpine
Автор

How reliable is it and how fast is the data access?

whilechannel