Earlier quoted context omitted.
you don't have to source one manually — pullrun kernel install fetches a kata containers kernel into ~/.pullrun/kernels/vmlinux- . One-time setup, then the daemon auto-discovers it.
If you run an ubuntu image with a kata kernel, do you have difficulty installing some packages? For example if you need linux-headers-$(uname -r) or linux-modules-extra-$(uname -r), it won't exist in canonical apt repos?
You can now run same OCI images as containers or Firecracker microVMs
21–30 of 45 posts
Re: You can now run same OCI images as containers or Firecracker microVMs
#22Where 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.
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.
Re: You can now run same OCI images as containers or Firecracker microVMs
#23Re: You can now run same OCI images as containers or Firecracker microVMs
#24Is 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.
Re: You can now run same OCI images as containers or Firecracker microVMs
#25Is 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.
It looks like OP only has an account here to self-promote, which also puts them in the same credibility tier as an advertiser.
Re: You can now run same OCI images as containers or Firecracker microVMs
#26Where 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.
I think `smolvm` may fit the bill? I've been using it to run pi.dev in a sandbox. https://smolmachines.com/
Re: You can now run same OCI images as containers or Firecracker microVMs
#27Earlier quoted context omitted.
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.
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.
Re: You can now run same OCI images as containers or Firecracker microVMs
#28Is 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.
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.
Re: You can now run same OCI images as containers or Firecracker microVMs
#29Is 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.
It looks like OP only has an account here to self-promote, which also puts them in the same credibility tier as an advertiser.
Re: You can now run same OCI images as containers or Firecracker microVMs
#30Earlier quoted context omitted.
you don't have to source one manually — pullrun kernel install fetches a kata containers kernel into ~/.pullrun/kernels/vmlinux- . One-time setup, then the daemon auto-discovers it.
If you run an ubuntu image with a kata kernel, do you have difficulty installing some packages? For example if you need linux-headers-$(uname -r) or linux-modules-extra-$(uname -r), it won't exist in canonical apt repos?