At v1.20, you will get a deprecation warning for Docker.

If you’re rolling your own clusters, you will also need to make changes to avoid Please work with your service provider to ensure proper upgrade If you have nodeĬustomizations you may need to update them based on your environment and runtime Make sure your worker nodes are using a supported container runtime beforeĭocker support is removed in a future version of Kubernetes. If you’re using a managed Kubernetes service like GKE, EKS, or AKS (which defaults to containerd) you will need to Tool for building containers, and the images that result from running docker build can still run in your Kubernetes cluster. Shouldn’t, use Docker as a development tool anymore. This doesn’t mean the death of Docker, and it doesn’t mean you can’t, or If you’re an end-user of Kubernetes, not a whole lot will be changing for you. Docker-produced images will continue to work in yourĬluster with all runtimes, as they always have. That use the Container Runtime Interface (CRI)Ĭreated for Kubernetes.

TL DR Docker as an underlying runtime is being deprecated in favor of runtimes Authors: Jorge Castro, Duffie Cooley, Kat Cosgrove, Justin Garrison, Noah Kantrowitz, Bob Killen, Rey Lejano, Dan “POP” Papandrea, Jeffrey Sica, Davanum “Dims” Srinivas