runc VS LXD

It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C) As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun), which is written in C as an alternative to runc, which is written in Go( - Source: Hacker News / 7 months ago

Yeah, runtimeClass lets you specify which CRI plugin you want based on what you have available. Here's an example from the containerd documentation - you could have one node that can run containers under standard runc, gvisor, kata containers, or WASM. Without runtimeClass, you'd need either some form of custom solution or four differently configured nodes to run those different runtimes. That's how krustlet did... Source: over 1 year ago

Your Docker Container can only run Linux. That's because Docker takes advantage of runC which uses the Linux kernel. You can't run Windows inside of Docker. But of course you can run Docker on a Windows host machine. If you are running a .NET project, you won't be able to use Docker. On the other hand, if you're running .NET Core then you're in luck! - Source: dev.to / over 1 year ago

This is what Podman, an open-source daemonless and rootless container engine, was developed with in mind. Podman runs using the runC container runtime process, directly on the Linux kernel, and launches containers and pods as child processes. In addition, it was developed for the Docker developer, with most commands and syntax seamlessly mirroring Docker's. Buildah, an image builder, and Skopeo, the image utility... - Source: dev.to / almost 2 years ago

If you are curious about how exactly Docker does this I urge to have a look at the following links on layered file system and the library runc and also this great wikipedia overview of Docker. - Source: dev.to / almost 2 years ago

Linux containers project. Foreshadowing of this move at https://linuxcontainers.org/lxd/. - Source: Hacker News / 5 months ago

The expected changes are: - https://github.com/lxc/lxd will now become https://github.com/canonical/lxd - https://linuxcontainers.org/lxd will disappear and be replaced with a mention directing users to https://ubuntu.com/lxd - The LXD YouTube channel will be handed over to the Canonical team - The LXD section on the LinuxContainers community forum will slowly Be sunset in favor of the Ubuntu Discourse forum... Source: 10 months ago

Hello community, It seems LXC images for arm7l/armhf are no longer available, not from the official Turris mirror nor from LinuxContainers.org (https://linuxcontainers.org/lxd/). Any solution or alternative for people like me heavily relying on the Turris Omnia to run LXC containers? Thanks. Source: 10 months ago

Any distribution stable enough and LXD https://linuxcontainers.org/lxd/ for containers and VMs. Source: about 1 year ago

This has been really stable, and has worked pretty well for me. I deploy the applications to a set of LXD containers (read: lightweight Linux VMs) on Proxmox, a free and open-source hypervisor with an excellent management interface. - Source: dev.to / about 2 years ago