v0.2.1

Container orchestration over CRI, with service images built straight from
Nix closures instead of Dockerfiles.

nix-compose speaks CRI gRPC directly to containerd or CRI-O — no daemon,
no compose file, nothing shelling out to another tool. A service can name a
package instead of a registry image, and its image is built from that
package's Nix closure and imported into the runtime: no Dockerfile, nothing
pushed or pulled.

Install

nix run github:systemstart/nix-compose -- up -d
# or
go install github.com/systemstart/nix-compose/cmd/nix-compose@latest

Or download an archive below. Linux only; needs containerd or CRI-O.
Run nix-compose doctor first — it checks every prerequisite and each
finding carries its fix.

Before you adopt it

Read docs/limitations.md
— a deliberately complete account of what does not work, not a marketing
document. The changes in this release are listed below.

Changelog

Fixes

• 0205711 fix(microvm): satisfy the NixOS boot assertions
• 769b12b fix(microvm): use the real virtio vsock module name
• f8cf695 fix(release): stop the changelog emptying itself
• 16bd42e fix(release): surface breaking changes in the release notes

Other changes

• fff18bf build(nix): version from ./VERSION, and complete package meta
• 1355514 build: relax the go directive to the dependency-graph minimum
• 3f4f566 build: sign release tags with git tag -s
• 8c190c7 chore: release v0.2.1
• c9c8aa1 ci: gate on nix flake check and build the VM images

---

While the major version is 0, the nix-compose.yaml schema and the CLI
surface may still change between minor releases.

Archives are attested with build provenance; verify with
gh attestation verify <archive> --repo systemstart/nix-compose.