Live data from Hacker News

LXD is now under Canonical

linuxcontainers.org

221–224 of 224 posts

Re: LXD is now under Canonical

#221
post #177

Sté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.

I agree. Snap is the weak point of LXD. I have been using it in production servers and until snap refresh --hold was made available my team went through the pains of snap workarounds [1] The LXD team was very proactive in the support side but the truth is that Snap is a pain and without --hold it would be possible for production servers to break out of a sudden due to uncontrolled updates (who did every think that th…

I'd like to hear more about your experience on joining Puppet and LXD, mind to share?

Re: LXD is now under Canonical

#222
post #55

Earlier quoted context omitted.

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.

This is the worse >The LXD section on the LinuxContainers community forum will slowly be sunset in favor of the Ubuntu Discourse forum run by Canonical A lot of useful lxd information are in forum.Stephane and the team is super helpful there. Also snap auto update kills my containers so I had to put on held. They also had just fixed a long standing bug that makes rebooting lxd container sometimes fails due to snap me…

I wonder, I don't remember the case like yours - I see LXD updates, but VEs (virtual environments) are kept running fine

Re: LXD is now under Canonical

#224
post #6
post #4

Earlier 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.

He no longer works for Canonical, it seems.
Post reply on HN