Plex Docker Container with NFS Mounts
HTML-код
- Опубликовано: 20 сен 2024
- Containerize Plex with NFS mounts for media library! Let me show you how to mount NFS shares directly inside your docker-compose.yml file!
Support me on Patreon! / omgthecloud
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!
Looking for the example code? It’s on my website! www.omgtheclou...
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!
Thanks! And thanks a TON for turning me on to OilveTin, first time I’d heard of it! I’ll give you a shout-out if I end up using that in a video! Cheers friend
@@OMGTheCloud No worries! It's a great app isn't it. So simple yet so powerful. I love being able to give my partner buttons to restart certain containers xD. Less work for me.
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.
Awesome man!
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.
I'm going to try it. I want all of my files on NFS because I don't want my Docker VM to be that large.
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?
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.
I've seen this in isolated cases, but not for several years now. My recollection in those cases, was there was underlying kernel drivers not starting up head of the Docker service itself. Have you seen this recently (I realize my response is more than a little bit late to the game here!!!!) if so, could you share the OS version, Docker version, and describe your hardware?
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: "- $DOCKERDIR/appdata/plex:/config"? Also, what about the transcoding section: "- /dev/shm:/data/transcode". Is this ok left in its regular format in the Services section?
Sure can! Volumes can mix and match, and are independent of each other. For example you can have your Plex config as a named-volume mount, while passing your media directories as NFS mounts. Stay tuned, I have an updated version of this deployment coming soon, as Plex has changed a bit, and I've learned some new tricks along the way myself :)
@@OMGTheCloud I am very much looking forward to your updated guide. I am kind of stuck trying to get this to work with my configuration. I use a different branded NAS (ASUSTOR) and am struggling with permission issues. The permission/options I am using on the VM to successfully mount NFS (on proxmox) are not working inside the container. I assume you can simultaneously mount NFS on the VM and inside the container? (Let's leave the LXC discussion for another time!). It may also have something to do with your naming. I follow the recommended naming schema of TRaSH guides to accommodate direct copy as described there. Your naming schema differs from this.
Actually, I figured it out tonight. Got everything working. Let's see if my Plex server stays stable now, for long periods.
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.
Same bro losing my mind, essentially running docker on ubuntu server. Tried mounting on server and portainer, just going around in circles, but guess I'll be trying this method now.
Can easily mount on Linux, but not able to get docker/portainer to communicate with it
How reliable is it and how fast is the data access?
Hey there, thanks for watching! No issues with reliability, and if the service were to ever crash, Dockers' health check would catch it and restart it right away. Data access, I presume you mean performance of the Plex server, transcoding, and the like: That would be equal to the underlying hardware performance. Unlike virtualization, there is no paravirtualization to be concerned with; it's essentially process isolation, not virtualization. Check it out, let me know how it goes!