tvcvt
Another option that’s pretty much perfect as long as you don’t need to provide remote support for macs is Remotely (https://github.com/immense/Remotely). You can selfhost it and it works kind of like teamviewer, so pretty simple from the client standpoint.
So I think the way I would want to do this is with something like mailpiler (https://www.mailpiler.org/). It’s been on my long list of things to dive into for a while.
To amplify RedWeasel’s very good answer, fstab runs as root and unless you specify otherwise, the share will mount with root as the owner on the local machine. From the perspective of the Samba server, it’s the Jellyfin user accessing the files, but on the local machine, but local permissions come into play as well. That’s why you can get at the files when you connect to the share from Dolphin in your KDE system—it’s your own user that’s mounting the share locally.
I’ve not done much with podman, but my first thought is that port 53 is privileged and usually podman runs as a non-privileged user, right? Do you have some mechanism in place that would allow podman to use port 53?
I’m a big fan of TrueNAS and Proxmox and I think OMV will be great for you.
In the order you asked:
- I think OMV is a decent choice, but there isn’t really a bad choice, just better fits for personal tastes.
- The upside compared to vanilla Debian or Ubuntu is a solid web-UI for management (though you could get that in the form of Cockpit) and a complete system philosophy. The downside is less flexibility. Any system someone else makes locks you into doing things their way.
- If you don’t have a desire to run VMs or set up clusters, or have by-default ZFS on root, you won’t be missing anything.
I haven’t seen any deleterious effects from what you’re proposing and I haven’t heard of any either. Were it me, I’d go for it.
You can set maintenance schedules in Uptime Kuma and alerts won’t be sent out during those times. I use that for when my backup routines run each night. That seems like a decent cross-platform work around.
I haven’t noticed anyone else bring it up, but you mentioned in passing the possibility of using a RAID 0. I’d avoid that except in very specific circumstances. They’re potentially fine for a scratch disk type of scenario, but if any member of the array fails, the whole array is toast. The chances of a failure increases with was each disk added, so a RAID 0 is less reliable than a single disk. I definitely wouldn’t want to trust my family’s photos to it.
My go-to for this is a plain Debian or Ubuntu container with Cockpit and the 45Drives file sharing plugin. It’s pretty straightforward and works pretty well.
Hey, as others have said, you can definitely set up OPNSense in a VM and it works great. I wanted to take a second and answer the first part of your question: it cannot run in Docker. Containers in Docker share their kernel with the Linux host machine. Since OPNSense isn’t a Linux distribution (it’s based on FreeBSD), it can’t make use of the shared Linux kernel.