Not really useless, it’s an extra layer of management (a good thing). The Proxmox system can be nearly static while giving you external level management of the OS that manages the containers.
I have a 3 server Proxmox cluster running various VMs doing different things. Some of those VMs are my container systems.
Besides, you can run containers directly on Proxmox itself.
I’ve never worked with buildpack, so that’s interesting
Sure, ZFS snapshots are dead simple and fast. But you’d need to ensure that each container and its volumes are created in each respective dataset.
And none of this is implying that it’s hard. The top comment was criticizing OP for using VMs instead of containers. Neither one is better than the other for all use cases.
I have a ton of VMs for various use cases, and some of those VMs are container/Docker hosts. Each tool where it works best.
Backups? I have an automatic job running every night.
It’s not the same. You then need to manage volumes separately from images, or if you’re mounting a host folder for the Jellyfin files then you have to manage those separately via the host.
Container images are supposed to be stateless. So then if you’re only banking up the volumes, then you need to somehow track which Jellyfin version it’s tied to, in case you run into any issues.
A VM is literally all of that but in a much more complete package.
I can backup an entire VM snapshot very quickly and then restore it in a matter of minutes. Everything from the system files, database, Jellyfin version and configs, etc. All easily backed up and restored in an easy to manage bundle.
A container is not as easy to manage in the same way.
My personal problem is that I’m so bad at using it
It’s not you, it’s just that Windows is badly designed.
Whenever I screw something up or something goes sideways. Or when I’m migrating from one host to another.