Earlier quoted context omitted.
As a stepping stone out of Ubuntu, Pop_OS! has been pleasant and snap-free.
The thought of people going to Pop to escape snap has me crackling.
LXD is now under Canonical
101–110 of 224 posts
Re: LXD is now under Canonical
#102Earlier quoted context omitted.
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)
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.
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.
Re: LXD is now under Canonical
#103Earlier quoted context omitted.
How can I run podman inside LXD? Last time I tried exactly that didn't work.
Vanilla LXD containers can't run podman inside them. You need privileged LXD containers. There were quite a few settings I had to figure out before I could get K3s to run on it. I'm considering publishing an article about it.
Make sure to post the article on HN if it comes around, I'm sure it will be appreciated.
Re: LXD is now under Canonical
#104Earlier quoted context omitted.
Yeah I'm setting up a Debian 12 Bookworm machine right now after ~13 years of being an Ubuntu user So far it's very snappy! My Ubuntu 18.04 machine somehow "rotted" in ways that previous installs didn't -- everything became slow and janky, sorta like Windows And I specifically installed 18.04 in 2021, to avoid Snaps But now it looks like Debian will work great
I switched to Debian 11 for the same reasons around Christmas. I also found out faster than Ubuntu 20.04 and the fan starts spinning less often. I've been on Ubuntu since 8.04. When I can I'm creating servers with Debian too, personal ones and for customers. The only problem there is that Letsencrypt uses a snap to update the certificates, even on Debian [1]. Not all my servers need a web server but when they do I us…
Re: LXD is now under Canonical
#105Earlier quoted context omitted.
> Docker / kubernetes is eating it up Is LXD's purpose the same as Docker/Kubernetes? I use both LXD and Docker and to me they are tools that use the same technology (containerzation) but for different purposes. Docker is for stateless containers, used to containerize services. LXD is for stateful containers, used to containerize operating systems. LXD can also run VMs while Docker can't. I think about LXD as a sort…
Since Linux containers are just namespace tricks, a kind of glorified chroot, what does it mean that you run VMs from within containers? Sincerely curious'
Re: LXD is now under Canonical
#106Re: LXD is now under Canonical
#107Earlier quoted context omitted.
As a stepping stone out of Ubuntu, Pop_OS! has been pleasant and snap-free.
The thought of people going to Pop to escape snap has me crackling.
For those who don't get the reference: https://en.m.wikipedia.org/wiki/Snap,_Crackle_and_Pop
Re: LXD is now under Canonical
#108LXD is really great software. The majority of the contributions already come from canonical, so I doubt this will make much difference in the trajectory of the project. I will say that I prefer running LXD on NixOS hosts where it isn't packaged as a snap. Hopefully canonical doesn't somehow break that.
Why LXD over podman? I've found podman to be a pretty great docker lite.
The original idea behind LXD was to build packages in a system equivalent to your real system but without spamming your dpkg database and filesystem with all the required -dev files. The idea behind Docker (which podman is a better implementation of and extension to) was to be able to have three different versions of Apache ephemerally on your system to match the versions used by three different projects today.
Ultimately you can do both with either (and I generally use podman to build packages, as an example) but if you do that you aren't playing to the project's strengths.
Toolbox and distrobox are sort of middle grounds that do both of them well enough to be tolerable.
Re: LXD is now under Canonical
#109Earlier quoted context omitted.
Yeah I'm setting up a Debian 12 Bookworm machine right now after ~13 years of being an Ubuntu user So far it's very snappy! My Ubuntu 18.04 machine somehow "rotted" in ways that previous installs didn't -- everything became slow and janky, sorta like Windows And I specifically installed 18.04 in 2021, to avoid Snaps But now it looks like Debian will work great
I switched to Debian 11 for the same reasons around Christmas. I also found out faster than Ubuntu 20.04 and the fan starts spinning less often. I've been on Ubuntu since 8.04. When I can I'm creating servers with Debian too, personal ones and for customers. The only problem there is that Letsencrypt uses a snap to update the certificates, even on Debian [1]. Not all my servers need a web server but when they do I us…