tl;dr
For developers
Don't panic, Docker containers and images are still alive. It's not that it will change everything.
Als...
For further actions, you may consider blocking this person and/or reporting abuse
Another OCI Runtime -> crun
It's faster than runc (the performance gains are notable when starting containers).
Also it supports cgroups v2, runc also added support on v1.0.0-93 (which has not been launched?)
podman + crun do work very well (also podman can launch rootless containers) so I prefer to use them instead of Docker + runc.
I just moved to podman/crun due to cgroups problem
Docker phases out?
Docker 20.10 will support cgroups v2
Will, in the future. Podman does it right now and rootless containers are a huge improvement on process isolation
Docker also supports rootless now.
PSA: This doesn't mean what most people think it means. kubernetes.io/blog/2020/12/02/dont...
For dummies like me:
TL/DR: The Docker Container Runtime is history - your Docker-built containers will still run.
Just adding my 2 cents from my own experience.
At work, we are using classical RKE Rancher with Kubernetes with Docker and k3s Rancher with Kubernetes with containerd. So I have experience with both. The problem is, that in our case it often seemed like containerd, at least the way it is used with Kubernetes, is not that stable and reliable. It showed us a lot of bugs and issues, which the legacy Kubernetes never had shown.
So I'm asking myself, how can they suddenly guarantee that all this new stuff is even production ready, when we had not too many but quite substantial issues with it?
(Perhaps the issue was mainly to be found in the whole Rancher thing, but we cannot confirm this.)
Great overview, thanks!
I found this while very true kind of ironic since we're talking about kubernetes here which in itself is a very complex system. That does not invalidate the point you're making though, it just makes another case for why less complexity in an already complex system is probably a good idea.
Fantastic post. My feedback: I hope this particular Kubernetes rearchitecture saves us all time. We are getting closer to making it realistic to have a container format specific to my favorite programming language. No need for us to all be the same.
Both containerd and CRI-O know how to pull docker images and run them and Docker Images Manifest V2 and OCI image specification are almost the same, so we dont need to worry now.
But, if you want to know how to live without Docker I suggest you this video - How to live without Docker for developers - Part 1 | Migration from Docker to Buildah and Podman. Or just search Without Docker on YouTube.
So now I have to learn yet another framework (Buildah, Podman, etc) instead of just doing the easy thing and running Docker in Docker. The Kubernetes community sure loves creating new projects.
Seriously, calm down #kubernetes and #docker, what's going on guys?
A nice reference on the kubernetes blog as well for those interested in knowing more: kubernetes.io/blog/2020/12/02/dont...
Great reference!
How does one tell what runtime is currently being used in a cluster?
kubectl get node -o wideI never realized that was there. Thanks!
There is any command I can run in my cluster to check if dockershim is being used?
So, Just dockershim was deprecated?