RedHat and Kubernetes essentially deprecating Docker (and adding unbelievable amounts of code to replace it as infrastructure) just means a central entity calls the shots now.
Err, the concept of containers aren't being deprecated. At first, Kubernetes only supported Docker. This was considered a negative monopoly, so they defined the CRI (Container Runtime Interface) and started shifting towards that. Now they're just taking the sensible step of deprecating the old specific support for Docker. Docker is still free to implement CRI (and IIRC there have been motions towards this). Containerd (Docker's underlying runtime) already supports it today.
Your Docker images will also keep working. Even if Docker doesn't end up implementing CRI, both containerd and CRI-O use the same container format, and are compatible with your existing images.
Comments
Err, the concept of containers aren't being deprecated. At first, Kubernetes only supported Docker. This was considered a negative monopoly, so they defined the CRI (Container Runtime Interface) and started shifting towards that. Now they're just taking the sensible step of deprecating the old specific support for Docker. Docker is still free to implement CRI (and IIRC there have been motions towards this). Containerd (Docker's underlying runtime) already supports it today.
Your Docker images will also keep working. Even if Docker doesn't end up implementing CRI, both containerd and CRI-O use the same container format, and are compatible with your existing images.