[Blockbuster]!!

KubernetesThe latest version is no longer supportedDocker.

At first hearing the news, I was also shocked. A mouthful of old blood almost choked me

K8s, Google and Red Hat will no longer support Docker…

And so on…

K8s no longer supports Docker and Google, so what does red Hat matter? Here is a long word, we see the end of the article related to my previous article ** “K8S extremely brief history” ** good.

K8s no longer supports Docker.

K8s uses the Container Runtime to communicate with k8S. However, Docker does not support the Container Runtime, so k8S has to write a Dockershim plug-in. Make a network bridge in the middle, transform the flow of information. You can refer to more details

Dev. To/Inductor /wa…

www.infoq.cn/article/rOh…

There is a reason why Docker is so strong. At the beginning of its popularity, early Docker was almost a proxy for containerization, so that many novices thought that Docker was container and container was Docker. In history, there was only one such awesome product, the Simmons mattress.

After dominating the environment construction site, Docker found the environment layout market, which caused a serious conflict of interest with CoreOS, the early container layout leader and his old friend. As a result, the two companies ended up on the road of separation. However, CoreOS did not have containerized products. In order to compete with Docker, CoreOS broke off relations with Docker and developed its own product Rocket.

However, At this time, Docker was undisputable in the container market, and there was no market for other container products.

At that time, Docker proved what is popular and prosperous, and money is nothing. After abandoning CoreOS, its old comrare-in-arms, Docker bought up compose, which is now being used all the time, and its early prototype was actually Fig. At this time, Docker has the momentum of dominating the service market.

Google and RedHat, looking at the kids at that time, showed signs of turning against themselves in a blink of an eye. After such development, Docker will eventually dominate the containerization + choreography market, and it is impossible to give up the trillions of market to others.

Finally, CoreOS, Google and RedHat joined forces to overthrow the OCI community established by Docker and set up CNCF. At the same time, Google was forced to show its talent and open the borg, a killer weapon it had been researching for 15 years, to the community after changing its name to Kubernetes.

However, considering that Docker is compatible with Docker, and Docker has a dominant voice in the container market. Does not open its own Container Runtime.

Docker did not compromise, launching its own Swarm choreography tool in an attempt to compete, and did not initially support K8S.

Finally, with the strong promotion of K8S in the community, Docker had to compromise and announced to abandon Swarm and fully embrace K8S in 2016.

Meanwhile, Docker hasn’t given up on the brink of death. Change the name of the Docker project to Moby and register Docker as the company’s name.

Well, anyway. Fire on the wall brings disaster to the fish in the pond…

In the end, it’s our honest technology that hurts the most. Just finished with Docker, it’s time to work on runtime.

But my personal estimate is that there won’t be much change at the Kubectl level, so you can rest easy on that.

For more exciting content, please visit me at my official account: Linux178. 200+ high-quality original articles waiting for you