~4m7:13
Better Stack

This Docker Alternative Starts Containers 8× Faster (Kiri)

Nov 14, 2026

Read: ~5m · You save: 2 min

This Docker Alternative Starts Containers 8x Faster (Kiri)

Docker-compatible runtime Kiri starts containers almost 8x faster than Docker Desktop, saves memory, and shares apps with one click. Worth switching?

Docker Desktop takes noticeably longer to start a test container than Kiri. According to its developers, Kiri performs the same operation in 22 milliseconds. Kiri uses the same Docker commands, saves memory, and shuts down the virtual machine when no containers are running. The architecture, test results, additional features, and product limitations are described below.

What Kiri Is

Kiri is a new Docker-compatible container runtime written in Rust. It is not a graphical shell over Docker. The implementation depends on the operating system:

PlatformHow Kiri works
macOSA small, custom Linux virtual machine
WindowsRuns through WSL2
LinuxRuns directly on the host system

Existing Docker commands, Compose files, and Dockerfiles work without changes.

Kiri is free, open source, and supports macOS, Linux, and Windows. The product is in beta.

Installation and Setup

Kiri is downloaded from the official website. After opening, the application automatically creates a Docker context named Kiri. There is no need to uninstall Docker Desktop: both products can be installed at the same time. Switching between them is done by changing the context. Docker commands are then directed to Kiri. You can also use the Kiri command-line interface directly.

Startup Speed Test

The test was run in the terminal on macOS. A minimal Alpine-based container was started, executed an empty command, and was removed immediately. Images were downloaded in advance in both environments, so download time was not counted. The startup and shutdown speed of the container was measured.

Results:

  • Docker Desktop: slower.
  • Kiri: 22 milliseconds, which is about 8 times faster, according to Kiri's own data and the test results.

Faster container startup does not mean faster application performance inside the container. However, when containers are started frequently for testing or local development, the difference adds up.

Local Domains and Public Access

Kiri automatically assigns local domain names to containers. No port forwarding is required for this. A test showed this on an nginx container: it opened at its address without any port mapping. On macOS, HTTPS can be enabled for such domains.

Kiri also allows you to share an application running on the local machine:

  1. Open the application in Kiri.
  2. Click the "Share" button.
  3. Get a public link.

A Kiri Cloud account is required for this. The link is public, so anyone who has it gets access. Confidential data is not exposed in the process, according to the author.

Architecture and Reasons for High Speed

In standard Docker, several components are involved in starting and managing containers: the Docker daemon, containerd, runc, and separate shim processes.

Kiri uses a different approach:

  • the entire stack does not run inside a virtual machine;
  • a lightweight daemon interacts directly with the agent inside Linux;
  • the agent uses the clone3 mechanism to launch containers in their own namespaces;
  • there is no separate runc or shim process for each container.

Fewer components reduce overhead on every container start. This explains the speed results shown.

Memory Usage

The Kiri daemon uses about 10 MB of RAM. This figure applies only to the daemon, not to the entire runtime environment. On macOS, Kiri still uses a virtual machine, which requires memory while it is running.

How the virtual machine works:

  • if no containers are running for 60 seconds, the virtual machine shuts down automatically;
  • unused memory is returned to macOS;
  • according to the developers, restarting the machine takes about 0.1 seconds.

Comparison with Alternatives

Docker Desktop is a mature product with a long history. However, it can be resource-intensive. Large projects may require a paid license.

OrbStack is an alternative for macOS. It is fast, easy to set up, and solves many of the problems of Docker Desktop.

Colima and Podman suit users who need more flexible configuration.

Kiri test results:

  • Colima reads bind mounts faster;
  • OrbStack handles more new HTTP connections per second.

The choice depends on the specific task.

Additional Features

  • Native application for managing containers, images, volumes, logs, and Compose projects.
  • Import of existing images and volumes from Docker Desktop or OrbStack.
  • Built-in support for single-node Kubernetes. According to Kiri, startup takes about 20 seconds when the image is already downloaded.

Limitations and Conclusions

Kiri is in beta. Replacing the Docker runtime requires considerably more work than speeding up container startup. It is necessary to verify:

  • network connectivity;
  • volumes and access permissions;
  • image builds;
  • Compose functionality;
  • non-standard scenarios.

Fully replacing Docker Desktop based on a single test is not recommended. For users who frequently start and stop containers, low overhead may be useful. Local domains and public link sharing are also practically significant features. Since Kiri is free and open source, it can be tested in real-world workflows at no financial cost.

Introduction and Overview of Kiri

Kiri is a Docker-compatible runtime written in Rust that starts faster than Docker Desktop and can shut down its VM when idle.

  • Docker Desktop shows a noticeably longer startup time for a simple container than Kiri (in the video, about 180 ms versus 22 ms for Kiri)
  • Kiri is a Docker-compatible container runtime written in Rust, not an add-on layered on top of Docker
  • On Mac, a small custom Linux VM is used; on Windows, WSL2; on Linux, containers run directly on the host
  • Existing Docker commands, compose files, and Dockerfiles continue to work
  • The Kiri daemon uses about 10 MB of RAM
  • After 60 seconds without containers, the VM automatically shuts down and can be brought back up in about 0.1 seconds

Installation and First Speed Test

Installing Kiri on Mac automatically creates a Docker context, and Docker Desktop does not need to be removed; you can switch between them.

  • Kiri is downloaded from the runkiri site (in the text — Run Cury) and, once opened, automatically creates a Docker context named Kiri
  • Docker Desktop does not need to be removed: you can install both and switch between them
  • After installation, Docker commands start using Kiri; the Kiri CLI is also available directly
  • Test: running an Alpine container that executes an empty command and is removed immediately; the images were already downloaded beforehand, so download time is not counted
  • The measurement compares the startup and shutdown speed of the runtime, not the performance of the application inside the container

Local Domains and Public Sharing

Kiri automatically assigns local domain names to containers, supports HTTPS on Mac, and lets you publicly share an application with one click.

  • The nginx container runs without port forwarding, but is accessible at an address that Kiri creates automatically
  • Instead of local ports, you can use service names (frontend, backend, etc.)
  • On Mac, you can enable HTTPS for domains
  • The Share feature in the app creates a public link to a container without deploying or configuring a tunnel
  • Sharing requires a Kiri cloud account; the link is public, so sensitive data should not be exposed

Architecture and the Reason for Speed

Kiri is faster due to a simplified architecture: a single daemon works directly with the agent inside Linux, without separate runc and shim processes for each container.

  • Docker uses the dockerd daemon, containerd, runc, and separate shim processes to run containers
  • Kiri uses a lightweight daemon that communicates directly with the agent inside the Linux VM
  • The agent runs containers in their own namespaces via the clone3 system call
  • Eliminating a separate runc and shim for each container reduces overhead on every container start

Memory Consumption

The figure of 10 MB refers only to the daemon; on Mac, Kiri still uses a VM, but it can return memory to macOS and shut down the VM when there are no containers.

  • The 10 MB figure refers to the daemon, not to the entire runtime
  • On Mac, Kiri still uses a VM, which needs memory while running
  • Kiri can return unused memory to macOS and shut down the VM when no containers are running

Comparison with Alternatives

Docker Desktop is mature but can be heavy and may require a paid license; OrbStack and Colima/Podman are alternatives. Kiri, however, does not win in every benchmark.

  • Docker Desktop has existed on the market for a long time, but sometimes runs heavily; large projects may require a paid license
  • OrbStack is a good option for Mac: fast, simple to set up, and solves many Docker Desktop problems
  • Kiri is currently free, open source, and works on Mac, Linux, and Windows
  • Colima and Podman are also available for more flexible configuration
  • In its own tests, Kiri was faster than Colima at reading bind mounts, while OrbStack handled more new HTTP connections per second

Additional Features

Kiri includes a native app for managing containers, importing images and volumes from Docker Desktop or OrbStack, and a built-in single-node Kubernetes that, according to Kiri, starts in about 20 seconds.

  • The native app manages containers, images, volumes, logs, and compose projects
  • Kiri can import existing images and volumes from Docker Desktop or OrbStack
  • Built-in single-node Kubernetes support; according to Kiri, startup takes about 20 seconds after the image is downloaded

Limitations and Final Recommendation

Kiri is still in beta, and replacing the Docker runtime is a complex task: networking, volumes, permissions, image building, compose, and edge cases all require verification.

  • Kiri is in beta
  • Replacing the Docker runtime requires verifying networking, volumes, access permissions, image building, compose, and other edge cases
  • The author recommends trying Kiri but not removing Docker yet
  • The author considers local domains and one-step sharing the most useful features, rather than startup speed