difference-docker-containerd-runc-crio-oci/

[utterances-bot]

The differences between Docker, containerd, CRI-O and runc - Tutorial Works

Let’s answer the question of Docker or CRI-O, and other common questions about different container runtimes

https://www.tutorialworks.com/difference-docker-containerd-runc-crio-oci/

[runlevel5]

Thanks for the great post. Would you be able to provide more insight on podman too?

[yarinkos]

Thanks for this great post

[14799678]

This is so clearly to understanding those stuff. Thanks for your work.

[vimalkrishna]

Excellent article, gave me a clear understanding of the ecosystem.

[josephalbaph]

Hi! In a kubernetes cluster, can you have both containerd and CRI-O at the same time, or do you have to choose only one or the other? Can you use CRI-O images if you chose containerd?

[PradnyaPBorkar]

Excellent article.. cleared the concepts of docker n containerd and runc

[ameiji]

Thanks for the explanation. You just forgot to mention what is dockerd role in that scheme.

[frank-cq]

Nice job. Thank you

[manishdash12]

THanks for the awesome article. I have a doubt. Containerd is internally used by docker. Containerd support CRI.

Then do we still need dockershim?

[frjonsen]

Thanks for an excellent explanation for an otherwise confusing area.

@manishdash12 We do not. It was announced some time ago that dockershim is deprecated as of Kubernetes 1.20.

[zhuyijing]

this is awesome, thanks for your excellent explanation.

[abhi1202]

This is very good post, I have been searching for something like this for sometime. Simple explanation for containers and tools and interactions between them. Can you add more examples if possible on what Azure, AWS and Google is using for their Kubernetes services.

[ghost]

Thanks for this clear and short explanation!

[bhelabhav]

Firstly, this is a great article which shed light on a lot of confusing points in the container landscape. Secondly, it seems there is a bit of misrepresentation, namely of runc, as well as other lower level container runtimes. For example:

runc is an OCI-compatible container runtime. It implements the OCI specification and runs the container processes.

This statement suggests that runc itself fully satisfies the OCI specification. The misrepresentation here is twofold:

1. The article seems to never clarify that there is no "OCI specification"; rather, there are 3 OCI specifications: runtime, image, and distribution.
2. The article fails to clarify that runc only satisfies the OCI runtime specification; higher level container runtimes like containerd satisfy the OCI image specification, delegates runtime specification operations to a lower level runtime (runc in the case of containerd).

Outside of that, this article is pretty awesome. Thank you for the write-up and sharing your knowledge!

[monodot]

Thanks @singhbgithub for your excellent points. I will make these a little clearer in the next update of this article.

[zenln]

Great article thank you @manodot . Also thanks to @singhbgithub for further clarification.

As per the explanation still bit confused as per why would we not directly manipulate the runc layer from k8s vs going through containerd or crio . I think @singhbgithub s explanation gives some light into it but still bit fuzzy there.

[trevorc1653]

This was a great writeup!!! This really lifted the fog that was hovering over my brain. Many thanks Tom!!!

[azusachino]

Thank you for your great post, it helps me understand these concepts better.

[gain620]

Thanks for the great post! It helped me understand how containers work under the hood :)

[djagit]

Thanks for the explanation.

[rprodan]

Thank you for this extraordinary explanation. From my point of view your blog offers audiance a good starting point for further reseach. Additional bonus points for provided diagrams which explain more than 1000 words. Kudos!