Docker Desktop is still the engine a lot of us reach for by habit. It works, and the tools around it are familiar. So when a new runtime offers to replace it, the fair question is not “is this exciting?” It is “is this actually ready?”
Kiri is an open-source Rust container runtime, licensed under Apache 2.0, built to run the same docker, Compose and buildx workflow you already use. The GitHub repository was created on 2 November 2026. As of 15 November 2026 it had about 4,690 stars, 50 open issues and 30 open pull requests, and the current release was 0.2.1. That is a fast start, and a very young project, so this Kiri vs Docker Desktop comparison looks at what works today and what still needs time.
This piece looks at what Kiri is, how it works, how you install it, and how it compares with Docker Desktop, OrbStack and Colima. Every speed figure below is Kiri’s own, not an independent test. For the wider picture of containers and clusters, see our guide on Docker vs Kubernetes.
- What Is Kiri?
- How Does Kiri Work?
- How to Install Kiri on Mac, Windows and Linux
- Quick Start: Your Usual Docker Commands
- Kiri vs Docker Desktop, OrbStack and Colima
- The Speed Numbers, and Their Caveats
- Licensing and Using It at Work
- Kubernetes, Local Domains and kiri import
- So, Is It Really a Docker Desktop Replacement?
- Kiri FAQs
- Final Thoughts
What Is Kiri?
Kiri is a Docker-compatible runtime for macOS, Windows and Linux. It serves the Docker Engine API, so the docker CLI, Compose, buildx, your IDE and Testcontainers can keep working. The name comes from the Igbo word ntakịrị, meaning “small”.
On a Mac, containers run inside one small Linux VM. On Windows, still in beta, the engine runs in WSL2. On Linux there is no VM: the same daemon runs on the host kernel. Kiri also adds a native window, local names such as web.kiri.local, HTTPS from its own certificate authority on the Mac, a one-command Kubernetes cluster, and kiri import to copy work over from Docker Desktop or OrbStack. It is in beta on all three platforms.
How Does Kiri Work?
Docker Desktop runs Docker’s own stack inside its VM: dockerd, containerd, a shim per container, and runc. Kiri’s architecture docs describe a shorter path. On a Mac, a daemon serves the Engine API at ~/.kiri/run/docker.sock and owns one Linux VM, created with Apple’s Virtualization framework. That VM boots a custom kernel of about 10 MB, cut down from 32 MB according to Kiri’s benchmarks page. Inside, a Rust agent called kiri-init is PID 1 and starts each container with a single clone3 call into new namespaces and the container’s cgroup.
The daemon and the agent talk over vsock. Image layers are streamed into the VM once and reused, and every container process is a direct child of the agent. If the daemon disappears, the VM powers itself off. On Linux, that same agent runs on the host kernel. On Windows, the Linux build runs in WSL2. If you like Rust in systems software, this is in the same spirit as projects such as Pingora among reverse proxies.
How to Install Kiri on Mac, Windows and Linux
Downloads live on runkiri.com/releases, with steps in the install docs. You can keep Docker Desktop or OrbStack installed. Kiri adds a kiri Docker context and does not replace /usr/local/bin/docker.
On a Mac you need macOS 14 or later, Apple silicon or Intel. Open the .dmg, drag Kiri to Applications, and launch it. The app is signed and notarized. On a Mac or Linux machine you can also use the install script, which checks the download first:
curl -fsSL https://runkiri.com/install.sh | bash
On Windows 10 or 11, Kiri is still in beta. Run the per-user .msi. The docs note that the installer is not code-signed yet, so Windows will ask you to confirm. The engine runs Linux containers in WSL2, not Windows containers.
On Linux there is no VM. Install a .deb or .rpm for x86-64 or ARM, join the kiri group, and sign in again. The full package includes the engine plus the Docker CLI, Compose and buildx; kiri-lite is the engine alone. Treat the kiri group like the docker group: membership is root-equivalent. The API socket is /run/kiri/docker.sock. If you are picking a distribution, our best Linux distros guide is a useful starting point.
sudo apt install ./kiri_0.2.1_amd64.deb # Debian, Ubuntu
sudo dnf install ./kiri-0.2.1-1.x86_64.rpm # Fedora, RHEL
sudo usermod -aG kiri $USER # then sign in again
Quick Start: Your Usual Docker Commands
Open a new terminal after install so your shell picks up the new PATH. If another engine is already the default, aim at Kiri with the context flag, or switch to it:
docker --context kiri run --rm alpine echo hello
docker --context kiri compose up -d
docker context use kiri
docker context use desktop-linux # back to Docker Desktop
The kiri command always talks to Kiri, so kiri run and kiri compose are safe aliases. If you already have a CLI you like, Kiri Lite leaves it in place and installs only the engine.
Kiri vs Docker Desktop, OrbStack and Colima
The everyday Docker workflow is common ground. The differences sit in platforms, licences, and what sits behind the socket. This table follows Kiri’s comparison on its Docker runtime page, checked in November 2026. Confirm current terms on each project’s site before you rely on them at work.
| Feature | Kiri | Docker Desktop | OrbStack | Colima |
|---|---|---|---|---|
| macOS | Yes | Yes | Yes | Yes |
| Windows | Yes (beta, Linux containers in WSL2) | Yes | No | No |
| Linux | Yes, no VM | In a VM | No | Yes |
| Free at work | Yes (Apache 2.0) | Paid over 250 staff or $10M revenue | Paid for work | Yes (MIT) |
| Open source | Apache 2.0 | No | No | MIT |
| Desktop app | Native | Electron | Native | CLI only |
docker, Compose, buildx | Yes | Yes | Yes | Yes |
| Kubernetes | Yes (k3s) | Yes | Yes | k3s |
Docker Desktop still has Windows containers, Extensions, and the admin features companies use to manage many installs. Kiri is pre-release, implements the Engine API itself, and answers with a clear error when a feature is missing. It also refuses some options today, including --gpus and some mount and network drivers.
The Speed Numbers, and Their Caveats
These figures all come from Kiri, either its benchmarks documentation or its Docker runtime page. I have not rerun them.
The benchmarks page uses this test: create a container from alpine:latest, run true, wait until it is removed. Median of 30 runs after 5 warm-ups, same docker CLI (29.7.2), one Apple silicon Mac, default bridge network:
| Path | Kiri | Docker Desktop | OrbStack |
|---|---|---|---|
| Docker Engine API | 2.55 ms | 213 ms | 380 ms |
docker CLI | 14.15 ms | 243.3 ms | 442.2 ms |
Kiri says most of its CLI time is the CLI starting up, and that the API path is around 80 times faster than Docker Desktop. The same docs note that OrbStack had 86 containers and a Kubernetes cluster running during that test, with Docker Desktop’s VM up as well, so OrbStack’s numbers are pessimistic. On a Mac you can rerun it with kiri bench --network bridge --runs 30.
A wider table on the Docker runtime page, dated 2 November 2026, compares Kiri 0.1.13 with Docker Desktop 4.90.0, OrbStack 2.2.4 and Colima 0.10.3, each limited to 2 CPUs and 8 GB. docker run --rm alpine true is listed as 22 ms, 178 ms, 279 ms and 152 ms. Parallel starts are 88.9, 11.4, 8.2 and 12.9 containers per second. Bind-mount reads of 1 GB go the other way: Colima at 5,235 MB/s and OrbStack at 3,240 MB/s both beat Kiri’s 1,724 MB/s, with Docker Desktop at 1,354 MB/s. On Windows, that page says Kiri starts a container in 78 ms against Docker Desktop’s 491 ms.
Cold boot of the VM to a ready agent is listed at 112 ms. The VM sleeps after 60 seconds idle. The README says it wakes in about 0.15 seconds, and that the daemon stays at about 15 MB. The benchmarks page measures the daemon plus guest agent at 9.7 MB resident, with no per-container shim.
Licensing and Using It at Work
This may matter more than the 2.55 ms figure. Kiri’s GitHub licence is Apache 2.0, and Kiri says it is free for any company of any size. Docker Desktop, on Kiri’s comparison page, needs a paid subscription in companies with more than 250 employees or more than $10 million a year in revenue. OrbStack is free for personal use and paid for work. Colima is also free, under MIT, but it is CLI-only and has no Windows build. A free licence still leaves the maturity question: a two-week-old beta needs a review, a rollback plan, and a check against the Engine API features your team actually uses.
Kubernetes, Local Domains and kiri import
kiri k8s start runs a single-node k3s cluster in one container and writes a kiri kubectl context. After the first image pull, Kiri’s docs say a start takes about 20 seconds. LoadBalancer services get their ports on localhost. The cluster is itself a container, so the VM stays awake while it runs.
kiri k8s start
kubectl --context kiri get nodes
Running containers answer at http://web.kiri.localhost with no setup, or at http://web.kiri.local once you turn that on. Compose services get names such as api.myapp.kiri.local. On a Mac you can enable HTTPS in Settings → Domains. Kiri then uses its own certificate authority, constrained so it can only vouch for *.kiri.local and *.kiri.localhost. Your app can keep serving plain HTTP inside the container. The docs say Windows and Linux do not yet have HTTPS for those names.
kiri import copies tagged images, named volumes and containers from OrbStack or Docker Desktop. It only reads from the source; nothing there is removed. The command is currently documented as Mac-only:
kiri import desktop-linux --list
kiri import desktop-linux
docker context use kiri
So, Is It Really a Docker Desktop Replacement?
For a lot of day-to-day Docker work, it can be. Install it beside Docker Desktop, import what you need, and switch contexts for a week. If Compose projects come up, builds finish, and your IDE still talks to the socket, you have a real answer for your machine. If something is missing, Kiri is supposed to say so with “Kiri does not support … yet.”
Try it, and you may want to switch, if you are on a personal Mac or Linux machine, you want a lighter engine, your company would otherwise pay for Docker Desktop, or you spend a lot of time on short-lived containers such as integration tests. Linux users who would rather not run Docker Desktop’s VM have an especially clean fit. Colima remains a strong free alternative if you are happy in the terminal.
Wait, or keep Docker Desktop as the default, if you need Windows containers, Docker Extensions, GPU passthrough, or a vendor your security team has already approved. The same goes for any workflow that depends on an Engine API feature Kiri has not implemented, or for teams that cannot accept a project this young as their standard tool. Two weeks of rapid development is impressive. It is not a long track record.
Kiri FAQs
Is Kiri compatible with Docker?
It serves the Docker Engine API, so the docker CLI, Compose, buildx and socket-based tools can work with it. It runs standard images from Docker Hub or other registries. Features it does not implement return an error that says so.
Do I need Docker Desktop installed, and can I switch back?
No, you do not need it. Kiri brings its own docker CLI, Compose and buildx, or Kiri Lite can install only the engine. To go back, use docker context use desktop-linux, or docker --context kiri for a single command. Both engines can stay installed, though they do not share a VM.
Does Kiri run on Linux without dockerd?
Yes. On Linux, one daemon replaces dockerd, containerd and runc, running on the host kernel as kiri.service, with the socket at /run/kiri/docker.sock.
Are the speed claims independently verified?
Not in this article. The numbers here are from Kiri’s documentation and website, including tests dated 2 November 2026 and later figures on the benchmarks page. Kiri also documents caveats, such as other engines being under load during one run. Use kiri bench on your own Mac if the difference matters to you.
Is it ready for a whole company to adopt?
I would not treat a mid-November 2026 beta, first released on 2 November, as a company-wide default yet. It is ready to try, and it may already be a good daily driver on a personal machine. For a fleet of work laptops, wait for more time in the wild and a check against the APIs your team actually uses.
Final Thoughts
Kiri is one of the more interesting Docker Desktop alternatives to appear this year: a small Rust engine, the same commands, a free licence at work, and no VM on Linux. For many developers’ daily docker and Compose use, it is already close enough to try, and maybe close enough to stay. For Windows containers, Docker’s wider product, GPUs, or any team that needs a mature, approved vendor, the honest answer is not yet. The best way to settle it is still the boring one: install it next to what you have, switch the context, and see whether your real projects come up cleanly.





