crun

Disclaimer: I work for Red Hat, but I don't code or design any of the things you've mentioned here. Opinions are my own. I think I just gave you your first ever upvote on HN! Thanks for this post, it's great discussion. Regarding Postfix/systemd issues, you should take a look at ubi-init image. It has a minimal systemd in it to address problems like that[1][2]. Regarding crun, have you looked at the "Why another implementation" in the crun README.md by chance?[3] Or have you read the blog post about it that goes into a lot more detail?[4] I totally agree with the dislike toward fragmentation. I myself have been very critical of NIH and fragmentation when it happens. I do think there's an interesting case to be made for crun though. [1]: https://developers.redhat.com/products/rhel/ubi [2]: https://catalog.redhat.com/software/contain

In addition to runc, I'd like to point out an alternative OCI runtime implementation, crun (https://github.com/containers/crun). You can play with both either directly, or through Podman (https://podman.io/) Useful for cgroups v2 too.

Podman can use runc or their own runtime crun https://github.com/containers/crun so it should be able to work without much drama :tm:

Can anyone share their experiences using the 'crun' container runtime (alternative to 'runc') in their clusters? (it's mentioned way down near the end of the article, and looks like it is less resource-intensive) [1] - https://github.com/containers/crun

Podman with the new crun[1] container runtime is pretty lightweight. Everything circles back to C. [1]: https://github.com/containers/crun