Live data from Hacker News

LXD is now under Canonical

linuxcontainers.org

211–220 of 224 posts

Re: LXD is now under Canonical

#211
post #200

Earlier quoted context omitted.

> that terrible ubuntu GUI update to have a ribbon. Which one was that? No version of Ubuntu I've ever seen has ribbons. This is one of the reasons I like it. Do you mean when they switched from Unity to GNOME?

As I suspect that op meant that left sidebar that Ubuntu actually introduced with Unity. It was definitely ugly and unnecessary, especially with Amazon button on it by default (if I recall correctly).

Ah, could be, by the timing. The wording threw me off.

I loved Unity. I still use it today.

Re: LXD is now under Canonical

#212
post #127

Earlier quoted context omitted.

I suspect the thing people find offensive is that this is not the default

If the reason of snapping is that their preference isn't the default, life must be quite tough for them. If there's an option, live with it and change it. I can't see what's so destructive about snaps. It's probably another echo chamber when people find a common target to yell at.

> I can't see what's so destructive about snaps

The implementation is shit.

Things take 10 times as long to start.

There are annoying 'Turn off firefox so snap can update it' messages. Nothing happens when you stop firefox, you'll just get the same message a few hours later.

Shutdown is going to take ages for some reason because it's waiting for snap to do something.

I don't give two shits about whatever snap is trying to do, but having to wait 10 minutes for my workstation to be useful whenever I want to reboot is not what I'm about.

Re: LXD is now under Canonical

#213

Earlier quoted context omitted.

AFAIK, snaps don't have a (official) way of disabling auto updates which means everything run a snap might update at any time, rather than when the best time is. This might work fine for a personal computer you use for Facetime or whatever, but in a professional environment or for servers, you can't just let software update when it thinks it time to do it, you need to figure out a good opportunity for it to happen.

Yes they do: https://snapcraft.io/docs/keeping-snaps-up-to-date#heading--...

Ah, supported in 2.58+ which is the latest stable version, seems I'm up to date when it comes to my snap knowledge. Happy that it finally is supported, but not super happy about it taking ~7 years to get in place...

Re: LXD is now under Canonical

#214

Earlier quoted context omitted.

You've been able to specifically schedule refresh times and interval's for awhile now. We did it monthly at a specific time and then set a calendar event with a couple notifications to keep track of it. IMO the "I can't turn off the updates" concern is overblown. If you aren't patching your systems ever you have problems anyways.

Overblown? Tell that to people that were hit with production outages. The whole idea of automatic updates for software running critical workloads is so stupid that I lost all respect for Canonical as a vendor.

The problem with auto updates for daemons and services is that the maintainer cannot possibly account for all the different ways their software is used to be able to guarantee that the new version doesn’t break some critical service. It’s akin to a team outsourcing their CI/CD pipeline to some 3rd party who have no idea they exist!

Re: LXD is now under Canonical

#215
post #75

Earlier quoted context omitted.

> Ubuntu powers the overwhelming majority of Azure workloads I expect this to shift. Some years ago `FROM ubuntu:something` was a go-to for Dockerfiles when I wasn't feeling fancy with `FROM alpine` or `FROM busybox` (or `FROM scratch`). Today if I need a generic distro base, I'm consciously going with Debian-based images and Ubuntu is never an option anymore (it used to be "Debian, but better", it became "Debian, bu…

Ha, it's the reverse for me. I used to use Debian base image, but now switch to Ubuntu LTS base images almost exclusively due to them offering newer versions of most core libraries, and longer support duration.

> them offering newer versions of most core libraries

Is that actually true? Debian has managed pretty consistent 2 year release cadence, same as Ubuntu LTS, so based on that alone they should on average have similar library freshness. Basically Debian releases on odd years, Ubuntu LTS on even years. I suppose Debian might have slightly longer freeze periods.

Re: LXD is now under Canonical

#216

I hear a lot of people complaining about Snap. While I am not a Ubuntu user for 15+ years, I am curious why Canonical is pushing Snaps so much. There must be positive feedback from their target market. Maybe the traditional Linux desktop user does not fit anymore into Canonical’s persona

Canonical wants some corner of the ecosystem where they can say that they are driving the progress instead of being just downstream consumers and (re-)packagers.

And to be honest, Snaps had fair chance of succeeding; when they first were released flatpak was still pretty young. Docker has had its own issues, and podman (etc) is even younger yet. If they played their cards right Snap could have been Canonicals chance to shine, and I guess they know it and are still trying to salvage the effort.

Re: LXD is now under Canonical

#218
post #6

Earlier quoted context omitted.

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

> Docker / kubernetes is eating it up 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…

Hey, I'm looking for a Proxmox alternative!

But how do I use LXD on Debian without Snap?

Re: LXD is now under Canonical

#219

> Canonical, the creator and main contributor of the LXD project has decided that after over 8 years as part of the Linux Containers community, the project would now be better served directly under Canonical’s own set of projects. > While the team behind Linux Containers regrets that decision and will be missing LXD as one of its projects, it does respect Canonical’s decision and is now in the process of moving the p…

AFAIK, Canonical funds most of the development and has always been leading it.

Re: LXD is now under Canonical

#220

> Canonical, the creator and main contributor of the LXD project has decided that after over 8 years as part of the Linux Containers community, the project would now be better served directly under Canonical’s own set of projects. > While the team behind Linux Containers regrets that decision and will be missing LXD as one of its projects, it does respect Canonical’s decision and is now in the process of moving the p…

When your employer and the owner of the intellectual property you are employed to work on decide to move that intellectual property to a different server, you either acquiesce or you look for another job doing something else. You have to ask yourself if it's the hill you're willing to die on, and only a few are privileged enough to choose a life of full-time leisure.
Post reply on HN