Hacker News
Kiri – The Modern Container Runtime
5G_activated
|next
[-]
We have the phrase “container engine” which could mean dockerd or Podman; “container runtime” to me usually refers to containerd or CRI-O but could also refer to runc and crun; and “container manager”, which could alternately refer to dockerd and Podman or to “orchestrators” like k8s Swarm and Nomad. “Desktop app” is what I would call Docker Desktop, Podman Desktop etc.
From cursory reading this appears to be a new desktop app for containers. However they say that the container logic runs behind the real dockerd, so I suppose they’ve slotted it in where containerd goes? So it would be a new container runtime. I feel that’s a little odd to conflate the two, but that’s getting into the hole we’ve already dug with these terms.
binsquare
|root
|parent
[-]
Their test setup based on their docs is `docker run --rm alpine true`.
Which almost certainly guarantees kiri's claim is comparing the warmed boot time with a cached image with docker which calls out to containerd under the hood. Generally cold start is what people actually notice & care about most.
Anyhow I looked under the hood a bit, there's some concerning things calling out to me like they default to deferring actual cleanup before responding with exit notification. It's a tradeoff but clean up failures result in silent pile ups: https://github.com/libracoder/kiri/blob/b249eccc2ed708ce10d7....
disclaimer: I maintain smolvm, a vm that uses crun as the container runtime for running containers.
gempir
|next
|previous
[-]
What is the architecture or technology decision that makes that 8x claim possible?
sureglymop
|next
|previous
[-]
For example, I don't use crun but a more security hardened runtime instead.
sercant
|next
|previous
[-]
:))))))
cholindo
|next
|previous
[-]
d3Xt3r
|root
|parent
|next
[-]
And for macOS, the comparison should be done against Apple containers, OrbStack, Colima etc.
tpetry
|root
|parent
|previous
[-]
And the memory davings is for more than 100 processes. So more than 100 containers? I‘ve got a couple running. Won‘t notice a difference again.
Orbstack is great because the bind mounting is really fast. No talk about that one…
user-error
|next
|previous
[-]
So that's interesting. The offering of container runtimes (also thin VMs in general) on MacOS has been improving a lot.
ksajadi
|next
|previous
[-]
wiether
|root
|parent
|next
[-]
sam_lowry_
|root
|parent
[-]
card_zero
|root
|parent
[-]
pmkary
|root
|parent
|next
|previous
[-]
NewJazz
|next
|previous
[-]
Anhone want to convince me this isn't just slopware?
jbverschoor
|root
|parent
|next
[-]
webstrand
|root
|parent
|next
|previous
[-]
Looking at the codebase this is either not majorly AI generated or the spent a lot of time cleaning up the tells I recognize, so I'd say not slop.
wavemode
|root
|parent
[-]
dimpalo
|next
|previous
[-]
forty
|next
|previous
[-]
i_v
|previous
[-]
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?