Comment # 1 on bug 1214406 from Egbert Eich

I was partly wrong with my assessment in item 1. in above description:
It is perfectly fine to use crio runtime - however, it needs to be enabled and
running at the time `kubeadm init` runs.
Thus, this should be set in a postinstall script.
NOTE: before doing so it should be checked if another container runtime
(containerd) is already enabled (or even running). It it is running, nothing
should be done (ie crio should not be touched). If it is just enabled, it
should be started.