Hello, I yet again come, hat in hand, for assistance from those wiser in the ways of the Linux. I’m having a bit of an issue downloading Jellyfin on my ElementaryOS laptop. I’ve tried all the guide on the first few pages of ddg only to receive errors after entering the comman “ sudo apt-get update “. I get ERR:3 https//repo.jellyfin.org/debian circle Release 404 Not found.

If someone can point me the way I’d be most appreciative

    • @Kelp@lemmy.worldOPEnglish
      8•11 hours ago

      I was so ill prepared I didn’t even know what docker was. I definitely jumped the gun on the media server lol. Eh, blessing in disguise since I’m now getting such info I guess. Thank y’all for being kind to an ignoramus

      • @hperrin@lemmy.caEnglish
        2•3 hours ago

        So, Jellyfin is one of those apps where the Docker documentation is really lacking. I’m gonna give you my docker-compose.yml file in case it helps:

        services:
  jellyfin:
    image: jellyfin/jellyfin
    user: 0:0
    restart: 'unless-stopped'
    ports:
      - '8096:8096'
    environment:
      #- JELLYFIN_CACHE_DIR=/var/cache/jellyfin
      #- JELLYFIN_CONFIG_DIR=/etc/jellyfin
      - JELLYFIN_DATA_DIR=/var/lib/jellyfin
      - JELLYFIN_LOG_DIR=/var/log/jellyfin
    volumes:
      - ./config:/config
      - ./cache:/cache
      - ./data:/var/lib/jellyfin
      - ./log:/var/log/jellyfin
      - /data/jellyfin:/data/jellyfin
    devices:
      - /dev/dri

        For me /data/ is my RAID array, which is why my jellyfin data directory is there. Everything else goes in the same directory as the compose file. My system has a graphics card that does transcoding (Arc A380), so I have /dev/dri under devices.

        You should learn a lot about Docker Compose, because it will help you tremendously. I use Jellyfin behind an Nginx Proxy Manager reverse proxy. I’d highly recommend it. Here’s my compose file for that:

        services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    network_mode: "host"
    #ports:
    #  - '80:80'
    #  - '81:81'
    #  - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

        Running in “host” mode is important, instead of just forwarding ports, because it lets you forward things to localhost, like pointing https://media/.[mydomain]/ to http://127.0.0.1:8096/ for Jellyfin.

        Anyway, best of luck to you, and I hope that helps!

    • KushanEnglish
      7•13 hours ago

      Op please don’t ignore the above.

      Learn docker once and you’ll be able to install almost anything, rather than having to learn every individual app and how it installs on specific operating systems.

    • @interdimensionalmeme@lemmy.ml
      6•15 hours ago

      Probably not interested in dealing with endless permission and proxy problems. Me I just run everything as root and password 543211111111111111Aa±

      • monovergent 🛠️
        10•17 hours ago

        To be completely honest, I installed Jellyfin “bare-metal” and have been using it that way since after attempting to skim the Docker documentation and failing to understand how Docker works.

        • @Nibodhika@lemmy.world
          4•12 hours ago

          Docker is a virtualization platform, similar to setting out a Virtual Machine but a lot less resource intense. You need to:

          • install docker on your machine
          • Start/enable the service (this is usually done automatically on most user friendly distros, and if you’re using one that doesn’t I expect you to know how to do it)
          • Add your user to the docker group

          That’s it, docker setup done, now you need to write a compose file, i.e. something that tells docker what do you want to run, usually you get a working example on any project website, and linuxserver.io is a great site for them too, for example for Jellyfin can be found here: https://docs.linuxserver.io/images/docker-jellyfin/

          Just create a folder, create a file called compose.yaml there and put that content in it, now run docker compose up -d and congratulations you have a working Jellyfin server.

          With time you’ll learn what the compose file is doing, for example the ports map ports from the docker to your machine, volumes does the same, so for example the example has /path/to/jellyfin/library:/config if instead you write ./config:/config a folder called config will be created on the same folder the compose.yaml file is and inside the docker it will be mounted as /config which is where Jellyfin will look for configurations. In the same manner you can add /home/myuser/Movies:/Movies and inside docker you will be able to see the contents of /home/myuser/Movies when scanning the /Movies folder.

        • GoldenQuetzal
          3•16 hours ago

          My friend, i would like to introduce you to the wonders of Portainer. Go forth and watch a video on youtube and you’ll get it.

          • @hperrin@lemmy.caEnglish
            4•15 hours ago

            Use Portainer if you don’t want anything to be portable. There are other issues too. Just use Docker Compose.