firecracker-microvm /firecracker
Secure and fast microVMs for serverless computing.
★ 38,033⑂ 2,751👁 356⑃ 4,787● 1,541▤ 93
+12
日增长
+121
周增长
38,033
stars
2,751
forks
356
watchers
4,787
prs
1,541
issues
93
releases
README
Our mission is to enable secure, multi-tenant, minimal-overhead execution of
container and function workloads.
Read more about the Firecracker Charter here.
What is Firecracker?
Firecracker is an open source virtualization technology that is purpose-built
for creating and managing secure, multi-tenant container and function-based
services that provide serverless operational models. Firecracker runs workloads
in lightweight virtual machines, called microVMs, which combine the security and
isolation properties provided by hardware virtualization technology with the
speed and flexibility of containers.
Overview
The main component of Firecracker is a virtual machine monitor (VMM) that uses
the Linux Kernel Virtual Machine (KVM) to create and run microVMs. Firecracker
can also run a guest as a Nitro Sandbox,
isolated by the AWS Nitro System instead of KVM. Firecracker has a minimalist
design. It excludes unnecessary devices and guest-facing functionality to reduce
the memory footprint and attack surface area of each microVM. This improves
security, decreases the startup time, and increases hardware utilization.
Firecracker has also been integrated in container runtimes, for example
Kata Containers and
Flintlock.
Firecracker was developed at Amazon Web Services to accelerate the speed and
efficiency of services like AWS Lambda and
AWS Fargate. Firecracker is open sourced
under Apache version 2.0.
To read more about Firecracker, check out
firecracker-microvm.io.
Getting Started
To get started with Firecracker, download the latest
release binaries
or build it from source.
You can build Firecracker on any Unix/Linux system that has Docker running (we
use a development container) and bash installed, as follows:
bash
git clone https://github.com/firecracker-microvm/firecracker
cd firecracker
tools/devtool build
toolchain="$(uname -m)-unknown-linux-musl"
The Firecracker binary will be placed at
build/cargo_target/${toolchain}/debug/firecracker. For more information on
building, testing, and running Firecracker, go to the
quickstart guide.
The overall security of Firecracker microVMs, including the ability to meet the
criteria for safe multi-tenant computing, depends on a well configured Linux
host operating system. A configuration that we believe meets this bar is
included in the production host setup document.
Contributing
Firecracker is already running production workloads within AWS, but it's still
Day 1 on the journey guided by our mission. There's a lot more to
build and we welcome all contributions.
To contribute to Firecracker, check out the development setup section in the
getting started guide and then the Firecracker
contribution guidelines.
Releases
New Firecracker versions are released via the GitHub repository
releases page,
typically every two or three months. A history of changes is recorded in our
changelog.
The Firecracker release policy is detailed here.
Design
Firecracker's overall architecture is described in
tTop issues
#5744MicroVM hangs during SMP boot with ≥16 vCPUs on dual-socket NUMA hosts36 comments · 2026-03-09#1933[Network] Add support for MacVTap interfaces18 comments · 2020-05-28#4751[Feature Request] Move to OpenAPI / OAS 3.115 comments · 2024-08-27#1033Add documentation for VM dev machine(using free or open source software)14 comments · 2019-03-22#3161Use `clippy::as_conversions`13 comments · 2022-10-04#4709Allow Running `vmm` Unittests in Parallel12 comments · 2024-07-29#1601Firecracker doesn't close when running `poweroff` in the guest12 comments · 2020-02-12#2609[Feature Request] Hot-plug vCPUs11 comments · 2021-06-03
Discussions
#6438RFC: a community-supported best-effort tier for untestable-in-CI hardware, applied to Hygon (HygonGenuine) x86_64 support0 comments · 2026-11-13#6269`SharedMemfd` memory backend4 comments · 2026-10-13#6222Downstream fork with support for Hygon CPUs (HygonGenuine)1 comments · 2026-09-16#6024Hyper - distributed Firecracker microVM orchestrator written in Elixir0 comments · 2026-07-09#5781Is vsock just slow on Linux? (EDIT3: Fixed in Linux 7.1, 6.18.52 and 6.12.110)2 comments · 2026-03-22#5667How is networking usually configured at boot inside Firecracker microVMs?1 comments · 2026-01-25#5549Firecracker Balloon only deflating on OOM1 comments · 2025-12-01#5541Firecracker Extension for Apache CloudStack1 comments · 2025-11-27
Latest release
Firecracker v1.18.0 v1.18.0 2026-11-09Added - 6393: Added support for Nitro Sandboxes. Firecracker can now launch and manage isolated VMs that the Nitro Hypervisor carves out of the parent EC2 instance, as an alternative to KVM. Firecracker drives the Nitro Enclaves driver (/dev/nitro_enclaves) instead of /dev/kvm, and keeps its existing API, jailer and virtio device model. A sandbox is configured with the new PUT /enclave API, in confidential or direct mode. See the Nitro Sandboxes documentation.