News for hackers. Stuff that matters.
Re:Krunvm – Create MicroVMs from OCI Images by 0xbadcafebee on Tuesday August 16, 2022 @11:20AM (#32483985)
Since it's a VM, it's ideal for workloads with a set amount of resource use and that need strong isolation guarantees. Regular containers are better to share a pool of resources whose usage varies widely, and when you don't need strong isolation guarantees. Depending on how I/O is handled, container I/O can be very slow, whereas a dedicated disk snapshot without CoW/overlays would be much faster. Since this also uses TSI for networking, you will need a patched Linux kernel to use networking in the guest at all, and raw sockets don't work at all.
Re:Krunvm – Create MicroVMs from OCI Images by staticassertion on Tuesday August 16, 2022 @12:14PM (#32484868)
> Depending on how I/O is handled, container I/O can be very slow, whereas a dedicated disk snapshot without CoW/overlays would be much faster.

Do you mean VM I/O can be very slow? I don't think containers should have any overhead, please correct me if I'm wrong though.

Re:Krunvm – Create MicroVMs from OCI Images by 0xbadcafebee on Tuesday August 16, 2022 @12:41PM (#32485303)
Container file I/O is very slow. It unpacks the OCI image layers onto the regular host filesystem, then adds overlay filesystems, does copy-on-write, and references files between each layer. For example, doing 10 containerized nodejs app builds simultaneously will swamp the host with iowait. A common hack to is to put the OCI file tree / overlays on a dedicated disk with much higher iops than the boot disk.
Re:Krunvm – Create MicroVMs from OCI Images by rascul on Tuesday August 16, 2022 @07:37PM (#32490474)
> It unpacks the OCI image layers onto the regular host filesystem, then adds overlay filesystems, does copy-on-write, and references files between each layer.

That's just Docker though, right? Does LXC or systemd-nspawn do that?

Re:Krunvm – Create MicroVMs from OCI Images by staticassertion on Tuesday August 16, 2022 @03:04PM (#32487277)
Thank you, I'll have to look into this. I was thinking from a file namespacing perspective there shouldn't be overhead, but it makes sense that adding the overlay filesystems and mounts would impact performance.