LXD now re-licensed and under a CLA

woelkchen@lemmy.world to Linux@lemmy.ml – 45 points –
stgraber.org

Blog post from LXC's project lead

30

Thank heavens for Incus.

The issue here is that this will stall the development of LXD/Incus. Two separate projects running in different directions no future feature parity and potentially less features in Incus than in LXD.

Currently LXC Incus is more active than Canonical LXD.

But it may never see much progress on the WebUI for instance while Canonical has paying customers pushing and asking for it. They may appear inactive and it seems there aren't many people working on the project but who knows? Maybe they're setting up their own image server, repacking images etc.

Again, I'm all in favor of this change and I've a couple of systems running on both and will obviously migrate everything to Incus but I can't ignore the fact that enterprise money pushes Canonical todevelop things.

I just see a problem here:

I perfectly understand, approve and back this move, however I’ve a question about the current state of things and specifically Debian 12 users. Debian includes LXD LTS 5.0.2 on their repositories and that version will be still be around after 2024/05 and trying to use the image server. Debian won’t likely change stable to include Incus until 2025, what’s the suggested path here?

https://discuss.linuxcontainers.org/t/important-notice-for-lxd-users-image-server/18479/9

Do people actually use LXD in production? All hosting services I've seen use LXC and not LXD for containers, as do UIs like Proxmox and Unraid, and you don't have to use Snap for LXC.