containerd vs LXC

containerd is a free container runtime for managing a host’s container lifecycle. It handles image transfer and storage, execution, and supervision, and is designed to be embedded in a larger system rather than used directly by developers or end users. It supports OCI images and image push and pull operations, and uses runc by default while allowing other OCI-compliant runtimes. Its built-in CRI plugin can make it the container runtime for a Kubernetes cluster, and it supports registries compliant with the OCI Distribution Specification. The daemon is available for Linux and Windows. Network-interface management and image building are outside containerd’s first-class scope, so higher-level systems or tools handle those jobs. Its ctr command-line tool is intended for development and debugging, without a guarantee of a stable interface or a human-friendly experience. Users typically also need runc and CNI plugins. The plan is free; free plan available, with no free trial.

LXC is free software for creating and managing Linux system or application containers through Linux kernel containment features. It aims to make each container resemble a standard Linux installation without a separate kernel. The project includes the liblxc library, container control tools, distribution templates and API bindings for Python 3, Lua, Go, Ruby and Haskell. Process containment uses kernel namespaces, AppArmor and SELinux profiles, seccomp policies, chroots, kernel capabilities and cgroups. Unprivileged containers map container root to an unprivileged host user. LXC is included in most Linux distributions and is generally installed through the distribution package manager. Listed requirements include a supported C library and Linux kernel 2.6.32 or later. LXC 7.0 and 6.0 are listed as long-term support releases through June 1, 2031 and June 1, 2029. Most code uses GNU LGPLv2.1+, with some BSD 2-clause or GNU GPLv2 components.