Subscribe
0%
Illustration for: Kiri is a free Rust container runtime that keeps your Docker commands and starts containers in milliseconds. What to know

Kiri is a free Rust container runtime that keeps your Docker commands and starts containers in milliseconds. What to know

Kiri, an Apache-2.0 Docker Desktop and OrbStack alternative for Mac, Windows and Linux, has passed 10,800 GitHub stars in about two weeks. An independent Linux benchmark found warm starts about 5x faster than Docker CE, but also slower builds, early setup bugs and a group that is effectively root.

Listen to this article0:00 / 4:50
libracoder/kiri

A small, fast container runtime for macOS, Windows and Linux with a free ngrok alternative

Language
Rust
License
Apache-2.0
Stars
10.8K
View on GitHub

Kiri, an open-source container runtime written in Rust, is one of the fastest-rising projects on GitHub this week. GitHub's search API shows libracoder/kiri was created on November 2 and had about 10,860 stars by November 19. Apache-2.0 licensed, it pitches itself as a drop-in for Docker Desktop or OrbStack. Your docker CLI, Compose files and Dockerfiles keep working, but they talk to a much smaller engine.

Why it matters: as Geeky Gadgets notes, Docker Desktop's licensing can require payment for larger organisations. A free engine that keeps the Docker workflow and starts containers almost instantly is an easy sell. That explains a Hacker News thread and several write-ups in the past week. The independent numbers back up part of the pitch. They also show it's beta software with sharp edges.

What it does

Per the project materials summarised by Better Stack and Geeky Gadgets:

  • Implements the Docker Engine API. It installs a Docker context called kiri alongside any existing Docker Desktop or OrbStack contexts. A quick test is docker --context kiri run --rm alpine echo hello.
  • One small daemon instead of a stack of shims. The project says Docker Desktop and OrbStack pass each container start through several processes, while Kiri's daemon starts containers directly with Linux clone3. That's the project's own description of the design.
  • Per-platform approach: on macOS, a small Linux VM that idles down after about 60 seconds and gives memory back. On Windows, WSL2. On Linux, the host kernel directly.
  • Extras: automatic local domain names for containers (HTTPS on Mac), a native GUI, a bundled single-node k3s cluster, Linux machines, image and volume import from Docker Desktop or OrbStack, and public share links for local apps. The share links require a Kiri Cloud account and are open to anyone who has the URL.

The v0.2.1 release notes add Testcontainers support, pulls from GitHub's registry and Amazon ECR, Docker-style exit codes, and a long list of fixes for networking, restarts and bind mounts. Downloads are on the project site, runkiri.com.

How fast is it, really?

The headline claim is a warm docker run of Alpine in 22 ms versus 178 ms for Docker Desktop on an Apple-silicon Mac. That's roughly 8x, from the project's own November 2 benchmark. Better Stack points out that this measures short-lived container starts, not application performance.

ComputingForGeeks ran its own tests of Kiri 0.2.1 on 2-vCPU Google Cloud VMs running Ubuntu 26.04 and Rocky Linux 10:

Test Kiri 0.2.1 Docker CE Podman
Warm run --rm alpine (mean of 20) 69.5 ms 349.2 ms 169.0 ms
Cold start (median of 5) 341 ms 767 ms 513 ms
compose up -d (median of 5) 175 ms 708 ms 938 ms
--no-cache build (median of 3) 2,035 ms 1,953 ms 1,674 ms
Idle engine memory 3.6 MB 137.3 MB no daemon

That works out to about 5x Docker CE on warm starts, not 8x, and slightly slower builds. Memory rose to 82 MB after builds because Kiri starts a BuildKit container. Better Stack also notes comparisons where Colima reads bind mounts faster and OrbStack accepts more new HTTP connections per second.

The catches

  • Security on Linux: ComputingForGeeks found that members of the kiri group are effectively root. Its author read /etc/shadow from a container without sudo. Under SELinux enforcing, the daemon and containers ran unconfined, and the :Z volume label had no effect.
  • Coexisting with Docker: a bug (#261) silently dropped Kiri container traffic when Docker CE ran on the same host until the author added two iptables rules.
  • Setup rough edges: the service didn't start after install, and the Rocky Linux RPM needed EPEL for a WebKit dependency. Upgrades restart the engine, which stops all containers.
  • Not for Kubernetes nodes: it's a Docker API engine, not a CRI runtime, so a kubelet can't use it.
  • Young project: Kiri is under three weeks old and still labelled beta. A third-party repo tracker, OSRepos, attributes most commits to a single contributor. ComputingForGeeks judged it fine for developer workstations and CI runners, but not production servers.

Who should try it

Mac and Windows developers frustrated by Docker Desktop's start-up times or memory use can install Kiri next to their current setup. Point a single project at --context kiri, then switch back if something breaks. Switching contexts doesn't migrate existing containers or volumes, so use Kiri's import tool or start fresh. On shared Linux machines, treat the kiri group like the docker group, which effectively means root, and wait for SELinux confinement before going near servers.

Sources

  1. ComputingForGeeks — Kiri Container Runtime on Linux: Install and Benchmark vs Docker computingforgeeks.com
  2. Better Stack — Kiri: A Smaller Runtime Behind Familiar Docker Commands betterstack.com
  3. Geeky Gadgets — Kiri Docker alternative geeky-gadgets.com
  4. OSRepos — libracoder/kiri osrepos.com
  5. NewReleases — libracoder/kiri v0.2.1 release notes newreleases.io
  6. Zeli — Kiri runs Docker containers 8× faster than Docker Desktop (Hacker News discussion) zeli.app

#Kiri#containers#Docker#Docker Desktop#OrbStack#Rust#developer tools#open source