I want to use Jellyfin on Proxmox, if that is a thing. After reading a post here where most people recommended Debian as host OS I want to make a VM running Debian and install Jellyfin Server there.

Now I have a few questions:

  • I see many people install Jellyfin via docker. Does that have any advantages? I would prefer to avoid docker as it adds a level of complexity for me.

  • where do I save my media? I have a loose plan to run a second VM running openMediaVault where all my HDDs are passed through and then use NFS to mount a folder on the Jellyfin VM. Is that a sane path?

  • what do I have to consider on Proxmox, to get the best hardware results on Jellyfin? Do I need some special passthrough magic to get it running smoothly? I don’t have a dedicated GPU, does that make the configuration easier?

  • Fermiverse@feddit.deEnglish
    0·
    11 months ago

    So since the LXC route is promoted here take a look into these Helper Scripts they make the use of LXC very easy.

    That said you could still adjust parameters afterwards and when you feel comfortable with.

    • glasgitarrewelt@feddit.deOPEnglish
      0·
      11 months ago

      Thank you for your answer. I maybe want to add some features in the future, like all those *arr- programs. Wouldn’t it be easier to have everything in one VM instead of many LXC?

      • Kaavi@lemmy.worldEnglish
        0·
        11 months ago

        I have arr in lxc also, I just map a folder from the host into the lxc containers. It’s working flawless, plus it’s quite flexible.

        I also have a few things running in docker, but if I can get it in lxc I do that.

        And it’s so easy doing with the scripts from the page I linked to you:)

  • thejevans@lemmy.mlEnglish
    0·
    11 months ago

    A lot of services that I run on my Proxmox host are far easier to set up and maintain as a docker container because that’s just how the developer packages them. Proxmox says that Docker in an LXC is no-no, so to reduce the maintenance overhead and to stick to supported builds, I use a bunch of VMs with many running Docker. Jellyfin has install instructions to run directly on Debian, and that works for me, but don’t be afraid to run Docker on a Proxmox VM if it will make your life easier.

    • glasgitarrewelt@feddit.deOPEnglish
      0·
      11 months ago

      Proxmox could be the perfect learning environment for docker, just make a new VM if I borg something. I will look into it, thanks. Just not for this specific project, Jellyfin on Debian sounds good for me.

  • ostsjoe@lemmy.worldEnglish
    0·
    11 months ago

    Jellyfin is very conveniently packaged in docker, so while it may seem daunting, I highly recommend at least trying that route.

    Running an nfs mount, docker or not, should be perfectly fine. Jellyfin just uses normal storage so won’t care if it’s nfs. No real special considerations with proxmox either, especially without worrying about a dedicated GPU. Just spin up a Debian guest and go.

    • glasgitarrewelt@feddit.deOPEnglish
      0·
      11 months ago

      The other comment made sense to me, why contain a container. But you are right, I will learn more about docker, it seems like a great tool.

      Thank you for your confirmation with NFS. Just read about it yesterday, in search of an alternative to samba, what all the windows user seem to use.

      • atzanteol@sh.itjust.worksEnglish
        0·
        11 months ago

        You “contain the container” because the VM provides storage and compute for docker (the docker container needs to run “somewhere”).

        I use a VM on proxmox to run a jellyfin container. VM mounts needed NFS dirs for config and media. Then create a systemd service to start/stop the container.

        • glasgitarrewelt@feddit.deOPEnglish
          0·
          11 months ago

          I understand that I can use a VM to run docker, but:

          Wouldn’t make a LXC more sense than a VM with docker inside? And what are the advantages of running jellyfin in a container instead of a normal installation? The VM is already kind of a container, what benefits do I get from yet another container inside? I am curious to learn more!

          • thirdBreakfast@lemmy.worldEnglish
            0·
            11 months ago

            Your head might be spinning from all the different advice you’re getting - don’t worry, there are a lot of options and lots of folk are jumping in with genuinely good (and well meaning) advice. I guess I’ll add my two cents, but try and explain the ‘why’ of my thinking.

            I’m assuming from your questions you know your way around a computer, can figure things out, but haven’t done much self-hosting. If I’m wrong about that, go ahead and skip this suggestion.

            • Jellyfin good - a common gateway drug to homelabbing, and the only thing you’ll do that non-tech friends will appreciate
            • Proxmox good - it makes the backups simple and provides a path forward for all sorts of things
            • Docker good - you’ve said it increases complexity; this is correct in that you’re adding more layers of stuff, but it reduces your complexity of management by removing a heap of dependency issues. There is a compute and memory overhead involved, but it’s small and the tradeoff is worth it.
            • VM good - yes an LXC is more efficient, but it’s harder to run docker in. Save that for a future project
            • Media data somewhere else good - I run a separate NAS with an SMB share. A NAS in a VM is a compromise, but like all things self hosting, you start out with what you’ve got. I let Jellyfin keep the metadata in the VM that’s hosting my Jellyfin though since the NAS is over the network. That’s less of a consideration if you are visualizing your NAS on the same machine, but I’d still do it my way for future proofing.
            • Passthrough magic not yet - this can also be a future project. If your metal has quicksync that can be utilized to reduce the CPU load, but that can also be a future project.
            • glasgitarrewelt@feddit.deOPEnglish
              0·
              11 months ago

              That summarized my situation pretty good. Since a year now I switched everything to Linux, selfhosting seems to be a natural extension of that.

              May I ask, since you have a very beginner-friendly way of writing:

              I run a separate NAS with an SMB share.

              Why did you choose SMB instead of NFS? I read here that NFS is very efficient and fast.

              Docker good

              Many people here have very convincing arguments for docker. While checking it out I saw that it uses partly proprietary licenses. Why are so many people so sure that docker won’t pull a ‘Unity-stunt’ and make their knowledge about docker obsolete?

              LXC is more efficient, but it’s harder to run docker in.

              I meant to install a Jellyfin LXC, if there is such a thing, without docker involved. Is that possible?

  • Possibly linux@lemmy.zipEnglish
    0·
    11 months ago

    Silly question but what is your question? Yes you can run jellyfin in docker in a VM on Proxmox. Personally have a similar setup and I don’t use GPU encoding or decoding.

    Also GPU passthough to a VM with vfio is generally pretty good and stable so if you want GPU acceleration it shouldn’t be to hard. I personally run a virtual machine for gaming that has a GPU and USB controller passed though to it. I can’t even tell the difference in terms of hardware performance

    • glasgitarrewelt@feddit.deOPEnglish
      0·
      11 months ago

      There seem to be many ways to reach the same goal:

      • run Jellyfin in Docker in a VM in Proxmox
      • install Jellyfin Server in Debian in a VM in Proxmox
      • install a Jellyfin LXC container on proxmox
      • … Probably more

      I try to find the best way for me.