52

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 new old
[-] frongt@lemmy.zip 11 points 9 months ago* (last edited 9 months ago)

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 9 months ago

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 9 months ago

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 9 months ago

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.

load more comments (1 replies)
[-] webhead@sh.itjust.works 4 points 9 months 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.

[-] Tinkerer@lemmy.ca 3 points 9 months ago* (last edited 9 months 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.works 2 points 9 months ago* (last edited 9 months 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

[-] Tinkerer@lemmy.ca 2 points 9 months ago

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.

[-] LazerDickMcCheese@sh.itjust.works 1 points 9 months ago

I tried taking a screenshot of the full page to show you, but yes it's set to QSV and /dev/dri/renderD128. I've tried QSV and VAAPI with similar results, I'm sticking with QSV for now as it's Jellyfin's official recommendation. I've enabled decoding for H264, HEVC, VP9, and AVI. I've enabled hardware encoding for H264 and HEVC. If I disable transoding completely it works fine, but some of the streaming devices need 720p functionality (ideally to transcode down to 4:3 480i).

[-] Tinkerer@lemmy.ca 1 points 9 months ago

Ah OK what GPU are you using? are you using the integrated graphics of your CPU?

[-] LazerDickMcCheese@sh.itjust.works 1 points 9 months ago

Yes, just using the iGPU. Thought about an Nvidia card, but setting it up sounded like torture so just whatever is on the i5-13500 for now

load more comments (4 replies)
[-] curbstickle@anarchist.nexus 3 points 9 months ago* (last edited 9 months 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.works 1 points 9 months 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.nexus 4 points 9 months ago* (last edited 9 months 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.works 2 points 9 months ago* (last edited 9 months ago)

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 9 months ago

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 9 months ago

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

load more comments (6 replies)
load more comments (23 replies)
[-] NameTaken@lemmy.world 2 points 9 months ago

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 9 months ago

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

load more comments (14 replies)
load more comments
view more: next ›
this post was submitted on 05 Nov 2025
52 points (98.1% liked)

Selfhosted

61770 readers
625 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS