• 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 Troubleshooting Updated container has gone all wrong

     
    • 0 Vote(s) - 0 Average

    Updated container has gone all wrong

    Femur4889
    Offline

    Junior Member

    Posts: 8
    Threads: 1
    Joined: 2024 May
    Reputation: 0
    Country:United States
    #1
    2024-05-07, 07:55 PM
    I simply want to make my updated JF container behave exactly like my old established installation did.

    I'm really at a loss with what to do, I've troubleshot this for hours but nothing works. 

    I had not used Jellyfin in quite some time. I updated the docker container using docker compose. The container loaded but when I entered into Jellyfin on my server, none of the media files were there and my original Username/Password combo did not work.

    I do not want to lose all the metadata/info which was associated with my old server.

    I am certain that my media path is correct. My existing /config and /cache files are currently in the same place they've always been. My existing /media has been moved to a local ZFS array and I have changed the path's settings in the docker compose file.

    version: '3.5'
    services:
      jellyfin:
        image: jellyfin/jellyfin
        container_name: jellyfin
        #user: 1000:1000
        network_mode: 'host'
        volumes:
          - /mnt/500gb/docker/jellyfin/configConfused-faceconfig
          - /mnt/500gb/docker/jellyfin/cacheConfused-facecache
          - type: bind
            source: /mnt/gator1/Jellyfin/
            target: /media
            read_only: true
        restart: 'unless-stopped'
        extra_hosts:
          - 'host.docker.internal:host-gateway'

    If anyone can assist I'd be most grateful.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    Messages In This Thread
    Updated container has gone all wrong - by Femur4889 - 2024-05-07, 07:55 PM
    RE: Updated container has gone all wrong - by TheDreadPirate - 2024-05-07, 08:12 PM
    RE: Updated container has gone all wrong - by TheDreadPirate - 2024-05-07, 08:27 PM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-07, 08:41 PM
    RE: Updated container has gone all wrong - by TheDreadPirate - 2024-05-07, 11:58 PM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-08, 02:52 AM
    RE: Updated container has gone all wrong - by bitmap - 2024-05-08, 03:36 AM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-08, 07:42 PM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-08, 09:06 PM
    RE: Updated container has gone all wrong - by 3216 - 2024-05-08, 09:21 PM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-08, 11:01 PM
    RE: Updated container has gone all wrong - by Femur4889 - 2024-05-08, 11:11 PM

    • 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