this post was submitted on 05 Nov 2025
45 points (97.9% liked)

Selfhosted

52787 readers
598 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
45
[Proxmox] Jellyfin w/ NAS mount + iGPU passthrough (sh.itjust.works)
submitted 2 days ago by LazerDickMcCheese@sh.itjust.works to c/selfhosted@lemmy.world
70 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

you are viewing a single comment's thread
view the rest of the comments
[–] curbstickle@anarchist.nexus 2 points 3 hours ago (1 children)

It definitely is, especially if you get a cluster going. FWIW, my media is all on a synology NAS (well technically two, but one is a backup) that I got used through work, so your setup isn't the wrong approach (imo) by any stretch.

What it comes down to in the connection is how you look at it - with a VM, its a full fledged system, all by its lonesome, that just happens to live inside another computer. A container though is an extension of that host, so think of it less like a VM and more like resource sharing, and you'll start to see where the different approaches have different advantages.

For example, I have transcode nodes running on my proxmox cluster. If I had JF as a VM, I'd need another GPU to do that - but since its a container for both JF and my transcode node, they get to share that resource happily. Whats the right answer is always going to depend on individual needs though.

And glad I could be of some help!

[–] LazerDickMcCheese@sh.itjust.works 2 points 3 hours ago

In case you want to keep following, I did make that post in c/jellyfin