firecracker-containerd
github.com
- Free plan
- Linux
- Self-hosted
What firecracker-containerd is
firecracker-containerd lets containerd manage containers as Firecracker microVMs, adding isolation through the KVM hypervisor. The project describes uses such as sandboxing untrusted third-party containers and placing different workloads on multi-tenant hosts. It follows OCI image format where possible. Its components include a control plugin and API, an out-of-process shim runtime, an agent inside each microVM and a root filesystem image builder. The in-VM agent invokes runC through containerd-shim-runc-v1 to create Linux containers. Networking supports pre-created tap devices or tap devices created by CNI plugins, including bridge, ptp, host-local, firewall and tc-redirect-tap. The software is free under Apache 2.0. Hosts need 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 calls the project very early-stage and warns multi-tenant use is at the user's own risk.
Who it suits
It suits Linux operators exploring virtualized container isolation on Intel x86_64 hosts with KVM.
Good to know, and what to watch
- Adds Firecracker microVM isolation to containerd
- Uses OCI image format where possible
- Supports several CNI networking plugins
- Licensed under Apache 2.0
- Free plan
- Requires Linux 4.14 or later and KVM
- Intel x86_64 required; AMD and Arm unsupported
- Project is described as very early
- Multi-tenant use is at user's own risk
Plans
Every plan and pricefirecracker-containerd
Free plan
The verdict
firecracker-containerd provides a containerd-to-microVM path with defined networking and build components. Its host restrictions and early maturity make evaluation and careful deployment important.
What the maker publishes
- Build prerequisites
- The guide lists git, gcc, Docker CE, and Go 1.23 or later as prerequisites. source
- Components
- The repository includes a control plugin and API, an out-of-process shim runtime, an agent that runs inside the microVM, and a root filesystem image builder. source
- Container compatibility
- The project uses container standards such as the OCI image format where possible. source
- Container runtime
- The in-VM agent invokes runC through containerd's containerd-shim-runc-v1 to create Linux containers inside the microVM. source
- Host requirements
- The getting-started guide requires Linux 4.14 or later, an Intel x86_64 processor, and KVM; it says AMD and Arm are not yet supported by this project. source
- Integrations
- The getting-started guide describes CNI plugins including bridge, ptp, host-local, firewall, and tc-redirect-tap. source
- Isolation
- Firecracker microVMs can provide an additional layer of isolation through the KVM hypervisor. source
- License
- The project is licensed under Apache 2.0. source
- Networking
- Networking supports pre-created tap devices and tap devices created automatically by CNI plugins. source
- Production networking
- The guide says production deployments should choose network configuration suited to their environment and workloads, with attention to network isolation between tasks. source
- Project maturity
- The getting-started guide describes the project as being in a very early state and says it is not yet as plug-and-play as desired. source
- Purpose
- firecracker-containerd enables containerd to manage containers as Firecracker microVMs. source
- Security caveat
- The repository states that multi-tenant use cases are at the user's own risk. source
- Support
- The README directs bug reports, roadmap discussion, and feature requests to GitHub Issues, and general discussion to the Firecracker Slack #containerd channel. source
- Use cases
- The project describes sandboxing untrusted third-party containers and bin-packing disparate workloads on multi-tenant hosts as potential use cases. source
Checked against the maker's pages on 4 Oct 2026.