Firecracker microVM backend on Linux hosts with KVM

Open
#64 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, kubernetes, linux, rust

Research direction

Start by reading design §7.2 and the related issues #8, #29, #37, #41, #48, and #63 to understand the sandbox and placement interfaces and acceptance flows. The issue calls for a Firecracker backend, snapshot-based warm pools and parking, networking modes, and a Cloud Hypervisor fallback, but does not name implementation files or tests. Done means KVM hosts run the acceptance flows in Firecracker microVMs, start from snapshots in under a second, and route network access only through wicket.

Written by the indexing model from the issue text.

Description

enhancement

Why. On Linux hosts with KVM (bare metal, or cloud instances with nested virtualization), microVMs are the strongest practical isolation tier: the workload's own kernel behind hardware virtualization, a tiny device model, full Linux compatibility, and fast restores from snapshots. gVisor stays the floor because it runs anywhere.

What.

  • A Firecracker backend behind the sandbox and placement interfaces (#37). Official jailer. Root filesystems built from the agent's OCI image.
  • No network device in mediated mode: wicket-entry's forwarders reach wicket's endpoints over vsock (host side bridged to the run's sockets), as on Macs (#48). filtered and direct use a virtio-net TAP with host-side nftables and NAT (#63).
  • Snapshots: warm pools restored from snapshots (with RNG reseeding), and parking with pause and resume (#8, #29).
  • Cloud Hypervisor where Firecracker lacks a device (GPU passthrough), behind the same interface.
  • Isolation tier vm, ranked above gvisor.

Done when. On a KVM host, boxes run as Firecracker microVMs, start in well under a second from a snapshot, pass the acceptance flows (#41), and reach the network only through wicket.

Refs. design §7.2; research 02, 07; #8, #29, #37, #48, #63.

Dominant language
Rust
Stars
0
Forks
0
Avg merge
1h 43m
Merged PRs (30d)
190

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from public/wicket

All issues in public/wicket

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.