LXD is now under Canonical
11–20 of 224 posts
Re: LXD is now under Canonical
#12Earlier quoted context omitted.
The point of them owning LXD is to give them total control of the underlying technology they are using for Snaps. Snaps is the play… has nothing to do with kube/docker. It’s actually more of a synonym of ostree and flatpaks.
Snap is not built on top of lxd.
Re: LXD is now under Canonical
#13Stéphane Graber's work is fantastic and LXD had a lot of potential. But Canonical managed to drive me away from it with that abomination called Snap and its auto updates that could bring down a cluster without warning.
Re: LXD is now under Canonical
#14Re: LXD is now under Canonical
#15Stéphane Graber's work is fantastic and LXD had a lot of potential. But Canonical managed to drive me away from it with that abomination called Snap and its auto updates that could bring down a cluster without warning.
Re: LXD is now under Canonical
#16Stéphane Graber's work is fantastic and LXD had a lot of potential. But Canonical managed to drive me away from it with that abomination called Snap and its auto updates that could bring down a cluster without warning.
Re: LXD is now under Canonical
#17* Ubuntu powers the overwhelming majority of Azure workloads (both customer and internal)
* Nearly all Linux applications and tooling target Ubuntu first (or at the very least)
* Github, VSCode. The missing piece is the actual runtime operating system. Ubuntu.
* Canonical employs nearly all the remaining core enterprise open-source developers after IBM acquired Red Hat
Start the countdown to Microsoft Ubuntu.
Re: LXD is now under Canonical
#18Earlier quoted context omitted.
Woah I notice that the signatures on that include Stéphane Graber. It's rather hard to imagine LXD continuing as a going concern without him. Does this mean he regrets the decision, but is going to keep working on LXD, or... does this mean LXD is fucked? -- concerned LXD user
> does this mean LXD is fucked It is either way. Docker / kubernetes is eating it up. There aren't as many LXD users as they'd hope. Oh and he does work for Canonical.
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 of Proxmox alternative (because you can manage LXC containers and VMs with it) instead of a Docker/Kubernetes alternative. In fact, I actually have migrated my systems from Proxmox to Ubuntu Server with Docker, for stateless applications, and LXD, for when I need to containerize an entire OS or VMs for my friends.
Re: LXD is now under Canonical
#19Very soon Microsoft will acquire Canonical for at least $40 billion. The reasons: * Ubuntu powers the overwhelming majority of Azure workloads (both customer and internal) * Nearly all Linux applications and tooling target Ubuntu first (or at the very least) * Github, VSCode. The missing piece is the actual runtime operating system. Ubuntu. * Canonical employs nearly all the remaining core enterprise open-source deve…
Re: LXD is now under Canonical
#20Stéphane Graber's work is fantastic and LXD had a lot of potential. But Canonical managed to drive me away from it with that abomination called Snap and its auto updates that could bring down a cluster without warning.
Moved completely off ubuntu after snaps were introduced. Sticking with gentoo now because it’s one of a few distros that doesn’t try to control what software you have to use.