this post was submitted on 05 Nov 2025
52 points (98.1% liked)

Selfhosted

53061 readers
577 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
52
[Proxmox] Jellyfin w/ NAS mount + iGPU passthrough (sh.itjust.works)
submitted 2 weeks ago by LazerDickMcCheese@sh.itjust.works to c/selfhosted@lemmy.world
76 comments fedilink hide all child comments
 

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

top 50 comments
sorted by: hot top controversial new old
[–] frongt@lemmy.zip 11 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

curl doesn't work on my machine, most install scripts don't work, nano edits crash, and mounts are inconsistent.

If your system is that fucked, I would wipe it and start over. And don't run any scripts or extra setup guides, they're not necessary.

Personally I run all my containers in a Debian VM because I haven't bothered migrating them to anything proxmox native. But gpu accel should work fine if you follow the directions from jellyfin: https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/

Just make sure you follow the part about doing it in docker.

load more comments (3 replies)
[–] 4am@lemmy.zip 6 points 2 weeks ago (1 children)

It may be better now but I’ve always had problems with Docker in LXC containers; I think this has to do with my storage backend (Ceph) and the fact that LXC is a pain to use with network mounts (NFS or SMB); I’ve had to use bind mounts and run privileged LXCs for anything I needed external storage for.

Proxmox is about managing VMs and LXCs. I’d just create a VM and do all your docker in there. Perhaps make a second VM so you can shuffle containers around while doing upgrades.

If you plan to have your whole setup be exclusively Docker and you have no need for VMs or LXCs, then Proxmox might be a bunch of overhead you don’t need.

I use the LXCs for simple stuff that does a bare-metal type install within them, and I use the VMs for critical services like OPNSense firewall/routers. I also have a Proxmox cluster across three machines so I can live-migrate VMs during upgrades and prevent almost any downtime. For that use case it’s rock solid. It’s a great product and it offers a lot.

If you just need a single machine and only Docker, it’s probably overkill.

[–] LazerDickMcCheese@sh.itjust.works 3 points 2 weeks ago (1 children)

Well, the plan was to use a couple VMs for niche things that I'd love to have and many services. But if I can't get Proxmox working as advertised, I'll throw most of that out of the window

[–] 4am@lemmy.zip 2 points 2 weeks ago (1 children)

The easiest solution if you want to have managed VMs IMHO is to just make a large VM for all your docker stuff on Proxmox and then you get the best of both worlds.

Abstracting docker into its own VM isn’t going to add THAT much overhead, and the convenience of Proxmox for management of the other VMs will make that situation much easier.

LXC for docker can be made to work, but it’s fiddly and it probably won’t gain you much in the long run.

Now, all these other issues you seem to be having with the Proxmox host itself; are you sure you have networking set up correctly, etc? curl should be working no problem; I’m not sure what’s going on there.

[–] LazerDickMcCheese@sh.itjust.works 1 points 2 weeks ago

That's good to know at least. I was getting anxious last night thinking that I signed up for something I'd never get running. So curl is working now...not sure why it wasn't earlier, but I've used it since and it is confirmed working. And networking (as in internet connectivity) is working, but now I'm struggling with the NAS mount: it was working perfectly at first, but now it's randomly shifting between "available" and "unknown".

[–] webhead@sh.itjust.works 4 points 2 weeks ago

https://community-scripts.github.io/ProxmoxVE/scripts?id=jellyfin

This is the way I'd imagine. I used this for Plex and this should make iGPU a lot easier.

[–] curbstickle@anarchist.nexus 3 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

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.works 1 points 2 weeks ago (1 children)

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.nexus 4 points 2 weeks ago* (last edited 2 weeks ago) (24 children)

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.works 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Friend, thank you. My users and I greatly appreciate it. You just taught me how to solve one of the biggest problems I've been having. Just tested a movie through Jellyfin after using that cli.

Got any pointers for migrating config files from my NAS's docker containers to Proxmox's LXCs/VMs?

[–] curbstickle@anarchist.nexus 1 points 2 weeks ago (1 children)

No worries!

So if you've got docker containers going already, you don't need them to be LXCs.

So why not keep them docker?

Now there are a couple of approaches here. A VM will have a bit higher overhead, but offers much better isolation than lxc. Conversely, lxc is lightweight but with less host isolation.

If we're talking the *arr stack? Meh, make it an lxc if you want. Hell, make it an lxc with dockge installed, so you can easily tweak your compose files from the web, convert a docker run to compose, etc.

If you have those configs (and their accompanying data) stored on the NAS itself - you dont have to move them. Let's look at that command again...

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

So let's say your container data is stored at /opt/dockerstuff/ on your NAS, with subdirectories of dockerapp1 and dockerapp2. Let's say your new lxc is number 101. You have two options:

  • Mount the entire directory

pct set 101 -mp0 /mnt/Pve/NAS/opt/dockerstuff,mp=/opt/dockerstuff

  • Mount them specifically for each container to get a bit more granular in control
pct set 101 -mp0 /mnt/Pve/NAS/opt/dockerstuff/dockerapp1,mp=/opt/dockerstuff/dockerapp1

pct set 101 -mp1 /mnt/Pve/NAS/opt/dockerstuff/dockerapp2,mp=/opt/dockerstuff/dockerapp2

Either will get you going

[–] LazerDickMcCheese@sh.itjust.works 1 points 2 weeks ago (1 children)

I think I'm getting a grip on some of the basics here. I was trying to make a new mount for my NAS's docker data...separate drive and data pool. In the process of repeated attempts to get the SMB mount to get accepted, I noticed my NAS's storage isn't working as intended suddenly.

'cat /etc/pve/storage.cfg' shows the NAS still 'pvesm status' says "unable to activate storage...does not exist or is unreachable"

I thought it was related to too much resource usage, but that's not the case

[–] curbstickle@anarchist.nexus 1 points 2 weeks ago (1 children)

What do you get putting in:

showmount <ip address of NAS>

[–] LazerDickMcCheese@sh.itjust.works 2 points 2 weeks ago (1 children)

"Hosts on 192.168.0.4:" As a novice, I get the feeling that means it's not working

[–] curbstickle@anarchist.nexus 2 points 2 weeks ago (3 children)

If you've got nothing under it, yeah.

OK, what I'd probably do is shutdown proxmox, reboot your nas, wait for the nas to be fully up and running (check if you can access it from your regular computer over the lab), then boot up the proxmox server.

Then run that command again, you should see a result.

Its possible you've got some conflicting stuff going on if you did manual edits for the storage, which may need to be cleaned up.

load more comments (3 replies)
load more comments (23 replies)
[–] Tinkerer@lemmy.ca 3 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

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.works 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

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

[–] Tinkerer@lemmy.ca 2 points 1 week ago (7 children)

This is most likely because of encoding. Did you change any settings in jellyfin for hardware acceleration? Have you passed theough your GPU? You will need to find out what codecs your GPU supports and enable those in the jellyfin hardware encoding spot.

load more comments (7 replies)
[–] NameTaken@lemmy.world 2 points 2 weeks ago (2 children)

https://tteck.github.io/Proxmox/ this is a good place to start. Also highly recommend youtube videos lots of good stuff there.

[–] jjffnn@feddit.dk 6 points 2 weeks ago

Tteck is unfortunately no longer with us.
The new proxmox scripts project can be found here.

[–] LazerDickMcCheese@sh.itjust.works 1 points 2 weeks ago (1 children)

Yes, I tried a couple of those. They were giving me errors

[–] jjffnn@feddit.dk 6 points 2 weeks ago (2 children)

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. 😅

[–] irmadlad@lemmy.world 2 points 2 weeks ago (1 children)

Can confirm. The scripts in the new repository work just fine. I've run a bunch of them.

[–] LazerDickMcCheese@sh.itjust.works 3 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I was struggling with it for a bit, but I got it working. Main concern (before I check transcoding/acceleration) is NAS file sharing. Huge headache. The host is connected, but the lxc and vms don't use it

[–] jjffnn@feddit.dk 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

May i be so bold as to ask about how much experience you have with linux?
A basic understanding would go a long way i think.

But to answer your question:
You need to mount the nas drive directly to the lxc running jellyfin, not to the proxmox host.

[–] LazerDickMcCheese@sh.itjust.works 2 points 2 weeks ago (1 children)

Probably hundreds of hours, but very little was in a functional desktop...most of it was trying to get an install to boot and update software (I'm not joking).

[–] jjffnn@feddit.dk 1 points 2 weeks ago

That sucks. But this is a good way to learn.

[–] LazerDickMcCheese@sh.itjust.works 1 points 2 weeks ago (1 children)

Any tips on copy-pasting those commands into a console window? Every function I've tried has failed, but I'm willing to keep trying

[–] jjffnn@feddit.dk 1 points 2 weeks ago (1 children)

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

[–] LazerDickMcCheese@sh.itjust.works 2 points 2 weeks ago (1 children)

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.dk 1 points 2 weeks ago (1 children)

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.works 2 points 2 weeks ago (2 children)

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

load more comments (2 replies)
[–] ryokimball@infosec.pub 1 points 2 weeks ago (2 children)

There is a helper script for jellyfin LXC. From memory I can't help much, but I suggest searching for that. I think the default specs for disk space and RAM were weak, But setup was easy enough. After the initial helper script, you will need to learn how to mount the NAS into the LXC as well.

[–] ryokimball@infosec.pub 1 points 2 weeks ago (1 children)

I want to say iGPU makes things easier, not because of experience but only because I tried passing through an Nvidia card and the instructions all insinuated this was more difficult than any other option

[–] curbstickle@anarchist.nexus 1 points 2 weeks ago* (last edited 2 weeks ago)

If youre going LXC, its not going to matter much of you just map GIDs and provide the LXC access to the host.

Side bonus, multiple LXCs and they can all share that GPU. This is what I do, I have a couple of JF instances among other containers that use the GPUs.

Edited to add: Well, nvidia itself can be a pain. But that'd be because nvidia.

load more comments (1 replies)
load more comments
view more: next ›