Using Proxmox with lxc containers, there is no second kernel. It uses the host kernel’s native cgroups and namespaces for process isolation. You can actually achieve the same with just systems and namespaces.
Having said that, I think if you prefer traditional distro packaging, you should absolutely stick to that.
I'm aware of the tradeoffs here. For home assistant specifically, there's two options if you want to stay on the path of first-class support. Run it bare metal or in a VM.
Going a different path isn't a bad choice, or even a big downgrade.
I had fun with all the different ways of running home assistant 6+ years ago, and then decided to embrace a solution that required the least fuss and would hold up long term. I'm happy with my choice, and it gave me exactly what I was expecting.
I'm also running dozens of things alongside HA and I don't have to use proxmox.
It's not hard to run HA in unsupported mode. The only real difference is an annoying reminder that you're unsupported. Everything else works, including plugins/add-ons.
I've run HA a bunch of ways. It doesn't really matter all that much. Use HACS to fill any gaps.
One-click updates work from the dashboard? I don't think they would.
Of course you don't have to go the proxmox route, but it is an easy route.
I have a proxmox cluster, so moving things between machines, high availability, and backups are a breeze. Had an SSD go bad a few months ago, and I just moved everything on that machine to another node until the new drive showed up. It was a pleasant experience.
There's plenty of other ways to achieve this, but this is what I chose and I'm happy with it. It's simple, and I can manage everything from my phone if needed.
Yes, one click updates work just fine. The only difference is the unsupported message which only appears after reboots or an update. Click ignore and it goes away.
The OS is the path of least resistance and gives you the best experience for low maintenance.
https://community-scripts.github.io/ProxmoxVE/scripts?id=hao...