4 ms·
I think people are missing the contribution of bootc and composefs. This is a big part of what undergirds Red Hat's new 'image mode' means of deployment. They'r
by j1mc 2y ago
I think people are missing the contribution of bootc and composefs. This is a big part of what undergirds Red Hat's new 'image mode' means of deployment. They're using container-related tooling to deploy whole operating systems, and it's a large part of where they're headed.
I write this to say, "This is not them dumping abandonware." To me, it's them putting these technologies under the supervision of a neutral third party to encourage adoption.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- jauntywundrkind 2y agoComposefs has a totally crucial feature that sold me immediately, which is that if two containers use the same file, the kernel can serve that file from the same page cache. This means you can hypothetically launch a lot of containers, and if they share some layers/base images, the memory usage can still be quite reasonable. Nice. https://github.com/containers/composefs?tab=readme-ov-file#backing-store-shared-on-disk-and-in-page-cache https://github.com/containers/composefs?tab=readme-ov-file#b...
- ChocolateGod 2y agoIf you swap to a content-based object store for container images (like OSTree/Flatpak), you could potentially save a lot of disk space too because you'll no longer need to be careful about your Dockerfile layers. If two OCI images share the same file, they'll be de-duplicated on disk and only be downloaded once.
- deleted 2y ago[deleted]