gscrivano

3 ms·

1. 1.▲
   by gscrivano 3y ago

   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:/&
2. 2.▲
   by gscrivano 3y ago

   crun is not a setuid program
3. 3.▲
   by gscrivano 4y ago

   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...
4. 4.▲
   by gscrivano 6y ago

   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.
5. 5.▲
   by gscrivano 6y ago

   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&
6. 6.▲
   by gscrivano 6y ago

   The OCI runtime cost is so small that I do not expect any measurable difference in a cluster.