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.
[ Parent
| on HN ]
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.