I run the steam headless docker, using dockers you don't have to pass through a gpu so Jellyfin can still use it for transcoding aswell. Or like you said you can go the other way and put them both in a vm
I have a TrueNAS Scale NAS in my home network. Since they using k3s, your NVidia GPU should be picked up automatically: https://docs.k3s.io/advanced#nvidia-container-runtime-support If you have troubles, I guess a little tweak here and there and you should be fine. I generally recommend Truenas, it serves me several years until now.
You could possibly also use proxmox and setup a VM for docker, games (use GPU passthrough), and TrueNAS. You also combine docker and games to same VM to use GPU for jellyfin. Only thing is I'm not quite sure how well your games will play (guess it depends on what games). Also keep in mind TrueNAS requires alot of memory (RAM). If you don't have enough for your games and TrueNAS you may have some performance issues.
You could also try running everything from within TrueNAS but personally I'm not a fan of it. I haven't tried TrueNAS scale yet but it does look promising.
I'd prefer to use it as a NAS most the time as it has plenty of drive bays and I need somewhere better to run jellyfin than my desktop.
I feel like "NAS" has simply lost all meaning.
Network attached storage? I don't see the issue with OPs usage of the term.
Jellyfin is a NAS?
The storage for Jellyfin is a NAS. You can run it on a Synology NAS too. This is the same thing just DIY.
They're looking to run Jellyfin on the nas. And do a little gaming. That's not a NAS. It's a server/desktop that serves nfs shares.
I'm sure there are some folks who run a NAS simply for the joy of storing files. Most of us care primarily about what services can use those files, ideally with the same machine serving both functions.
That, is not a NAS then.
I feel like you are the one who is confusing a "NAS device" or "NAS appliance" as in a device that is specifically designed and primarily intended to provide NAS services (ie, its main attribute is large disks, with little design weight given to processing, RAM or other components except to the extent needed to provide NAS service), and a NAS service itself, which can be provided by any generic device simultaneously capable of both storage and networking, although often quite poorly.
You are asserting the term "NAS" in this thread refers exclusively to the former device/appliance, everyone else is assuming the latter. In fact, both are correct and context suggests the latter, although I'm sure given your behavior in this thread you will promptly reply that only your interpretation is correct and everyone else is wrong. If you want to assert that, go right ahead and make yourself look foolish.
Please quiet
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:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!