A sandbox platform that runs agent and user code in isolated Firecracker microVMs, controlled through an HTTP API.
losfair/bake
A Linux CLI that embeds a Firecracker microVM (binary, kernel, initrd, rootfs) into a single executable that runs a container inside a VM.
- Stars
- 483
- Forks
- 19
- Open issues
- 1
- Last commit
- 9 months ago
What is it?
bake packages a Firecracker microVM, including the firecracker binary, kernel, initrd and a root filesystem image, into a standalone ELF executable. Running that file boots a microVM and launches the container entrypoint inside it, so the output can be distributed and run like an ordinary binary.
The tool also provides host-guest communication without root privileges. Networking is bridged over vsock through a SOCKS5 proxy and a UDP bridge, with an optional allowlist for outbound IPv4 addresses. Directories can be shared into the VM over 9p, and host TCP ports can be forwarded into the guest with -p. A WireGuard config can be supplied for guest connectivity.
The built binary also includes an ssh subcommand that connects to a running instance, and a systemd subcommand that prints a service unit. An optional init script can run pre-flight checks before the VM starts.
Key features
- 01Embeds firecracker, kernel, initrd and rootfs into one executable.
- 02Runs without root privileges, with networking handled in userspace over vsock.
- 03Restricts outbound access with an IPv4/CIDR allowlist.
- 04Shares host directories into the VM via 9p and forwards host TCP ports.
- 05Connects to running instances with a built-in ssh subcommand.
Use cases
- Distributing a containerized application as a single binary that runs in an isolated microVM.
- Running untrusted or sandboxed workloads on Linux hosts without root.
- Packaging a service with a WireGuard tunnel for controlled network access.
Topics
FAQ
- What is bake?
- A Linux CLI that embeds a Firecracker microVM (binary, kernel, initrd, rootfs) into a single executable that runs a container inside a VM. bake packages a Firecracker microVM, including the firecracker binary, kernel, initrd and a root filesystem image, into a standalone ELF executable. Running that file boots a microVM and launches the container entrypoint inside it, so the output can be distributed and run like an ordinary binary.
- Is bake free to use? What license does it have?
- bake is open source under the MIT license. Check the license terms before using it in commercial products.
- Is bake still maintained?
- No commits for 6+ months. The last commit to bake was on Feb 2, 2026.
- What can I use bake for?
- Distributing a containerized application as a single binary that runs in an isolated microVM. Running untrusted or sandboxed workloads on Linux hosts without root. Packaging a service with a WireGuard tunnel for controlled network access.
- Where can I get bake?
- The source code and installation instructions are on GitHub: https://github.com/losfair/bake
Summary generated by AI from the project's README. GitHub stats refresh daily.
Related projects
Zero-trust sandboxed runtime on Kubernetes for running large numbers of untrusted, mostly-idle AI agents with snapshot-based suspend and resume.
Self-hosted infrastructure that runs untrusted code in lightweight VM sandboxes, managed through a CLI, HTTP API and Python SDK.
A safe, private runtime that sandboxes autonomous AI agents, enforcing declared policies on files, system calls, and network access.
A terminal UI (TUI) for viewing and controlling Docker containers, with live stats, logs, and container actions.
Self-hosted, Cloudflare Workers-compatible platform that runs as one Rust binary on a single machine.