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

You can now run same OCI images as containers or Firecracker microVMs(github.com)

43 points by pullrun 5 hours ago | 15 comments

aliasxneo 1 hour ago |

Is the OP the author of this? Because they are writing responses here that are unquestionably unedited LLM generated responses. The project looks cool, and I'm particularly glad to see a reach for a p2p container registry, but that sort of behavior doesn't lend credibility to something as critical as image infrastructure.

wiether 1 hour ago | |

I hate how I feel about this: the sole contributor's account is not 2 month old, and yet they have created an org for this project, with all the bells and whistles in the README.

To me, a project that young, with a unique developer at the helm, cannot look "that nice", so I can't resist seeing it as too nice to be true, and being actually a scam or whatever.

I know that, thanks to AI, a solo dev can not only orchestrate an actual projects in a few days, but can ALSO take time to make a good looking README.

When, in the past, the focus was first on the code, then on the README.

add-sub-mul-div 1 hour ago | |

It looks like OP only has an account here to self-promote, which also puts them in the same credibility tier as an advertiser.

themgt 51 minutes ago | | |

There's actually two additional sockpuppet accounts (liquid64 / yakimbo90) in here self-promoting. Whole thing is throwing off a ton of red flags.

aliasxneo 1 hour ago | | |

You're right, this is a duplicate of: https://news.ycombinator.com/item?id=48910087.

vaylian 2 hours 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 3 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.

jtbaker 1 hour ago | |

I think `smolvm` may fit the bill? I've been using it to run pi.dev in a sandbox.

https://smolmachines.com/

ranger_danger 1 hour ago | | |

I tried smolvm, and built several single binaries with it for different distros. Less than a month later, those same binaries now silently exit with code 0 and I have absolutely no idea what's wrong or how to diagnose.

thepoet 2 hours ago | |

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

Currently we have to supply a kernel to run the OCI as a microVM with a warm pool.

  TARIT_KERNEL=/path/vmlinux

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

liquid64 3 hours 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.

ktm5j 1 hour ago | | |

I don't think I've ever seen a kernel or initrd in a container image. The whole point of containers is not to duplicate the kernel, and you definitely don't need an initial ram disk since you already have a running operating system.

spwa4 3 hours ago | | |

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