I was wondering about that odd "I am leaving #Canonical" blogpost by @stgraber some months ago and with this talk it all makes sense: relicensing and kicking out the community of #lxd is pretty hostile and caused the inevitable immediate fork as #incus .
And so it begins... Canonical just merged a pull request into #LXD including 3 of my changes from #Incus with me clearly listed as the author despite me having specifically declined to sign the CLA that's supposedly required for all contributions to their project... https://github.com/canonical/lxd/pull/12709
My preferred containerization solution when I'm not using FreeBSD: LXC/LXD on Alpine Linux.
Back in 2020, I documented the (easy) installation and usage procedure of LXC on Alpine Linux in their wiki: https://wiki.alpinelinux.org/wiki/LXD
"'"[…] Canonical re-licensed LXD […] Because LinuxContainers community can't lean on to LXD, they've decided not to build and publish LXD images anymore. Non-LTS LXD will gradually start losing access to these images immediately in 2024, while LTS LXD is allowed until ~April-May of 2024 to have a fair chance migrating into #Incus LTS, which is expected to be out in April 2024. […]"'"
Just migrated my last #LXD cluster over to #incus!
This was the scariest one as that's the production cluster running my BGP routers and all the Linux Containers infrastructure, but lxd-to-incus took care of it and 20min later everything was back online!
I struggled to pick #terraform to create the new networks. Not because of the bullshit they be pushing but, I needed to create a 3 new #lxd#networks and this would be the only time.. I hope I'll be doing this . I coded!
In good news because I spent so much time on the #wiregaurd#overlay#network. Moving my instances from one network to another was a breeze! what happen underneath didn't even register!
This is a blog post version of a talk I presented at both Ubuntu Summit 2022 and SouthEast LinuxFest 2023. I cover why one might want to use VMs, application containers, or system containers, I talk specifics about VM hypervisor types, how application and system containers work, and when I think it's appropriate to use each technology.
When a (VC backed) Open Source project demands from you, a community member, to sign a CLA (Contributory License Agreement) that forces you to give up your rights on your code - RUN. #Hashicorp et all who unfortunately, really sorry, kudos, love you switch their licenses to proprietary whenever they feel like it.
@jwildeboer indeed, this was the problem canonical ran projects under CLA's had posed, and still poses. Speaking of which, I see that there is a fork of #lxd and something similar should be done to #HashiCorp projects worth saving.
Linux Containers - Incus - Introduction (linuxcontainers.org)
The Linux Containers project has announced the addition of Incus, which is a fork of LXD 5.16 started by Aleksa Sarai.