Add the --cri-socket parameter to configuration

Also fix the syntax for CRI-O, adding unix://

Author: afbjorklund

docs/alternative_runtimes.md

@@ -25,9 +25,10 @@ Or you can use the extended version:
 ```shell
 $ minikube start \
     --network-plugin=cni \
+    --cri-socket=/var/run/crio/crio.sock \
     --extra-config=kubelet.container-runtime=remote \
-    --extra-config=kubelet.container-runtime-endpoint=/var/run/crio/crio.sock \
-    --extra-config=kubelet.image-service-endpoint=/var/run/crio/crio.sock \
+    --extra-config=kubelet.container-runtime-endpoint=unix:///var/run/crio/crio.sock \
+    --extra-config=kubelet.image-service-endpoint=unix:///var/run/crio/crio.sock \
     --bootstrapper=kubeadm
 ```
 
@@ -47,8 +48,9 @@ Or you can use the extended version:
 ```shell
 $ minikube start \
     --network-plugin=cni \
+    --cri-socket=/run/containerd/containerd.sock \
     --extra-config=kubelet.container-runtime=remote \
     --extra-config=kubelet.container-runtime-endpoint=unix:///run/containerd/containerd.sock \
     --extra-config=kubelet.image-service-endpoint=unix:///run/containerd/containerd.sock \
     --bootstrapper=kubeadm
-```
+```