docs: bootstrapping fails out of the box #1612
Description
Please describe the question or issue you're facing with "How to install Canonical Kubernetes from a snap".
I followed the sudo snap install and sudo k8s bootstrap steps but the latter failed with:
$ sudo k8s bootstrap
Bootstrap config verification failed: pre-init checks failed for node: The path '/run/containerd' required for the containerd socket already exists. This may mean that another service is already using that path, and it conflicts with the k8s snap. Please make sure that there is no other service installed that uses the same path, and remove the existing directory.(dev-only): You
Looking at the other docs (e.g., https://documentation.ubuntu.com/canonical-kubernetes/latest/snap/howto/install/dev-env/ ), it seems like the fix here is to get Canonical K8s to use a custom containerd path. But the claim is that this fix is necessary for development environments only, whereas in my case it seemed to be necessary in general.
Also, if you apply this fix, and manage to bootstrap, if you want to do anything useful with your K8s you find out you need to resize your /run mount (again, following the fix recommended in the development environment doc). Again, this means the out of the box experience fails. Related to this other issue: #1456 .
Reported from: https://documentation.ubuntu.com/canonical-kubernetes/latest/snap/howto/install/snap/