Apple container vs firecracker-containerd

Apple container creates and runs Linux containers as lightweight virtual machines on a Mac. Written in Swift and optimized for Apple silicon, it gives each container its own lightweight virtual machine with core utilities and libraries. Host data is shared by mounting only the data needed inside each virtual machine. The tool consumes and produces OCI-compatible images that can be pulled from and pushed to standard registries. Documented features include CPU and memory limits, bind mounts, named volumes, tmpfs, DNS-based names, port forwarding, and isolated networks. It can run local single-node or multi-node Kubernetes clusters for development and testing, and documentation covers building, running, and publishing images for Apple silicon and x86-64. Integrations include macOS Virtualization, vmnet, XPC, launchd, Keychain services, and unified logging. Apple container is free, Apache-2.0 licensed, and supported on macOS 26, but requires Apple silicon. The project is under active development.

firecracker-containerd lets containerd manage containers as Firecracker microVMs, adding isolation through the KVM hypervisor. Potential uses include sandboxing untrusted third-party containers and bin-packing different workloads on multi-tenant hosts. It uses OCI image format where possible. The project includes a control plugin and API, an out-of-process shim runtime, an agent inside the microVM, and a root filesystem image builder. That agent invokes runC through containerd-shim-runc-v1 to create Linux containers inside the microVM. Networking supports pre-created tap devices and tap devices created by CNI plugins such as bridge, ptp, host-local, firewall, and tc-redirect-tap. The software is free under Apache 2.0. Hosts require Linux 4.14 or later, Intel x86_64, and KVM; AMD and Arm are not supported. Building requires git, gcc, Docker CE, and Go 1.23 or later. The guide describes the project as very early, and multi-tenant use is at the user’s own risk.