You can now run same OCI images as containers or Firecracker microVMs
1–10 of 45 posts
Re: You can now run same OCI images as containers or Firecracker microVMs
#2[deleted]
Re: You can now run same OCI images as containers or Firecracker microVMs
#3Where 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.
Re: You can now run same OCI images as containers or Firecracker microVMs
#4Where 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.
[deleted]
Re: You can now run same OCI images as containers or Firecracker microVMs
#5Where 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.
[deleted]
Re: You can now run same OCI images as containers or Firecracker microVMs
#6Where 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
#7Where 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.
And if they don't have a kernel? You just specify kernel + initrd?
Re: You can now run same OCI images as containers or Firecracker microVMs
#8Earlier 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.
And if they don't have a kernel? You just specify kernel + initrd?
[deleted]
Re: You can now run same OCI images as containers or Firecracker microVMs
#9Earlier 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.
And if they don't have a kernel? You just specify kernel + initrd?
[deleted]
Re: You can now run same OCI images as containers or Firecracker microVMs
#10Earlier 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.
And if they don't have a kernel? You just specify kernel + initrd?
[deleted]