I'm trying to set up Nextcloud and Jellyfin in separate containers so that I can access all my movies and TV shows in Jellyfin from Nextcloud. To do this, I created a main folder called "nextcloud" and put a sub-folder called "jellyfin" inside it. But I'm wondering if having both containers access the same data (like an .mp4 file, for instance) at the same time could lead to issues. Is this setup okay, or should I reconsider the folder structure?
4 Answers
It's actually safe to bind the same directory to multiple containers without causing issues. But I'd suggest avoiding nested directories mainly for easier management.
Honestly, it’s not a good idea to structure the folders this way. Just bind mount your media directory between both containers to avoid any potential issues. You might break something with this setup if you're not careful.
Thanks for the heads up! I’ll keep that in mind.
One thing to note is that if you edit files directly outside of Nextcloud, you'll have to run a detection script to get Nextcloud to recognize the changes. Otherwise, it won’t show the updated data.
Wait, so if I rename a file in Jellyfin, I’ll have to restart Nextcloud to see that change? That could be a hassle!
You don't really need to nest directories like that. Just bind mount your media folder for both containers. Just keep in mind that Jellyfin has specific needs for folder structure, and Nextcloud might add its own folders too. What exactly are you trying to achieve by linking both?
I'm just looking to see all my movies in Nextcloud and launch them directly in Jellyfin instead of having to download them each time. I was also just curious if the two containers would conflict over permissions or anything.
Exactly! You can bind any directory, and Docker doesn't have a problem with it. Just remember, you can also bind child contents along with the parent.