We have Rancher High availability setup on-premises running on Docker. That means for example if I want to promote another VM to the cluster I just run provided command from docker on a fresh installed VM. For example:
sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent:v2.5.7 --server https://rancher2.example.com --token XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --worker
But now as Kubernetes has announced the end of support for a docker we wanted to test on-premises setup with ContainerD.
Therefore, my question if that would work? When the command above will be executed - than some auto deployment based on Docker is happening in the background. I doubt that those scripts provided from Rancher for deployment of Worker and ETcd’ to the cluster are compatible with ContainerD?
Does anyone have experience with ContainerD and Rancher on premises? Is it even possible?