OpenShift Container Platform uses CRI-O as the container engine and runC or crun as the container runtime. Podman is only directly used for the openshift-instal

OpenShift Container Platform uses CRI-O as the container engine and runC or crun as the container runtime. Podman is only directly used for the openshift-installer, but as a container management tool uses the same underlying runtimes. This means they share the same long tenure in production when it comes to using runc. Is that what you meant? https://docs.openshift.com/container-platform/4.14/nodes/containers/nodes-containers-using.html#:~:text=OpenShift%20Container%20Platform%20uses%20CRI,Initiative%20(OCI)%20runtime%20specifications https://docs.openshift.com/container-platform/4.14/nodes/con.... https://docs.podman.io/en/latest/#:~:text=Podman%20relies%20on%20an%20OCI%20compliant%20Container%20Runtime https://docs.podman.io/en/latest/#:~:text=Podman%20relies%20.... The answer is a little bit more nuanced, as the defaults differ. Podman uses crun by default: https://podman.io/docs/installation#:~:text=crun%20%2F%20runc%E2%80%8B,for%20example%20on%20Ubuntu%2022.04 https://podman.io/docs/installation#:~:text=crun%20%2F%20run.... For OpenShift the use of crun is available as a Technology Preview: https://www.redhat.com/en/blog/whats-new-in-red-hat-openshift-4.12-blog https://www.redhat.com/en/blog/whats-new-in-red-hat-openshif... since 4.12. The default for 4.14 is still runC. Notwithstanding, Podman is gaining a lot of momentum, especially now with Podman Desktop. Disclaimer: I work for Red Hat on the Podman Machine and OpenShift Local/CRC teams to provide integration with Podman Desktop aiming at developer usecases