repowiserepowise

libracoder / kiri Architecture and code health

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

★ 12,144stars on GitHubRustApache-2.0

This connects Repowise to libracoder/kiri's code. It does not install kiri.

Repowise maps public repos from their source. Not affiliated with libracoder. What is Repowise?

github.com/libracoder/kiriIndexed at ac82581

What is kiri?

kiri is a container runtime for macOS, Windows and Linux that runs Docker images and works with the docker CLI, Compose and buildx that developers already use. On macOS and Windows it runs containers inside one small Linux VM, and on Linux it runs them directly on the kernel. It exposes the Docker Engine API, so existing tools connect to it without changes. The project is written in Rust. To install it, run brew install --cask libracoder/kiri/kiri and follow the steps below. Its code health is 6.2 out of 10 (Fair), ranked #207 of 4,000+ indexed repos. The last commit to kiri was on Nov 20, 2026, and 35 people have contributed.

As of commit ac82581, indexed Nov 21, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.

For agentskiri.md

Repo facts: type, license, health, rank, contributors
kiri facts
LicenseApache-2.0
Code health6.2 / 10 (Fair)
Health rank#207 of 4,000+ indexed repos
Last commitNov 20, 2026
Contributors35
Bus factor1
Size435 files, 93,607 lines

Install kiri

Commands copied from the README

  1. 1On macOS, install Kiri with Homebrew.
    brew install --cask libracoder/kiri/kiri
  2. 2Run your first container through the kiri Docker context.
    docker --context kiri run --rm alpine echo hello

Releases on GitHub (latest v0.2.2, Nov 19, 2026)

Full install notes on GitHub

Explore kiri

Ask about this code in your agent

This connects Repowise to kiri's code. It does not install kiri. To install kiri, use the install steps.

Useful if you want to change or fork kiri: your agent can ask how it is put together and get answers that cite its files.

Ask about kiri

Answers come from kiri's README and source, with the files they cite. Two free answers a day without an account.

Featured answer

kiri is a small, fast container runtime written in Rust for macOS, Windows and Linux that runs Docker images and works with the docker CLI, Compose and buildx. On macOS and Windows it runs containers inside a small Linux VM, while on Linux it runs them directly on the kernel. It exposes the Docker Engine API, so the docker CLI, Compose and buildx send requests to the kiri daemon without changes. The daemon handles API requests in crates/kiri/src/daemon/api.rs, keeps its core logic in crates/kiri/src/daemon/engine.rs, and owns the VM, talking to the guest over vsock with message types from crates/kiri-proto/src/lib.rs. Inside the VM, the guest agent running as PID 1, built from crates/kiri-init/src/main.rs, starts each container in namespaces and a cgroup without runc, a shim or dockerd. The Application layer holds 238 of the 435 files, with Docs & Tooling at 42 and Config at 8, so start with the daemon files and crates/kiri-init/src/main.rs.

Files per layer in kiri3 layers.

Basis: Inferred · knowledge graph· as of ac82581

Want this for your own codebase? Map your repo free

About this page

Get a page like this for your own codebase

Repowise built this map of libracoder/kiri from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Free for 2 public repos, with a page like this one. No card. See how Repowise works

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub

libracoder/kiri FAQ

What is kiri?

kiri is a container runtime for macOS, Windows and Linux that runs Docker images. It works with the docker CLI, Compose and buildx, so existing commands keep working against it.

How does kiri work?

kiri runs containers inside a small Linux VM on macOS and Windows, or directly on the kernel on Linux. Its daemon exposes the Docker Engine API, and a Rust guest agent inside the VM starts each container.

How do I install kiri?

On macOS, kiri can be installed with Homebrew using brew install --cask libracoder/kiri/kiri. After installing, run docker --context kiri run --rm alpine echo hello to start your first container. See the install steps

What language is kiri written in?

kiri is written in Rust. The repository also contains JavaScript, shell and Python files, along with a small amount of Swift.

How is the kiri code organized?

kiri keeps its Rust packages under crates, including crates/kiri for the daemon and crates/kiri-proto for the messages between the daemon and the guest. Tests, benchmark scripts and the xtask build tool sit in separate top-level directories.

Who is kiri for?

kiri is for developers who want a lightweight replacement for Docker Desktop on macOS, Windows and Linux. It keeps their existing docker, Compose and buildx commands working against a local engine.

What license does kiri use?

kiri is released under the Apache-2.0 license, as identified by the SPDX id Apache-2.0.

Code health

6.2out of 10Fair

Hotspots average 4.9, the place fixes pay off most.

On the leaderboards:#13 of 24 Rust repos

Key features of kiri

  • Runs Docker containers on macOS, Windows and Linux while the docker CLI, Compose and buildx keep working.
  • Publishes containers under local names ending in .kiri.local, with HTTPS from Kiri's own certificate authority.
  • Starts a single-node Kubernetes cluster with kiri k8s start and sets it as the kiri kubectl context.
  • Creates Linux machines with kiri machine create, with your user, sudo and home folder at the same path.
  • Imports images, volumes and containers from OrbStack or Docker Desktop with kiri import.

How libracoder/kiri works

The docker CLI, Compose and buildx send requests through the Docker Engine API to the kiri daemon, whose API handling is in crates/kiri/src/daemon/api.rs. The daemon's core logic sits in crates/kiri/src/daemon/engine.rs, and the daemon owns the VM. It talks to the guest over vsock using the message types defined in crates/kiri-proto/src/lib.rs. Inside the VM, the guest agent that runs as PID 1, built from crates/kiri-init/src/main.rs, starts each container with a single clone3 call into namespaces and a cgroup. The project does not use runc, a shim or dockerd, and xtask builds the macOS app bundle with the guest kernel and disk template inside it.

The codebase has 435 files and 9,869 symbols in 9 modules, led by Rust, JavaScript and Shell. Code health is 6.2 out of 10, rated fair.