I think the headline might be confusing because docker/podman already have the concept of a runtime. E.g. you can pass `--runtime` to set it on the fly or set it in the config...

For example, I don't use crun but a more security hardened runtime instead.

My question is wether "8x faster than docker" means that containers run faster or that the tooling around them runs faster

Excellent Persian name

My question, not clear from the front page, was if it runs faster on MacOS than colima with vz. Full benchmarks claim that it does.

So that's interesting. The offering of container runtimes (also thin VMs in general) on MacOS has been improving a lot.

I scrolled through and it just seems like yet another contaienr runtime.

Anhone want to convince me this isn't just slopware?

Interesting! So based on architecture[1], the daemon responsible for container… scheduling(?) works directly with the VM. There's no traditional init system. The "guest agent" is the initd (kind of a unikernel, huh?) so the overhead of spawning a container is as directly through the kernel syscalls as possible while the other bits happen on the macOS host?

The question I have is, does that mean Kiri implements its own entire container runtime or does it use containerd or some other runtime as its backend?

[1]: https://docs.runkiri.com/features/#what-runs-where

Is anyone still using docker ? I'm surprised they don't compare to podman & all that I see used these days