Update to use CRI

Author: adisky

contributors/devel/running-locally.md

@@ -5,7 +5,7 @@ Getting started locally
 
 - [Requirements](#requirements)
     - [Linux](#linux)
-    - [Docker](#docker)
+    - [Container Runtime](#container-runtime)
     - [etcd](#etcd)
     - [go](#go)
     - [OpenSSL](#openssl)
@@ -27,11 +27,9 @@ Getting started locally
 
 Not running Linux? Consider running [Minikube](https://kubernetes.io/docs/setup/learning-environment/minikube/), or on a cloud provider like [Google Compute Engine](https://kubernetes.io/docs/setup/production-environment/turnkey/gce/).
 
-### Docker
+### Container Runtime
 
-You will need [Docker](https://docs.docker.com/get-docker/) installed, at least version 17.03. Check the [Kubernetes release notes](https://kubernetes.io/docs/setup/release/notes/) for information about supported Docker versions.
-
-Ensure the Docker daemon is running and can be contacted with `docker ps`. Some of the Kubernetes components need to run as root, which normally works fine with docker.
+You will need a [Container Runtime](https://kubernetes.io/docs/setup/production-environment/container-runtimes/) like [Containerd](https://github.com/containerd/containerd) or [CRI-O](https://github.com/cri-o/cri-o) installed and running.
 
 ### etcd
 
@@ -68,6 +66,11 @@ The `--depth=1` parameter is optional and will ensure a smaller download.
 
 ## Starting the cluster
 
+Set the endpoint for container runtime e.g. containerd
+```sh
+export CONTAINER_RUNTIME_ENDPOINT="unix:///run/containerd/containerd.sock"
+```
+
 In a separate tab of your terminal, run the following:
 
 ```sh