Any Linux nerds willing to help me out with my Proxmox booty chest?

I'm assuming this is (one of) the threads you were looking at? https://forum.proxmox.com/threads/tutorial-unprivileged-lxcs-mount-cifs-shares.101795/

I know little about proxmox/LXC but lots about linux and containers in general so I might be able to help

Seems like you should be able to go into the LXC container and run (as root user, or with sudo):

groupadd -g 10000 lxc_shares

usermod -aG lxc_shares jellyfin

then shut down the LXC

And then on the proxmox host run (also all with root):

mkdir -p /mnt/lxc_shares/nas_rwx

echo '//NAS/nas/ /mnt/lxc_shares/nas_rwx cifs _netdev,x-systemd.automount,noatime,uid=100000,gid=110000,dir_mode=0770,file_mode=0770,user=smb_username,pass=smb_password 0 0' | tee -a /etc/fstab

Where //NAS/nas is the IP or hostname of the share (possibly localhost?) followed by the share folder name, and the username and password are set appropriately

mount /mnt/lxc_shares/nas_rwx

and if that succeeds,

echo 'mp0: /mnt/lxc_shares/nas_rwx/,mp=/mnt/nas' | tee -a /etc/pve/lxc/LXC_ID.conf

replacing LXC_ID with the VM ID of the LXC container (not sure how you get this but if you only have the one you could probably ls /etc/pve/lxc and see what options are there

Then you should be able to start the LXC back up, and when you get to the point in jellfyfin of setting the media folder, just type /mnt/nas and press enter (or a subdir of it ig) and it should find it

if you did all that and it didn't work then would need more info to help troubleshoot

Hi comrade! I hope it's cool to give other advice as well. I'll start with the other advice.

If you have more then 3 (roughly identical) disks for your NAS, then you may want to consider RAIDZ2 as it will be slightly more robust. If you have at least 6 drives it will also give you substantially more useable storage. If neither of these apply or you just don't wanna, it's not a big deal.

You may also want to consider running ZFS directly on the host rather than from the VM. ZFS likes to have full management of raw disks and can be CPU and memory-intensive at times, really benefiting from various CPU features your actual processor may have. The downside here would be that you'd be using ZFS on Linux rather than the slightly more feature-rich upstream ZFS running on BSD, but imo that tradeoff is worth it. This is not a huge deal either so long as your VM is providing truly raw access to the underlying disks (just a performance tweak).

Okay so now proxmox stuff.

Proxmox just makes it slightly easier to install and monitor and configure various open source software on Debian. Every thing you run or concept you use is actually some lower-level thing that you could do separately if you wanted to. For example, you could create lxc containers using lxc on plain Debian or virtual machines with qemu on plain Debian. This can be helpful when learning, because proxmox just shows you all the knobs you can fiddle but forgets to tell you that, say, cloud-init is an upstream thing with its own documentation that explains how to use it.

So, in your case, it may be helpful to forget that it's proxmox and instead think of it this way: you have a NAS and an lxc container and you want to share some files on the NAS with the lxc container (videos and stuff from the NAS to jellyfin running on the lxc container).

There are actually many valid answers:

• Mapping a NAS directory to the shared host and then mapping it read-only to the lxc container.
• Using an NFS on the NAS (using zfs or directly with NFS)
• Using a Samba share on the NAS (using zfs or directly with NFS)
• Using iSCSI on the NAS (with zfs and relevant iSCSI tools)

I would personally recommend thinking of your NAS and lxc container as if they are two separate computers on the same network, so your job would be to figure out how to share over the network (so not using the first option).

If your videos are on a single zfs volume/dataset, then using zfs' built-in support for NFS is my recommendation. If you only want to share a subdirectory, then I'd still use NFS but I'd set up /etc/exports (or equivalent) myself. Ideally you'd put a password on the share.

Once shared, you can set up your lxc container to read-only mount the NFS share. Do this by pointing it at the (hopefully static!) IP address of your NAS using proxmox tools + docs. If both are running via proxmox, then the bridge interface should already be set up for you on the host, so you just need to make sure both virtualized environment IPs are on your LAN CIDR, so like 192.178.0.[1-255] or whatever (there are other options but this is simplest). This is under the network tab for the VM or lxc container. You may need to restart the lxc container for the NFS share to be mounted.

Then just point jellyfin at the local path (on the lxc container) that the NFS share is mounted on.

One thing to look out for: don't put your jellyfin database (in its config dir) on a rw NFS share. It's an SQLite database and due to how NFS works there is a risk of database corruption. By default the database will still be in your lxc container and not on any NFS share, just wanted to mention this potential future pitfall.

Edit: I personally use iSCSI or much weirder things for media volume sharing and forgot that NFS (and Samba) doesn't send inotify events by default. So you may want to look into iSCSI or doing specific workarounds that stimulate inotify. inotify is helpful because it tells jellyfin when there are new files available.