Kubernetes has announced that it will deprecate Docker as a container runtime after version 1.20, but this change does not affect users who manage their own clusters or use managed services like CAST AI, which can continue to run Docker images without issue. The reason for this change is that Docker's API is incompatible with Kubernetes' Container Runtime Interface (CRI), and Kubernetes wants a unified API for different container runtimes. This means that users will need to switch to other compliant container runtimes like containerd or CRI-O, but their existing development flows that include building Docker images for running on Kubernetes do not need to change. However, relying on the underlying docker socket may break certain workflows, and there are alternative options available for this specific use case.