Release Kiri 0.1.14 · libracoder/kiri

New

A fresh Kiri is quiet. Nothing downloads and nothing new appears until you use it: the build engine (BuildKit) is fetched the first time you build, not at setup, and an empty Images list no longer offers a download.
The Engine card is your switch. A fresh Kiri reads Off with Start, even while it sets itself up inside. Press Start and it reads Running, and stays Running while the engine rests between uses. Press Stop and it reads Off. A container you start yourself, for example with docker run in a terminal, also turns it to Running. The button is always there, and Settings › Resources has the same switch.
Linux: Kiri shows in software centers. After installing the .deb or .rpm, Ubuntu's App Center, GNOME Software and KDE Discover list Kiri with its name, description and icon.

Linux: installing doesn't start anything. The engine starts when you set Kiri up (open Kiri, or sudo kiri host-access $USER), and then it waits asleep until you use it.
The engine starts asleep. After setup, a restart or a login it doesn't run a VM nobody asked for; the first docker command, pull or Run wakes it in about a tenth of a second. Containers with a restart policy still come back at once. An upgrade leaves a running engine alone and says how to restart it on the new version.
Kiri's own builder stays out of your lists. It's hidden from Images and Volumes as it already was from Containers; Settings › Builds shows it and can clear the build cache.

Upgrades never leave an old Kiri running. On Windows each engine start brings in this version's engine, so declining Restart engine no longer keeps the old one coming back at every login. On Mac and Linux the window warns when an older kiri comes first on your PATH and says how to remove it, and docker warns when the engine runs another version.
Uninstalling stops everything. kiri setup --uninstall, removing the Linux package, and the Windows uninstaller now stop every Kiri window and command still open.
Shares no longer stall on a single connection. A share that used one connection stopped after about 256 KB on some Kiri Cloud edges and waited there. Kiri now uses the window the edge offers, so one-connection shares run at full speed.
Linux: Builds set up on Ubuntu. The optional Builds step could fail with "docker buildx create failed" when docker already talked to Kiri without a kiri context. Kiri now makes the context when it's missing (without changing which engine plain docker uses), and when a step fails the window says why.
Linux: setup finishes before Open Kiri. Open Kiri waits until docker and builds are set up or skipped, and Kiri no longer says docker still uses Docker's engine when it already reaches Kiri.
Linux: the Kiri icon shows right after installing. GNOME showed an empty tile in search until you logged out and back in.

Downloads for macOS, Windows and Linux: https://runkiri.com/releases/