+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions)
+--- Thread: Change Docker Compose Image (/t-change-docker-compose-image)
Change Docker Compose Image - Lost_Ones - 2024-09-18
Hello,
I am currently running jellyfin in docker.
Is there any benefit of changing to the official docker image versus lscr.io/linuxserver's image?
jellyfin:
image: lscr.io/linuxserver/jellyfin:latest
#image: jellyfin/jellyfin
container_name: jellyfin
Now, if I change the image, and just the image, I face issues. Example, my users accounts are not all there. It seems that the databases are different?
Is there a way to safely correct this?
Regards.
RE: Change Docker Compose Image - TheDreadPirate - 2024-09-18
There aren't really any benefits to the official image. However, there have been users of linuxserver's Jellyfin image that had weird, unexplainable issues that went away when they switched to the official image.
Regarding switching images, for whatever reason they use a slightly different structure for /config. But the difference is enough to make it impossible, or unnecessarily difficult, to seamlessly switch between theirs and ours.
If you aren't having any issues with the linuxserver image, don't bother switching.
RE: Change Docker Compose Image - Lost_Ones - 2024-09-18
(Yesterday, 05:03 PM)TheDreadPirate Wrote: There aren't really any benefits to the official image. However, there have been users of linuxserver's Jellyfin image that had weird, unexplainable issues that went away when they switched to the official image.
Regarding switching images, for whatever reason they use a slightly different structure for /config. But the difference is enough to make it impossible, or unnecessarily difficult, to seamlessly switch between theirs and ours.
If you aren't having any issues with the linuxserver image, don't bother switching.
Thank you for your awesome insight as always. I am the one that had noticed that the LIveTV transcodes was not being cleaned up via the built-in tools. That was my only motivation of moving is that if/when it happens I figured that I would see it.
If you are saying stick with what I have, then I can do that. Or if there is a way to get the users migrated, that would be the most important task. I do see from the documentation a migration tool, https://github.com/Marc-Vieg/Emby2Jelly but the last commit was 3 years ago and that has me a bit nervous.
Regards,
RE: Change Docker Compose Image - TheDreadPirate - 2024-09-18
The live TV transcode cleanup issue is legit an issue with Jellyfin itself, not with linuxserver's image. So switching from linuxserver to the official image won't resolve that.
For the record, I use the official image for my test instances (direct apt install for my production instance).
I am 99.9% certain that migration tool will not work with Jellyfin as it stands today. Too many API changes in the last 3 years.