gscrivano
Re:Crun: Fast and lightweight OCI runtime and C library for running co...
on Monday June 05, 2023 @10:48AM (#36196933)
being the main author of crun, I can clarify that statement: I am not a fan of Go _for this particular use case_.
Using C instead of Go avoided a bunch of the workarounds that exists in runc to workaround the Go runtime, e.g. https://github.com/opencontainers/runc/blob/main/libcontaine...
Re:Crun: Fast and lightweight OCI runtime and C library for running co...
on Monday June 05, 2023 @10:45AM (#36196872)
crun is not a setuid program
Re:Podman vs. Docker: Comparing the two containerization tools
on Thursday February 23, 2023 @07:22AM (#34909520)
Podman and CRI-O share the low level libraries (namely containers/image and containers/storage).
crun is Tech Preview in OpenShift 4.12: https://cloud.redhat.com/blog/whats-new-in-red-hat-openshift...
Re:Crun: Fully featured OCI runtime and C library for running containers
on Sunday January 31, 2021 @06:14AM (#25977940)
I am the author of Crun and the name was chosen to emphasize it is in C, compete with runc and still read like "container run".
In retrospect, I could have chosen a better one.
Re:Crun: Fully featured OCI runtime and C library for running containers
on Sunday January 31, 2021 @06:11AM (#25977919)
crun runs the OCI validations tests on each PR.
The tests are maintained here: https://github.com/opencontainers/runtime-tools/tree/master/...
I guess this is the closest to be "certified compliant", but that is not enough for working with existing container engines as everyone just assumes runc is used
Re:Deep dive into runc and OCI specifications
on Thursday April 30, 2020 @05:32PM (#23036401)
The OCI runtime cost is so small that I do not expect any measurable difference in a cluster.