A Docker Desktop Replacement in Rust That Starts Containers in 2.5 Milliseconds

If you've ever waited for Docker Desktop to wake up, spin up its VM, and finally get around to running your container, you know the feeling. You open a terminal, type docker run, and then sit there while your machine thinks about it. Kiri is a bet that this doesn't have to be how it works—it's a lightweight container runtime written in Rust that aims to replace Docker Desktop and OrbStack without the weight.

What It Does

Kiri runs your Docker images in a single small Linux VM (or directly on the kernel if you're on Linux) and speaks the Docker Engine API. That last part matters: because it implements the same API, the docker CLI, Compose, and buildx you already use just work. You don't have to learn a new toolchain or rewrite your workflows.

Under the hood, it's a Rust project with a native window for managing containers, images, volumes, and networks, plus a menu bar item. The name comes from the Igbo word ntakịrị, meaning "small"—which sets the tone pretty clearly. It's available for macOS 14+, Windows 10 and 11 (through WSL 2), and Linux via .deb or .rpm packages.

Why It's Cool

• The startup numbers are the headline. A container starts and exits in about 2.5 ms through the Docker API, which the README claims is roughly 80 times faster than Docker Desktop. Whether that holds up on your machine is something you'd want to test yourself, but the architecture (one small VM instead of a heavier stack) explains where the savings come from.

• It's genuinely light on resources. The VM sleeps after 60 seconds of idle, the daemon sits at around 15 MB, and it wakes in about 0.15 seconds. If you've ever watched Docker Desktop eat a gigabyte of RAM while doing nothing, that's a meaningful difference.

• Compatibility isn't an afterthought. Beyond the docker CLI, Compose, and buildx, it supports docker login and runs amd64 images through Rosetta. Local domains come built in too—http://<name>.kiri.local, with HTTPS from Kiri's own certificate authority. That's the kind of thing you usually cobble together with a reverse proxy and a self-signed cert.

• It does more than containers. There's a one-command Kubernetes cluster and support for Linux machines. For local development setups that outgrow plain containers, that's convenient.

• The localization is unusually thorough. The window and setup ship in 38 languages across all three platforms, including right-to-left layouts for Arabic, Persian, and Central Kurdish. The translations live in the repo, so adding yours is a contribution away.

How to Try It

Grab the installer for your platform from runkiri.com/releases:

1. macOS 14+ (Apple silicon or Intel): download the .dmg.
2. Windows 10/11 (x86-64 or Arm, via WSL 2): download the .msi.
3. Linux (Ubuntu, Fedora, and others): download the .deb or .rpm.

The first time you open Kiri, it sets up a kiri Docker context for you. From there, your existing commands should work as usual—try something like:

docker run --rm alpine echo "hello from kiri"

Kiri also updates itself. If you'd rather build from source, the repo has a development guide, and the features doc goes deeper on what's supported. The full source is at github.com/libracoder/kiri, under Apache-2.0.

Final Thoughts

Kiri is aimed at developers who want Docker's ecosystem without Docker Desktop's footprint—people on laptops where every gigabyte of RAM and every second of startup time counts. The compatibility story is the smart part: you're not asked to change how you work, just what's running underneath. The project is still young enough that you'll want to check the features doc against your specific setup before committing, and the performance claims deserve your own benchmark. But if the numbers hold even approximately, it's a compelling alternative worth a look.