#microvm
Wiki 6
- Matryoshka Isolation (Containers Inside VMs) The defense-in-depth pattern where each isolation layer trusts only the layer below — host kernel, VMM, guest kernel, container runtime, untrusted code
- QEMU microvm machine type QEMU's stripped-down x86 machine type — no PCI, no ACPI, virtio-mmio only, qboot firmware, direct kernel boot, triple-fault shutdown
- Rivet Blog rivet.dev — engineering writeups from the team behind the Sandbox Agent SDK, focused on agent sandboxing and microVM infrastructure
- Spindle — QEMU microVM CI engine for Tangled Tangled's self-hostable CI runner gains a QEMU-microVM engine — per-workflow VMs, NixOS-from-YAML config, a vsock guest agent, and two-way Nix caching
- We Reverse-Engineered Docker Sandbox's Undocumented MicroVM API Rivet's writeup of the undocumented `/vm` HTTP API in Docker's sandboxd daemon, what it gives you, and the Sandbox Agent SDK they built on top
- Your Container Is Not a Sandbox — MicroVM Isolation in 2026 Emir Beganović's KubeCon-EU-2026 readout on the microVM ecosystem and why agentic AI is becoming microVMs' "Docker moment"
Toolbox 3
- pullrun Runs one OCI image as a runc container, a Firecracker microVM, or an Apple Silicon VM off a content-addressed DAG store
- pve-microvm Debian package that adds sub-second-booting QEMU microvm guests to Proxmox VE
- Sandbox Agent SDK TypeScript SDK for running coding agents inside Docker's microVM sandboxes under one interface