Fresh Proxmox install, having a dreadful time. Trying not to be dramatic, but this is much worse than I imagined. I’m trying to migrate services from my NAS (currently docker) to this machine.

How should Jellyfin be set up, lxc or vm? I don’t have a preference, but I do plan on using several docker containers (assuming I can get this working within 28 days) in case that makes a difference. I tried WunderTech’s setup guide which used an lxc for docker containers and a separate lxc of jellyfin. However that guide isn’t working for me: curl doesn’t work on my machine, most install scripts don’t work, nano edits crash, and mounts are inconsistent.

My Synology NAS is mounted to the host, but making mount points to the lxc doesn’t actually connect data. For example, if my NAS’s media is in /data/media/movies or /data/media/shows and the host’s SMB mount is /data/, choosing the lxc mount point /data/media should work, right?

Is there a way to enable iGPU to pass to an lxc or VM without editing a .conf in nano? When I tried to make suggested edits, the lxc freezes for over 30 minutes and seemingly nothing happens as the edits don’t persist.

Any suggestions for resource allocation? I’ve been looking for guides or a formula to follow for what to provide an lxc or VM to no avail.

If you suggest command lines, please keep them simple as I have to manually type them in.

Here’s the hardware: Intel i5-13500 64GB Crucial DR5-4800 ASRock B760M Pro RS 1TB WD SN850X NVMe

  • Tinkerer@lemmy.caEnglish
    1·
    1 day ago

    I run jellyfin on an LXC, so first get jellyfin installed personally I would separate jellyfin and your other docker containers, I have a separate VM for my podman containers. I need jellyfin up 100% of the time so that’s why its separate.

    Work on the first problem, getting jellydin installed I wouldn’t use docker, just follow the steps for installing it on Ubuntu directly.

    Second, to get the unprivileged lxc to work with your nas share follow this forum post: https://forum.proxmox.com/threads/tutorial-unprivileged-lxcs-mount-cifs-shares.101795/

    Thirdly, read through the jellyfin docs for hardware acceleration. Its always best practice to not just run scripts blindly on your machine.

    Lastly take a break if you can’t figure it out, when I’m stuck I always need to take a day and just think stuff over and I usually figure out why its not working by just doing that.

    If you need any help let me know!

    • LazerDickMcCheese@sh.itjust.worksOPEnglish
      1·
      22 hours ago

      So I got Jellyfin running last night as an unprivileged LXC using a community script. It’s accessible via web browser, and I could connect my NAS. Now I’m having NAS-server connection issues and “fatal player” issues on certain items. I appreciate the support, I’m going to need a lot of it haha

  • curbstickle@anarchist.nexusEnglish
    0·
    2 days ago

    How should Jellyfin be set up, lxc or vm

    Either way. I prefer lxc, personally, but to each their own. lxc I think is drastically easier, in part because you don’t need to pass through the whole GPU…

    Is there a way to enable iGPU to pass to an lxc or VM without editing a .conf in nano?

    You don’t need to pass the igpu, you just need to give the LXC access to render and video groups, but yes, editing the conf is easiest. I originally wrote out a bunch here, then remembered there is a great video.

    https://www.youtube.com/watch?v=0ZDr5h52OOE

    My Synology NAS is mounted to the host, but making mount points to the lxc doesn’t actually connect data

    Do they show up as resources? I add my mount points at the CLI personally, this is the best way imo:

    pct set 100 -mp0 /mnt/pve/NAS/media,mp=/media

    This is done from the host, not inside the LXC.

    Does your host see the mounted NAS? After you added the mount point, did you fully stop the container and start it up again?

    Edit: You can just install curl/wget/etc BTW, its just Debian in there.

    apt install curl

    Edit 2: I must have glossed over the mount part.

    Dont add your network storage manually, do it through proxmox as storage, by going to Datacenter > Storage > Add, and enter the details there. This will make things a lot easier.

    • LazerDickMcCheese@sh.itjust.worksOPEnglish
      0·
      2 days ago

      Do they show up as resources? I add my mount points at the CLI personally, this is the best way imo: pct set 100 -mp0 /mnt/pve/NAS/media,mp=/media

      I’d love to check that, but you lost me…

      So the NAS was added like you suggested; I can see the NAS’s storage listed next to local data. How does one command an lxc or vm to use it though?

      • curbstickle@anarchist.nexusEnglish
        0·
        2 days ago

        This line right here shares it with the LXC, I’ll break it down for you:

        pct set 100 -mp0 /mnt/pve/NAS/media,mp=/media

        pct is the proxmox container command, youre telling it to set the mount point (mp0, mp1, mp2, etc). That point on the host is /mnt/pve/yourmountname. In the container is on the right, mp=/your/path/. So inside the container if you did an ls command in the directory /your/path/, it would list the files in /mnt/pve/yourmountname.

        The yourmountname part is the name of the storage you added. You can go to the shell at the host level in the GUI, and go to /mnt/pve/ then enter ls and you will see the name of your mount.

        So much like I was mentioning with the GPU, what youre doing here is sharing resources with the container, rather than needing to mount the share again in your container. Which you could do, but I wouldn’t recommend.

        Any other questions I’ll be happy to help as best as I can.

        Edit: forgot to mention, if you go to the container and go to the resources part, you’ll see “Mount Point 0” and the mount point you made listed there.

        • LazerDickMcCheese@sh.itjust.worksOPEnglish
          0·
          22 hours ago

          Are there different rules for a VM with that command? I made a 2nd NAS share point as NFS (SMB has been failing, I’m desperate, and I don’t know the practical differences between the protocols), and Proxmox accepted the NFS, but the share is saying “unknown.” Regardless, I wanted to see if I could make it work anyway so I tried ‘pct set 102 -mp1 /mnt/pve/NAS2/volume2/docker,mp=/docker’

          102 being a VM I set up for docker functions, specifically transferring docker data currently in use to avoid a lapse in service or user data.

          Am I doing this in a stupid way? It kinda feels like it

          • curbstickle@anarchist.nexusEnglish
            0·
            22 hours ago

            For the record, I prefer NFS

            And now I think we may have the answer…

            OK so that command is for LXCs, and not for VMs. If youre doing a full VM, we’d mount NFS directly inside the VM.

            Did you make an LXC or a VM for 102?

            If its an lxc, we can work out the command and figure out what’s going on.

            If its a VM, we’ll get it mounted with NFS utils, but how is going to depend on what distribution you’ve got running on there (different package names and package managers)

            • LazerDickMcCheese@sh.itjust.worksOPEnglish
              0·
              22 hours ago

              Ah, that distinction makes sense…I should’ve thought of that

              So for the record, my Jellyfin-lxc is 101 (SMB mount, problematic) and my catch-all Docker VM is 102 (haven’t really connected anything, and I don’t care how it’s done as long as performance is fine)

              • curbstickle@anarchist.nexusEnglish
                0·
                21 hours ago

                Ok we can remove it as an SMB mount, but fair warning a few bits of CLI to do this thoroughly.

                • Shut down 101 and 102
                • In the Web GUI, go to the JF container, go to resources, and remove that mount point. Take note of where you mounted it! We’re going to mount it back in the same spot.
                • Go to the web GUI, go to Storage, select the SMB mount of the NAS, and select Edit - then uncheck Enable.
                • With it selected, go ahead and click remove
                • For both 101 and 102, lets make sure they aren’t set to start from boot for now. Go to each of them, and under the options section, you’ll see “Start at Boot”. If they say yes, change it to No (click edit or double click and remove the check from the box).
                • Reboot your server
                • Lets check that the mounting service is gone, go to the host then shell, and enter systemctl list-units "*.mount"
                • If you don’t see mnt-pve-thenameofthatshareyoujustremoved.mount, its removed.

                That said - I like to be sure, so lets do a few more things.

                • umount -R /mnt/pve/thatshare - Totally fine if this throws an error
                • Lets check the mounts file. cat /proc/mounts - a whooole bunch of stuff will pop up. Do you see your network share listed there? If so, lets go ahead and delete that line. nano /proc/mounts, find the line if its still there, and remove it. ctrl+x then y to save.

                Ok, you should be all clear. Lets go ahead and reboot one more time just to clear out anything if you had to make any further changes. If not, lets re-add.

                Go ahead and add in the NAS using NFS in the storage section like you did previously. You can mount to that same directory you were using before. Once its there, go back into the Shell, and lets do this again: ls -la /mnt/pve/thenameofyourmount/

                Is your data showing up? If so, great! If not, lets find out whats going on.

                Now lets add back to your container mount. You’ll need to add that mount point back in again with: pct set 100 -mp0 /mnt/pve/NAS/media,mp=/media (however you had it mounted before in that second step).

                Now start the container, and go to the console for the container. ls -la /whereveryoumountedit - if it looks good, your JF container is all set and now working with NFS! Go back to the options section, and enable “Start at Boot” if you’d like it to.

                Onto the VM, what distribution is installed there? Debian, fedora, etc?

                • LazerDickMcCheese@sh.itjust.worksOPEnglish
                  0·
                  19 hours ago

                  Well, now the jelly lxc is failing to boot "run_buffer: 571 Script exited with status 2 Lxc_init: 845 failed to run lxc.hook.pre-start for container “101"”

                  But the mount seems stable now. And the VM is Debian 12

      • jjffnn@feddit.dkEnglish
        0·
        2 days ago

        The linked repository is unmaintained, and some of the scripts are broken as a result.
        The scripts have moved to this repository.
        Last time i used then they worked fine.
        Try the scripts in the new one, and if they still give you errors let me know and i’ll be happy to try and help you.
        Also, please don’t run scripts from the internet without reading trough them first. Even from a trusted source. You never know what random people could have written in there. 😅

          • jjffnn@feddit.dkEnglish
            0·
            1 day ago

            It always works for me to just paste with ctrl+shift+v directly in the terminal window of the web gui.

            • LazerDickMcCheese@sh.itjust.worksOPEnglish
              0·
              1 day ago

              Interesting, what browser do you use? Sounds like I may have to switch from Firefox if that’s the case because this lack of quality of life is ridiculous

              • jjffnn@feddit.dkEnglish
                0·
                1 day ago

                I use firefox as well, on linux mint, not windows. So if you use windows, that may be the culprit. I haven’t used it in a long time so i don’t know if that could be the case.

                • LazerDickMcCheese@sh.itjust.worksOPEnglish
                  0·
                  23 hours ago

                  Well, this is the first step in me eventually dropping Windows (assuming all goes well). I’d like to wipe my main PC and do a dual-boot situation eventually, but migrating services to an actual server takes priority…got kiddos counting on their cartoons, can’t let em down