GET STARTED

What's new

What changed in each release of Kiri, newest first. Kiri updates itself: the window offers each new release, and Updates explains how. For the longer story behind a release, see the blog.

Kiri 0.1.4

28 October 2026.

Updates in the window

• When a new release is out, a card in the corner of the window offers it, with Download, Snooze and Skip this version.
• The download runs in the background, with its progress in the status bar. Kiri checks its SHA-256, Kiri’s signature, notarization and version before it’s staged.
• Restart now installs it straight away. Otherwise it installs when you quit Kiri, or at the next launch.
• Kiri → Check for Updates… asks at any time, and kiri update does the same from a terminal.
• The window tells you when the engine is still running an older build than the app.

Images

• The Pull box searches Docker Hub as you type, then lists the tags of the image you pick.
• Pulls show progress per layer in the window, and docker pull draws its progress bars too.
• The Images table has a Pulled column and sorts by any column.
• Each image says which containers use it (“used by web”). Removing an image that stopped containers use offers to remove them first; if one is running, Kiri says so and removes nothing.
• After a pull or a remove, a notice shows how long it took, the size, and a Run button for a new image.

The window

• Drag a column’s edge to resize it; double-click to reset. Widths are saved.
• The Containers table sorts by name, image, state, ports, size or created.
• A container’s status reads in short units (Up 2 h, Exited (0) 5 min ago) and keeps counting while the window is open.
• A container with several ports shows the first one and a “+N more” chip, so rows stay inside the window. The default window is larger, at 1180 × 720.
• A container’s terminal tab works like a shell: one console, the prompt after the output, and cd carries over between commands.
• View → Zoom In (⌘+), Zoom Out (⌘−) and Actual Size (⌘0) change the text size.
• A strip at the bottom of the lists tells you when another engine has images, volumes or containers Kiri doesn’t, and opens a window to import them.
• A Feedback button in the status bar.
• Settings opens without freezing, and the sidebar no longer sticks after a quick click.

Memory

• The VM now sleeps after a minute idle even with the window open. Before, the window’s own status requests kept it awake.
• The VM holds less while awake: it gets back a 64 MB buffer it never used, and keeps 256 MB of headroom instead of 512 MB.
• The sidebar and status bar show the memory the VM uses, not its allowance, and 0 MB while it’s asleep.

Networking and the engine

• Published ports listen on all interfaces, as Docker’s do. Use -p 127.0.0.1:8080:80 to keep a port on this Mac only.
• Large input piped into a container (docker run -i, docker exec -i) is no longer cut off after 4 MiB.
• Opening a new copy of Kiri.app replaces a login agent left by another copy, and first-open setup no longer fails when the app has moved.

New

• Kiri Share: kiri share 3000 (or just kiri 3000) gives a local port or container a public HTTPS address on runkiri.cloud. See Command line and CI.
• Kiri on Windows, experimental: a per-user installer, first-run setup of WSL2 and the engine, the same window, Docker Hub search and in-app updates. See Kiri on Windows.
• Linux packages: .deb and .rpm, as kiri with the docker CLI, Compose and buildx, or kiri-lite for the engine alone. See Kiri on Linux.

Security

• Containers, including --privileged and unconfined ones, can’t open vsock sockets, the way to the Mac’s services, or use io_uring.
• A crafted image can’t write or delete files outside its layer, and a registry can’t name a host file as a blob.
• ~/Kiri is served only to your own user, over a private socket instead of a loopback port.
• An update must be newer than the running version and signed by Kiri, so an old release can’t be replayed.
• Kiri’s HTTPS certificates are reissued before they expire, registry credentials go only to https:// token services, and DNS forwarding checks its replies.

Kiri 0.1.0

24 October 2026. The first release: a signed, notarized app for Apple silicon Macs.

• Docker: the Docker Engine API on the kiri docker context, so the docker CLI, Compose and buildx work unchanged. Containers, volumes, bind mounts, user networks, builds on BuildKit, registries, and amd64 images through Rosetta.
• Names: containers at <name>.kiri.localhost, or <name>.kiri.local once you turn it on, with HTTPS from Kiri’s own certificate authority.
• Mac integration: container files in Finder at ~/Kiri, and your SSH agent inside containers.
• Memory: a balloon gives unused memory back while the VM runs, and the VM sleeps after 60 seconds idle.
• The app: the window, the menu bar, kiri setup on first open, and kiri update.
• Beyond Docker: kiri k8s start for a k3s cluster, kiri machine for Linux machines, and kiri import from OrbStack or Docker Desktop.

© 2026 Kiri · runkiri.com