Kiri 0.1.18

New

• A terminal in the window. Click Terminal in the status bar, or press Control and the backtick key (F4 on Linux). Your own shell with tabs, splits, find and pinned tabs, and Kiri's docker first on the PATH.

Fixed and improved

• Kubernetes pods can use your own folders. A pod's hostPath reaches your drives at /mnt/c, /mnt/d on Windows, /Users on the Mac and /home on Linux. Stop and start the cluster once to get it.
• Linux: Kubernetes no longer breaks your terminals. Privileged containers get their own /dev, as on Docker.
• Containers keep their connections while others start and stop.
• Ports below 1024 and ping work without root, as on Docker.
• Container DNS keeps working when the VM's resolver goes down, and docker build uses your Mac's DNS.
• Deleting Kiri no longer breaks docker build.
• Firewall tools work in containers: nftables, iptables, ipset, IPVS and traffic control.
• A volume over part of a bind gets the image's files, as on Docker. With ./:/app and /app/node_modules, the container keeps its own Linux node_modules, not your computer's.
• Kiri checks for updates every 6 hours while it stays open.
• Settings › Resources looks the same on Mac, Windows and Linux.

---

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

Kiri 0.1.17

Fixed

• Turning off automatic updates now sticks. On Mac, Windows and Linux, Settings showed Off, but the choice wasn't saved, so Kiri checked for updates again at the next launch. It's saved now.
• Turning on crash reports sends only new crashes. Switching them on used to send every crash still waiting, including ones you'd answered Not now to. Kiri now sends only crashes from after you turned reports on. You can still send an older one yourself from its card.
• Logs and reports take out more secrets. Passwords in URLs, Authorization values of any kind, PEM private keys, values after flags such as --password, GitHub, GitLab, Docker Hub and AWS access key tokens, and keys such as PGPASS, API-KEY and *_PRIVATE_KEY are now replaced with [redacted] before anything leaves your computer. It errs towards taking out too much: the whole user part of a URL goes, not only its password.
• Windows: updates stay on HTTPS. Kiri no longer follows a redirect from the update feed down to plain HTTP, and release builds no longer accept a feed from a local file.
• Crash reports never carry your Kiri Cloud account. A crash sent while you were signed in to Kiri Cloud went with your sign-in, so it named your GitHub account. Crashes now always go without it. A diagnostics report you send yourself still says it's from you, so we can reply, and the Send dialog says so.
• Crash reports leave out your image and container names. The log lines a crash report carries named the images you pulled and the containers that stopped, including private registries. Those names are now taken out wherever they appear in the report.
• Windows: reports take out your user name in every form. Your home folder was only blanked when written exactly as C:\Users\you. Now it also goes in lower case, with forward slashes, doubled inside JSON, as WSL's /mnt/c/Users/you, and as /home/you in the engine's log.
• Still more secrets are redacted. password: … and key = … with spaces, Cookie and Set-Cookie headers, X-Api-Key, JWTs, Stripe, Slack, Anthropic, OpenAI, Google, npm and PyPI tokens, and email addresses. A secret written inside another value, such as env=[DB_PASSWORD=…, is no longer missed.
• Settings says exactly what a crash report sends: the stack trace, the last 200 log lines, versions, the computer's model and a random ID for this install.

0.1.16 was tagged but never released; its fixes are in this release.

Thanks to @9trocode for the first four fixes, Kiri's first outside contribution.

---

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

Kiri 0.1.15

New

• Linux: signed packages and repositories. Every .rpm and the Linux checksums are signed with the Kiri Releases key, and download.runkiri.com now serves signed apt and dnf repositories, so apt upgrade and dnf upgrade can keep Kiri current. The key is kiri-archive-key.asc on the download site.

Fixed

• Mac: image files no longer come back empty. When the engine went to sleep or stopped right after a pull, the VM could stop before its disk had caught up, and a newly unpacked image could keep its file names but lose their contents. Builds then failed in RUN steps and some programs (iperf3, for one) wouldn't start. Kiri now waits for the engine's VM to power off, writes each layer out in full before using it, and unpacks again any layer that was cut short.
• kiri share no longer crashes when its output goes away. Piping it into a command that exits, or closing the terminal it printed to, made it panic and leave a crash report. Kiri commands now end quietly when their output is closed.

---

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

Kiri 0.1.14

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.

Changed

• 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.

Fixed

• 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/