Live data from Hacker News

LXD is now under Canonical

linuxcontainers.org

91–100 of 224 posts

Re: LXD is now under Canonical

#91
post #61
post #52

Earlier quoted context omitted.

LXD isn't an alternative to podman. Podman is meant to run 'application containers', where each container has just one running process. LXD is meant to run 'system containers' where each container is a full Linux distribution with an init system and (possibly) multiple daemons. LXD containers are like light-weight VMs. Unlike VMs, LXD containers share the host kernel. You could run podman or other OCI containers insi…

I gotta try multi node k8s setup for lxd

There are a few settings to figure out before LXD containers can host K8s. It's mainly about running the LXD containers in privileged mode. I have the settings written down somewhere. I think I should publish it somewhere, considering the expressed interest in it.

Re: LXD is now under Canonical

#92
post #80

Earlier quoted context omitted.

Where are you pulling these definitions/differences from?

https://ubuntu.com/blog/what-are-linux-containers I have used both lxd and podman.

I haven't read much about lxd until just now but based on that link, the differentiating feature between lxd and podman seems to be that lxd can manage full virtual machines (using qemu as backend, according to [1] which was linked elsewhere in this thread). Whatever this distinction is between application and system container, it doesn't appear to be a technical distinction nor a feature that lxd has that podman lacks, unless I'm wildly misunderstanding it. Containers you run with docker and podman are fully capable of running multiple processes (in my experience it's quite common to do so) and Red Hat has blog posts from years ago specifically discussing running systemd in podman, eg [2]. Managing VMs is indeed an additional feature though.

[1] https://ubuntu.com/blog/lxd-virtual-machines-an-overview

[2] https://developers.redhat.com/blog/2019/04/24/how-to-run-sys...

Re: LXD is now under Canonical

#93
post #28

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.

Yeah I'm setting up a Debian 12 Bookworm machine right now after ~13 years of being an Ubuntu user So far it's very snappy! My Ubuntu 18.04 machine somehow "rotted" in ways that previous installs didn't -- everything became slow and janky, sorta like Windows And I specifically installed 18.04 in 2021, to avoid Snaps But now it looks like Debian will work great

I switched to Debian 11 for the same reasons around Christmas. I also found out faster than Ubuntu 20.04 and the fan starts spinning less often. I've been on Ubuntu since 8.04.

When I can I'm creating servers with Debian too, personal ones and for customers. The only problem there is that Letsencrypt uses a snap to update the certificates, even on Debian [1]. Not all my servers need a web server but when they do I usually use ngnix. I'm investigating alternative update clients with no hurry. When that is solved, goodbye to Ubuntu.

[1] https://certbot.eff.org/instructions?ws=nginx&os=debianbuste...

Re: LXD is now under Canonical

#94
post #52

Earlier quoted context omitted.

LXD isn't an alternative to podman. Podman is meant to run 'application containers', where each container has just one running process. LXD is meant to run 'system containers' where each container is a full Linux distribution with an init system and (possibly) multiple daemons. LXD containers are like light-weight VMs. Unlike VMs, LXD containers share the host kernel. You could run podman or other OCI containers insi…

How can I run podman inside LXD? Last time I tried exactly that didn't work.

Vanilla LXD containers can't run podman inside them. You need privileged LXD containers. There were quite a few settings I had to figure out before I could get K3s to run on it. I'm considering publishing an article about it.

Re: LXD is now under Canonical

#95

Ubuntu is already the major contributor to LXD. What's peoples aversion to snaps in the thread? For me it makes for a stable system that allows me to run the latest version of apps in a confined space, it's actually perfect

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.

Re: LXD is now under Canonical

#96
post #80

Earlier quoted context omitted.

https://ubuntu.com/blog/what-are-linux-containers I have used both lxd and podman.

I haven't read much about lxd until just now but based on that link, the differentiating feature between lxd and podman seems to be that lxd can manage full virtual machines (using qemu as backend, according to [1] which was linked elsewhere in this thread). Whatever this distinction is between application and system container, it doesn't appear to be a technical distinction nor a feature that lxd has that podman lac…

> the differentiating feature between lxd and podman seems to be that lxd can manage full virtual machines

LXD is a management layer over LXC and Qemu(KVM?). LXC is all about system containers. The Qemu support is a recent addition [1]. LXD supported only LXC system containers until then.

> Containers you run with docker and podman are fully capable of running multiple processes

Yes. I have done this. But it was very unwieldy - probably because docker, podman etc weren't designed to run system containers.

[1] https://ubuntu.com/blog/lxd-virtual-machines-an-overview

Re: LXD is now under Canonical

#97

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.

The first think I always do after a fresh Ubuntu installation is removing snap entirely. Works fine in 20.04.

Re: LXD is now under Canonical

#98

Ubuntu is already the major contributor to LXD. What's peoples aversion to snaps in the thread? For me it makes for a stable system that allows me to run the latest version of apps in a confined space, it's actually perfect

Yeah, I don’t understand the hate in HN. Both snap and LXD are good container technologies. Snap is better than flatpak in several ways, for example, system programs could be confined too.

Re: LXD is now under Canonical

#99

Very 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…

If it gets us closer to being able to run native Office and Directx apps on Linux I'm all for it. Snap enforcement already scared me away from Ubuntu for the most part anyway.

Microsoft already has WSL2 so they can already run Office and Directx on the same box running Linux. I'm not sure that they have an incentive to make people run Office natively on a real Linux desktop. Wouldn't that lose some Windows customer? I think Office 365 already runs in browsers also on Linux but I never had a reason to check.

Re: LXD is now under Canonical

#100
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
Post reply on HN