You can now run same OCI images as containers or Firecracker microVMs

Discussion (6 Comments)Read Original on HackerNews

vaylian•4 minutes ago

Sweet. I had hoped for someone to make a p2p container registry eventually. There is too much centralization with the current popular registries.

ranger_danger•about 2 hours ago

Where does the microvm kernel/initrd come from? How can it be built?

I just want a system that's as easy as "docker run ubuntu" but launches as a microvm instead, without me having to source a kernel or remember hugenormously long qemu incantation lines.

thepoet•2 minutes ago

We will be soon including this in Tarit, a firecracker alternative https://github.com/instavm/tarit

Currently we have to supply a kernel

TARIT_KERNEL=/path/vmlinux

taritd serve taritd image build --oci ubuntu:24.04 --name ubuntu taritd vm create --image ubuntu

liquid64•about 1 hour ago

The kernel/initrd come from a regular OCI container image — there's no separate VM image format. Any OCI image containing /boot/vmlinux (and optionally /boot/initramfs.cpio.gz) works as a kernel image.

spwa4•about 1 hour ago

And if they don't have a kernel? You just specify kernel + initrd?

yakimbo90•26 minutes ago

you don't have to source one manually — pullrun kernel install fetches a kata containers kernel into ~/.pullrun/kernels/vmlinux-<version>. One-time setup, then the daemon auto-discovers it.

You can now run same OCI images as containers or Firecracker microVMs

⚡ Community Insights

Discussion (6 Comments)Read Original on HackerNews