Open ianlewis opened 4 years ago
If you use kubeadm with Docker installed then it prefers the docker.sock rather than CRI via containerd.sock. Using docker's socket file means that the runtime can't support CRI runtime handlers.
Issue found in #46. Should consider submitting an issue to kubeadm to see if we can't make them prefer the containerd.sock over docker.sock
If you use kubeadm with Docker installed then it prefers the docker.sock rather than CRI via containerd.sock. Using docker's socket file means that the runtime can't support CRI runtime handlers.