Again, pardon my ignorance when it comes to Kubernetes. Why would I use something like k0s instead of just regular old Docker? I suspect PCIe passthrough will have similar challenges on both k0s and Docker, whereas on Proxmox it's been relatively painless.
This might be better suited for a different community, in which case I'll make a post where appropriate. I'm not familiar with some of the Kubernetes terminology - batteries, pod/manifest (is this similar to stacks/docker compose?), NodePort?
I apologize for my ignorance when it comes to Kubernetes - I sort of wrote it off as complete overkill for a home lab when my very basic understanding was that it was essentially a load balancer. After some light research, I'm beginning to understand that it could be a better solution than a full-blown hypervisor.
If I understand your comment correctly, you're suggesting to simply run a lightweight distro and install k0s or k3s to run containers? What would be an ideal bare metal OS for this? What would be pros/cons to k0s vs k3s in a home lab environment, or is that simply a matter of personal preference? What would be the best way to connect to my media - SMB, NFS, something else? Or are the differences here irrelevant? Any concerns (permissions, IO latency) when passing an NFS mount from host into a container, or is there an even better way to do something like that entirely within the container?
The Fn and Carl keys can be switched in software. I have a work-issued Lenovo with a similar layout. They can be soft-swapped in the BIOS. There’s also a desktop utility to do the same but I don’t know if they have a Linux version of it. I totally agree, the physical layout is annoying but it has a simple fix.
Yep, I understand that. I didn’t know if RAID 6, having parity bits, would be able to repair a file from that data. I figured being RAID would protect it from corruption but apparently not. I didn’t overwrite the file with a bad one, it just stopped working.