LXD is now under Canonical
LXD is now under Canonical
Interesting move by Canonical. Wonder if this is related to the new GUI for LXD that Canonical released recently? Or maybe they want to bring more projects in-house after the RHEL shakeup?
How do you notice that you are not really awake yet? By thinking for several minutes about what LXD has to do with containers and then realising that you yourself had LXDE in mind.
8huh, was it not before? i thought the entire lx* space was canonical's thing
5Was developed by Canonical, but under the Linux Containers umbrella.
3
Used it once or twice then stopped, prefer raw lxc or even just manually creating namespaces if I want control.
Never quite understood the point, the additional polish seemed fairly minimal from a utility pov.
They should take over proxmox or something, give themselves a complete story.
2I don't know if I want a project as cool as Proxmox owned by the "you will use snap and you will like it" Canonical
1The point is that you want management, easy ways to create images, backups, move container between hosts, orchestration, network management and sometimes not only container but also virtual machines. LXD does it all very well and if you don't want those resources you might as well use
systemd-nspawn.They've taken over Proxmox. Not sure if you're following but they have now a WebUI and the entire solution is magnitudes better than the crap Proxmox has been offering.
0I haven't been following, but that's actually good to hear, proxmox needs a better ui.
LXD, I suppose for the migration, but for any more complex orchestration I think you've moving to k8s or something more serious, LXD just has an odd "not enough but too much" feature set for me, I like things either push-button, or let me do it, this is kind of both.
1
I wonder if this means LXC (which seems neglected lately) and LXD will soon be maintained by different people.
2RIP LXD
1