• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support General Questions Change Docker Compose Image

     
    • 0 Vote(s) - 0 Average

    Change Docker Compose Image

    Lost_Ones
    Offline

    Junior Member

    Posts: 12
    Threads: 5
    Joined: 2024 Sep
    Reputation: 0
    Country:United States
    #1
    2024-09-18, 04:55 PM
    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.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-09-18, 05:03 PM (This post was last modified: 2024-09-18, 05:03 PM by TheDreadPirate.)
    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.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    Lost_Ones
    Offline

    Junior Member

    Posts: 12
    Threads: 5
    Joined: 2024 Sep
    Reputation: 0
    Country:United States
    #3
    2024-09-18, 05:15 PM
    (2024-09-18, 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.  Smiling-face

    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,
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2024-09-18, 05:37 PM
    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.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode