The Kubernetes team advises to “ make sure your worker nodes are using a supported container runtime ”, which means testing containers on other than Docker engines.ĭocker images are expected to run well in other engines. Things are about to change and by the end of 2021 is when things are expected to stop working. In the beginning, there will be just a warning message about the incoming drop of support. so many things will change, but at least we can trust this as a foundation of modern cloud native computing.ĭoing nothing is not something that will suddenly destroy your business applications once the depreciation happens. Prepare for the inevitableįor the majority of DevOps specialists, there’s been a hidden assumption not to worry about this pair (Kubernetes-Docker) at all. Maybe it was, but touching on such a delicate subject matter, which affects so many, deserves better answers. There’s an assumption among the hard core Kubernetes fans that everybody follows the development of Kubernetes, and this move (depreciation of Docker runtime) was inevitable at some point in time. For me, this kind of answer is unacceptable. One of the answers to the news is that nobody should have ever used Docker runtime in the first place, because it was never compatible with the CRI API and it required a proxy (shim for API translation) to make it work with Kubernetes. What to do? Was Docker runtime a bad choice, always? Now Kubernetes is making Docker even weaker in the perception of the tech community. Docker wanted to win the war of container orchestrators with their Docker Swarm and failed. Many people are learning right this very minute that there are other container engines than Docker. Right now, container means Docker, but this news from Kubernetes changed that. Kubernetes does not want to maintain a Docker shim anymore as they are not responsible for Docker development and codebase.Īnother, and probably the most important, is that it’s a successful attempt to change the mindsets of DevOps and developers. The more components have to be maintained, the less secure the solution is because of the increased attack surface. Why is Kubernetes dropping support for the Docker engine? The same applies for Docker container registries, such as Docker Hub it won’t be deemed obsolete by this move. Docker means that it is the file format of the containers (metadata, files inside the container, to lesser extent configuration) and that this is not going to be affected by this recent move from Kubernetes.
![docker on kubernetes docker on kubernetes](https://thecustomizewindows.com/wp-content/uploads/2019/04/What-is-the-Relationship-Between-Microservices-Docker-Kubernetes.png)
They will be executed by another container runtime and be compliant with CRI.
DOCKER ON KUBERNETES HOW TO
So what’s going to happen to all the containers everybody created? All these DOCKERFILE files that define how to build Docker containers as the primary deployment method?Ĭlose to nothing is happening to them. Yes, there are other container runtimes which implement the now famous Container Runtime Interface (CRI), which Docker does not. “ We encourage you to evaluate moving to a container runtime that is a full-fledged implementation of CRI (v1alpha1 or v1 compliant) as they become available. And let’s not forget Apache Mesos, which was the thing before the meteoric rise to popularity of Kubernetes.īut this kind of migration is not necessary, and I’m going to explain why. For instance, Docker’s own Docker Swarm, which is not expected to drop support for Docker, for quite obvious reasons. So unless someone invested heavily in Kubernetes (like most of the enterprises have), it is possible to run Docker containers without Kubernetes. → Avenga about Kubernetes – how hot can it get? There are other alternatives for container orchestration, and despite Kubernetes winning the mindsets and market share, there are still other viable options.
![docker on kubernetes docker on kubernetes](https://cdn.ttgtmedia.com/rms/onlineimages/serverside-how_kubernetes_works-f_mobile.png)
The question is not as absurd as it may sound. Let’s analyze what it means and what we are supposed to do about it. You need to pay attention to this and plan for it. Ian Coldwater, Kubernetes SIG Security, wrote on his twitter account: “ Docker support is being deprecated in Kubernetes. Yes, it’s true, Kubernetes will deprecate the Docker runtime, starting from version 1.20. Until the news broke out about the deprecation of Docker shim in Kubernetes 1.20. It seemed to be inevitable that they both work together and are tightly bound together, forever.