From 86462d7087e8ebf6355c38bea4b0affaf2c6bf22 Mon Sep 17 00:00:00 2001 From: Alex Alvord <325058966+cloudlabworks@users.noreply.github.com> Date: Sun, 15 Nov 2026 22:24:21 -0800 Subject: [PATCH 1/2] features: healthchecks, Compose build and depends_on conditions, bind volumes These work on Kiri 0.2.1 and were not listed: --health-* options (including --health-start-interval) and ps --filter health=; Compose up --build and --wait, build:, healthchecks, depends_on conditions (service_healthy, service_completed_successfully) and platform:; and local volumes that bind a folder with driver_opts: {type: none, o: bind, device: /path}. Checked on Apple silicon, macOS 27.0.1, Kiri 0.2.1: - healthy, unhealthy and timeout states, and the health filter - a Compose project with build:, up -d --build --wait, service_healthy and a bind volume - a service_completed_successfully dependency on a platform: linux/amd64 service (uname -m gave x86_64) Docs only. e2e coverage for these is proposed separately in #358. --- docs/features.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/docs/features.md b/docs/features.md index 37ec5efd..99540375 100644 --- a/docs/features.md +++ b/docs/features.md @@ -11,7 +11,9 @@ Apple silicon and Intel Macs (macOS 14+), Windows 10 and 11 (x86-64 and Arm, thr `--restart`, `--entrypoint`), `exec`, `logs`, `attach`, `stop`, `kill`, `restart`, `rm`, `wait`, `rename`, `pause`/`unpause`, `update`, `stats`, `top`, `diff`, `export`, `commit`, `cp` (both ways, running or not), - `container prune`; records survive a daemon restart; filters on every list + `container prune`; records survive a daemon restart; filters on every list; + healthchecks (`--health-cmd` and the other `--health-*` options, including + `--health-start-interval`; `ps --filter health=`) - **Limits and security**: `--memory`, `--cpus`, `--cpu-shares`, `--pids-limit`, `--shm-size`; Docker's default capabilities and a default seccomp filter; `--cap-add`/`--cap-drop`, `--privileged`, `--read-only`, @@ -38,14 +40,19 @@ Apple silicon and Intel Macs (macOS 14+), Windows 10 and 11 (x86-64 and Arm, thr `~/.kiri/tls`, whose name constraints allow only `*.kiri.local` and `*.kiri.localhost` (Settings → Domains → HTTPS asks macOS to trust it) - **Storage**: named and anonymous volumes, bind mounts of Mac paths - (virtiofs), `--tmpfs`, `--mount`, `volume` commands + (virtiofs), `--tmpfs`, `--mount`, `volume` commands; local volumes that + bind a folder (`driver_opts: {type: none, o: bind, device: /path}`) - **Images**: `pull` (with `docker login` credentials), `push`, `tag`, `save`, `load`, `history`, `search`, `image prune`, `system df`; **amd64 images run through Rosetta**, `--platform` honoured - **Builds**: `docker build` / `buildx build` through BuildKit running in a Kiri container (buildx's docker-container driver), stopped when idle; - on Apple silicon, amd64 build steps run through Rosetta too -- **Compose**: `up`, `down`, `ps`, `logs`, `exec`, multiple networks, events + `--platform` for one platform at a time; on Apple silicon, amd64 build + steps run through Rosetta too +- **Compose**: `up` (with `--build` and `--wait`), `down`, `ps`, `logs`, + `exec`, `build:`, healthchecks, `depends_on` conditions + (`service_healthy`, `service_completed_successfully`), `platform:`, + multiple networks, events - **USB devices (beta)**: the USB tab hands a device (a serial adapter, a Zigbee stick, a development board) to your containers on Mac, Windows and Linux, and shows where it is inside Linux with the `--device` line to From c9757693ea1caff548090f4354be3885b1c352c8 Mon Sep 17 00:00:00 2001 From: Alex Alvord <325058966+cloudlabworks@users.noreply.github.com> Date: Sun, 15 Nov 2026 22:24:21 -0800 Subject: [PATCH 2/2] features: two build known issues, multi-platform --load and "not found" 1. docker build --platform linux/amd64,linux/arm64 (Kiri's builder loads by default) fails with "docker exporter does not currently support exporting manifest lists"; --load too. -o type=oci,dest=image.tar works, but Kiri's docker load does not read that archive ("not an image archive: no manifest.json"), so the entry says to build one platform at a time to use the image in Kiri. 2. A build whose BuildKit cannot reach the registry fails with ": not found", because Kiri's mirror is asked first and its 404 is the error BuildKit reports. Say so, and how to check the network instead. Reproduced on Apple silicon (macOS 27.0.1, Kiri 0.2.1) with no DNS in the builder, for a tag Kiri doesn't hold and for a digest-pinned base right after docker pull; with DNS restored the same builds pass. Mechanism and the check to run are in #330. Refs #330 --- docs/features.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/docs/features.md b/docs/features.md index 99540375..73c24a68 100644 --- a/docs/features.md +++ b/docs/features.md @@ -134,3 +134,24 @@ unless the Mac already has a docker CLI. (`--add-host name:172.18.0.1` on Windows and Linux, the default bridge's gateway; `198.19.248.254` on a Mac) or `DOCKER_BUILDKIT=0`, where Kiri maps `host-gateway` itself. + +- **`docker build --platform linux/amd64,linux/arm64` fails** with + `docker exporter does not currently support exporting manifest lists`: + Kiri's builder loads one platform into Kiri per build. Build each + platform with its own `--platform`, or write all of them to an OCI + archive with `-o type=oci,dest=image.tar` (Kiri's `docker load` does not + read OCI archives). + +- **A build that cannot reach a registry says `not found`.** When BuildKit + cannot reach the registry (for example, no DNS in the builder), a base + image Kiri doesn't hold fails with `failed to resolve source metadata for + docker.io/library/alpine:3.15: docker.io/library/alpine:3.15: not found`. + So does a digest-pinned base (`FROM alpine:3.13@sha256:...`) right after + `docker pull` fetched it by that digest. Kiri's builder asks Kiri's image + mirror first; the mirror has no answer for that tag or digest, and when + the registry then can't be reached BuildKit reports the mirror's + "not found" instead of the network error. A docker-container builder + with no mirror shows the real cause (`dial tcp: lookup + registry-1.docker.io ...`). The builder runs on the default bridge, so + check from a container there: + `docker run --rm alpine nslookup registry-1.docker.io`.