This is the worse

>The LXD section on the LinuxContainers community forum will slowly be sunset in favor of the Ubuntu Discourse forum run by Canonical

A lot of useful lxd information are in forum.Stephane and the team is super helpful there.

Also snap auto update kills my containers so I had to put on held.

They also had just fixed a long standing bug that makes rebooting lxd container sometimes fails due to snap messing up with zfs mounts.

To this day about 90% of discourse links I click do not load. Seems to be some adversarial interaction with uBlock origin. As usual Canonical is on the wrong side of history.

I wonder, I don't remember the case like yours - I see LXD updates, but VEs (virtual environments) are kept running fine

Have you tried nixos? Its a totally different paradigm and definitely an acquired taste, but I used gentoo for ~2 years, then used Arch for ~5 and now am switching everything to nixos.

Main benefits is setting up a new machine is much easier, and updates are easier because almost all the normal configuration is managed by nixos (in the nix language) as opposed to regular files floating around etc.

Me too. Turns out alpine is better for server vms for my use case and cachyos is better for desktop for my use case as wrll (at least possibly until i figure out nixos)

I recently transitioned on the desktop from Debian then-testing to Alpine edge. I switched for a newer kernel (4.9 to 6.1 for recent fixes to busted microcode -- little annoyances around charging and the touchpad) but I like a lot of things about it: quick install, up-to-date repos, easy-to-understand init, battery lasts longer...

While at it, have you tried Void Linux? Sort of lightweight like Alpine, but much more convenient as a daily driver.

Do you use alpine for the host os as well as the vms? Been concerned that musl would prove a handicap.

Also, can confirm void is amazing on the desktop.

Can confirm alpine works fine as a libvirtd/kvm/qemu hypervisor, fwiw.

The one gotcha to be aware of here is that libvirtd as of now has two ways to be operated: Either run just the monolithic libvirtd service, or individual subsystems like virtstoraged. Trying to do both at the same time will cause issues.

Due to the limitations of OpenRC compared to systemd for interdependent and interoperating system services like this, I stuck with the monolthic libvirtd approach and it's been running fine so far.

https://libvirt.org/daemons.html#architectural-options

Oh yeah, I hated that when systemd would kill (restart) my libvirtd daemon (and my various VMs/containers whenever I adjusted my systemd-controlled nftable.

Monolithic libvirtd (which is disabling the systemd libvirt) is the way to go.

Nice, thanks. Though I was going to try using Xen on there, rather than kvm - any experience/thoughts on that?

Nope, but I'd be keen to learn of your results.

I was also aiming for Xen initially. However, my host just crashed (can't recall the exact dump) when I tried running a Xen kernel - Alpine or not. I never confirmed if it's due to the Intel N5105 lacking the proper CPU extensions to support Xen or if I could hope to hassle the machine vendor for a firmware update to get it working.

Ha, sounds good. If I remember to I'll necropost ya when I work on it. Otherwise you may see me begging for help on the alpine IRC.

I would expect musl to be less of a problem for the host than guests, though, since a VM/container host only needs to run packaged software from the distro's official repos (mostly libvirt/docker, probably). What problem would you expect to hit?

no, proxmox is too good not to use. That runs on the bare metal and then the vms are all alpine at this point.

I'm also a big fan of alpine on the server.