3 ms·

It runs on top of https://github.com/containers/libkrun https://github.com/containers/libkrun. Similar to Firecracker but seems specifically targeted to making

It runs on top of https://github.com/containers/libkrun https://github.com/containers/libkrun. Similar to Firecracker but seems specifically targeted to making microVMs out of OCI containers (via CLI) as opposed to Firecracker which uses a downloaded kernel and rootfs and is managed via API ala https://github.com/firecracker-microvm/firecracker/blob/main/docs/getting-started.md#running-firecracker https://github.com/firecracker-microvm/firecracker/blob/main.... But I'm no expert, just my armchair take on things.

debarshri 4y ago
If it is OCI compatible, it technically means you could use kubernetes or another container orchestrator to orchestrate these microvms. I wonder krunvm already works with kubernetes.
- mcronce 4y ago
  If I'm understanding correctly, it's OCI compatible in the other direction - it consumes OCI compatible images, but it doesn't expose an OCI compatible layer on top for orchestration. kube-virt[1] is a thing, though, that provides k8s orchestration for VMs. I don't see why you couldn't use krunvm microvms with that [1] https://github.com/kubevirt/kubevirt https://github.com/kubevirt/kubevirt