Kiri for Linux.

No VM at all. The same Rust daemon that runs inside Kiri's VM on a Mac runs straight on your kernel here, creating each container with one clone3. No dockerd, no containerd, no shims, no runc.

Coming soon How it works

Kiri runs on Linux today. The packages aren't published yet.

Linux

The whole engine, and nothing else.

One daemon, one call per container

Namespaces, the cgroup, overlayfs and the seccomp filter are set up by Kiri itself, with nothing left running per container.

A systemd service

kiri.service is enabled and started on install. The socket is /run/kiri/docker.sock, owned by the kiri group.

Two flavours

kiri brings the docker CLI, Compose and buildx. kiri-lite is the engine alone, for machines that already have a docker.

Doesn't fight your docker

Kiri offers docker through update-alternatives only when nothing else owns it. A CLI another package installed keeps winning.

One build for every distro

Static binaries, so the same package runs on Debian, Ubuntu, Fedora, RHEL and openSUSE.

Upgrades don't stop containers

Upgrading the package leaves the running engine alone. Restart kiri when it suits you.

When it lands

What you'll need.

An x86-64 Linux with systemd

Debian or Ubuntu for the .deb; Fedora, RHEL or openSUSE for the .rpm. Arm64 packages are coming.

Membership of the kiri group

Like the docker group, it is root-equivalent: anyone in it can run containers as root on this machine.

Nothing else

The full package brings the docker CLI, Compose and buildx.

Day one

Three steps to your first container.

Install the package
```
$ sudo apt install ./kiri_<version>_amd64.deb
```
Or sudo dnf install ./kiri-<version>-1.x86_64.rpm.
Join the kiri group
```
$ sudo usermod -aG kiri $USER
```
Then sign out and back in.
Run something
```
$ docker run --rm hello-world
```
Compose and buildx work as usual.

Other platforms

Kiri for MacOne small VM on Apple silicon Kiri for WindowsInside WSL2, with a native window