Registry access and test-tool expectations
The official notes add image pulls from GitHub and Amazon ECR using the registries’ own sign-in pages, along with a searchable language selector and a 38-language interface. They also report improved Testcontainers compatibility. For a developer, these boundaries matter because running a simple image is only one part of a usable environment. Integration-test clients can depend on details of Docker API responses before starting their own services. The release claim is useful evidence of work on that boundary, while compatibility with an individual project’s full suite still requires validation.
Predictable starts, stops and restarts
The maintainers report fixes for competing Start and Stop operations and for restoring containers configured with the always or unless-stopped restart policies after Kiri restarts. Lifecycle behavior is especially relevant to local databases, message queues and other dependencies that tests expect to remain available. An interface showing a stopped service should agree with what client tools observe. These are upstream release claims, not results from a cross-platform test performed by this publication. A team evaluating the update should include its usual shutdown and recovery sequences rather than testing only the first successful launch.
The architecture and licensing context
The repository presents Kiri as a Rust-based alternative to Docker Desktop and OrbStack that implements the Docker Engine API. The practical proposition is to retain familiar client tools while changing the engine behind them. The project code uses Apache 2.0, with separate third-party notices and a GPL-2.0 Linux kernel. Our assessment is that API compatibility should be evaluated through actual workflows: Compose configuration, volumes, networking and test tooling can reveal differences that a minimal container demonstration misses. A supported API name is not a certification that all operational behavior is identical.
Keep the speed claim attached to its test
Kiri’s homepage advertises a comparison of one docker run scenario on one Apple-silicon machine, with two CPUs and 8 GB allocated to each engine. It is the developer’s measurement, not our independent benchmark of container workloads generally. Startup timing says little about a large image build, storage throughput or a database under sustained load. For this release, the compatibility changes provide the more useful evaluation targets. Compare a representative development cycle before moving an existing environment, and retain a way back to the previous runtime if project-specific behavior differs.

Discussion.
Your perspective matters. Sign in, pick a nickname and choose your cyber identity.
Loading discussion…
Your account name, email and photo stay off your comments.