Firecracker microVM backend on Linux hosts with KVM
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
- Domain
- backend, infrastructure, security
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
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
mediatedmode: wicket-entry's forwarders reach wicket's endpoints over vsock (host side bridged to the run's sockets), as on Macs (#48).filteredanddirectuse 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 abovegvisor.
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from public/wicket
-
Don't break the machines: node health alerts, admission control, reserved headroom, volume lifecycle, collection trackingPossibly taken @public claimed this today. Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement parked
Difficulty 5/5 Over a week Newbie friendliness 12/100
public/wicket#371 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
Windowed egress caps and standard OTLP decision records (from AgentCore, Strands Box and Dogwood)Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 22/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yantrikos/yantrik-os#1272 ·
Maintainers usually reply within 1 day
-
crate: spate-kafka priority: low tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·