Kiri Windows

Experimental Windows 10 and 11 · x64 · WSL2

Kiri for Windows.

Kiri's Linux engine runs inside WSL2, on the Linux kernel Windows already ships. A small Windows program serves the Docker API on a named pipe and opens Kiri's window, so docker in PowerShell just works.

Experimental, and not out yet. Every number here was measured on it.

Measured

Six times faster to start a container.

Kiri and Docker Desktop on one Windows PC, minutes apart, through the same docker CLI from PowerShell, with the same images, warm.

MeasurementKiriDocker Desktop
docker run --rm alpine true78 ms491 ms
docker exec … true57 ms89 ms
200 MB out of a container255 MB/s40 MB/s

Medians of 20 runs, 25 October 2026. Windows 11 Pro, AMD Ryzen AI MAX+ 395, 128 GB, WSL 2.6.3 with NAT networking; Docker Desktop 29.8.2 on its WSL2 backend with default settings; Kiri 0.1.0 in Ubuntu 24.04. Copying into a container isn't comparable yet, so it isn't shown.

Windows

Windows on the outside, Linux where it counts.

A native window

The same Kiri window as on the Mac, built on Win32 and WebView2, the browser engine Windows already has. No Electron.

The Docker API on a named pipe

kiri-win.exe serves the API at \\.\pipe\kiri as the kiri docker context, and carries it into WSL over a single bridge.

Your network settings stay put

No change to WSL's or Windows' network configuration, no port juggling, no localhost relay to drop half your output.

No admin, no service

A per-user installer into your own profile. Kiri starts when you sign in, and uninstalls cleanly.

Plays nicely with Docker Desktop

If Docker Desktop is installed, Kiri doesn't take over as the default engine, and an existing docker CLI keeps winning on PATH. Switch with docker context use kiri.

Everything in one installer

The engine, kiri-win.exe, the docker CLI, Compose and buildx, so nothing else needs installing.

When it lands

What you'll need.

Windows 10 or 11, x64

Arm PCs aren't supported yet.

WSL2

If you don't have it yet, wsl --install in an administrator PowerShell, then restart. Kiri uses a WSL distro you pick on first run.

Nothing else

No Docker Desktop, no Hyper-V settings to change. Kiri brings its own docker, Compose and buildx.

Day one

Three steps to your first container.

  1. Run the installer

    Open the .msi. It installs for you alone, with no admin prompt, and adds Kiri to the Start menu.

  2. Open Kiri

    First run picks a WSL distro and sets up the kiri docker context. Then open a new PowerShell window.

  3. Run something

    > docker run --rm hello-world

    Compose and buildx work too, from Windows or from inside WSL.