Skip to main content
Status as of 2026-09-30. v0.1.0 is released. The release tracker is #56.

​
Scope

v0.1 deploys services to one server, for one trusted operator. Rootless Podman containers are the default runtime. MicroVMs (Cloud Hypervisor) are experimental but working: they accept the same Russelfile fields as containers and run under the same unprivileged control plane. v0.1 has no multi-user support, no agent sandboxes, and one server only.

​
What’s in v0.1

​
Tested

  • Formatting, clippy, and the full test suite pass on main.
  • CI deploys every container example against an unprivileged control plane and checks that each answers.
  • A local run with KVM deployed all 13 examples as microVMs.
  • A fresh-machine test of a release candidate found that containers didn’t start under the installed service. v0.1.0 includes the fix (Changelog).

​
Left for v0.1

​
Known gaps

  • #69: containers reject an entry point that is a relative symlink, such as busybox applets or python3 -> python3.x.
  • #70: a service name shaped like <name>_g<hex> is accepted, and can be confused with the name before _g during an update.
  • Uncommitted changes: update, rollback --rebuild, and health restarts of a deployment made from a folder with uncommitted changes build what the folder holds now.
  • After a reboot, containers don’t come back on their own (#60).

​
After v0.1

The order is v0.1, then agent sandboxes, then v0.2. The lifecycle fixes from the 2026-10-01 audit come before sandbox work. See Decision: what comes after v0.1.
  • Agent sandboxes (#71): isolated environments for AI agents, microVM first, with gVisor or PVM for hosts without KVM. Needs a full Linux guest (guest = "linux", #24, #26, #27).
  • v0.2, production readiness (#83): replicas and autoscaling on one host (#25, #29, #30), and services that come back after a reboot (#60).
  • destroy that follows each volume’s keep setting (#59) is tracked but not yet scheduled.