It looks like runC is a tool built by Docker specifically to begin decoupling the codebase. This to me suggests that Docker is heading in a direction to address the issues mentioned and fixed with podman.
Basically docker is opensource and working to create its own competition.
I will add something more in your comment .
The Open Container Initiative (OCI)
Following Docker's release, a large community emerged around the idea of using containers as the standard unit of software delivery. As companies started using containers to package and deploy their software more and more, Docker's container runtime did not meet all technical and business needs that engineering teams could have. In response to this, the community started developing new runtimes with different implementations and capabilities. Simultaneously, new tools for building container images aimed to improve on Docker's speed or ease of use. To make sure that all container runtimes could run images produced by any build tool, the community started the Open Container Initiative — or OCI — to define industry standards around container image formats and runtimes.
Docker's original image format has become the OCI Image Specification, and various open-source build tools support it, including:
.... Read more... here .... padok.fr/en/blog/container-docker-oci
It looks like runC is a tool built by Docker specifically to begin decoupling the codebase. This to me suggests that Docker is heading in a direction to address the issues mentioned and fixed with podman.
Basically docker is opensource and working to create its own competition.
docker.com/blog/runc/
I will add something more in your comment .
The Open Container Initiative (OCI)
Following Docker's release, a large community emerged around the idea of using containers as the standard unit of software delivery. As companies started using containers to package and deploy their software more and more, Docker's container runtime did not meet all technical and business needs that engineering teams could have. In response to this, the community started developing new runtimes with different implementations and capabilities. Simultaneously, new tools for building container images aimed to improve on Docker's speed or ease of use. To make sure that all container runtimes could run images produced by any build tool, the community started the Open Container Initiative — or OCI — to define industry standards around container image formats and runtimes.
Docker's original image format has become the OCI Image Specification, and various open-source build tools support it, including:
.... Read more... here .... padok.fr/en/blog/container-docker-oci
Docker is also moving to rootless. Yesterday there was a very talk about that in DockerCon by runC's maintainer.
Here's the link:
youtube.com/watch?v=uWURUtqLiqQ
+1 thanks Thomas