←back to thread

Red Hat to contribute container tech (Podman, bootc, ComposeFS...) to CNCF

(www.redhat.com)
272 points twelvenmonkeys | 2 comments | 14 Nov 24 17:59 UTC | HN request time: 0s | source
Show context
j1mc ◴[14 Nov 24 22:35 UTC] No.42141922[source]▶
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.

replies(4): >>42141926 #>>42141989 #>>42143842 #>>42149122 #
1. jauntywundrkind ◴[15 Nov 24 03:58 UTC] No.42143842[source]▶
Composefs 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#b...
replies(1): >>42145328 #
2. ChocolateGod ◴[15 Nov 24 09:41 UTC] No.42145328[source]▶
If 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.