cross-posted from: https://lemmy.zip/post/40833329
We are pleased to announce the first release candidate preview release of Jellyfin 10.11.0!
This is a preview release, intended for those interested in testing 10.11.0 before it’s final public release. We welcome testers to help find as many bugs as we can before the final release.
As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!
WIP release notes: https://notes.jellyfin.org/v10.11.0_features
This is the first release that uses the new EF Core database mapper. If you’d like to help test this release, please remember to remove all plugins to make debugging logs as easy as possible.
i gave emby and jellyfin a testrun yesterday using docker. I kept emby because i can easily add smb shares using the webinterface. jellyfin requires me to mount those to the host/container. am i using jellyfin wrong?
I see you’ve got some downvotes, but without anyone suggesting a solution.
You can add the mount points in the docker compose file and then configure Jellyfin to read from the path(s) mounted in the container (/media/movies)
Eg:
volumes: # local path : path in container - /mnt/storage/media/movies:/media/moviesi know. i did. i hate it. thanks though. but that usually also requires fiddling with fstab and nobody wants that. just imagine the user roles and rights desasters that anyone with access to the host can see the mount. mount where you need the data, not in 2 or more places just to access it from one place. for me personally emby works much better on this. there are so many environments where you can deploy docker but not modify the host - so i do not see jellyfin really being useable here. i wish they’d add this, but from google searches i understand that it has been requested and there does not seem to be any intention to implement it.
Why is it not mounted on the host/cointainer? I dont think you are using jellyfin “wrong” but its not like you cant just configure a mount point if you wanted to use jellyfin with it.
That is an interesting thing to point out though, im not actually sure but i think they used to support smb shares directly, i might just be thinking of kodi though.
it is not mounted to the container because that is a shit solution. the host would need to mount it and pass that to tge container. emby i stop the container and no connection to the share. mounted in host it would still be there. not to mention the hassle this also means more traffic. an idea why jellyfin doesnt do shares like emby?
Maybe because it’s not an obviously wanted feature? But I’m just guessing. You should request it and see what happens, maybe more people want it. I’ve never even thought about it, since in the case of Podman/docker it’s so “obvious” and easy to just mount network shares to the host first. And in the case of Kubernetes you can just mount NFS shares directly into pods.
Docker(/Compose) can do mounts directly to the container as well.
https://blog.stefandroid.com/2021/03/03/mount-nfs-share-in-docker-compose.html
https://docs.docker.com/engine/storage/volumes/#create-a-service-which-creates-an-nfs-volume
I’ve used NFS mounts with docker compose before but I see the second link also includes an example for CIFS as well.
Oh, alright! I didn’t know that. Thank you for the info, that’s handy to know.