@@ -203,8 +203,9 @@ You have several choices for Kubernetes images:
203203 - Useful if you are using a private registry.
204204 - The release contains files such as ` ./kubernetes/server/bin/kube-apiserver.tar ` which
205205 can be converted into docker images using a command like
206- ` tar -C kube-apiserver -c . | docker import - kube-apiserver `
207- - * TODO* : test above command.
206+ ` docker load -i kube-apiserver.tar `
207+ - You can verify if the image is loaded successfully with the right reposity and tag using
208+ command like ` docker images `
208209
209210For etcd, you can:
210211- Use images hosted on Google Container Registry (GCR), such as ` gcr.io/google_containers/etcd:2.0.12 `
@@ -373,8 +374,18 @@ installation, by following examples given in the Docker documentation.
373374### rkt
374375
375376[ rkt] ( https://github.com/coreos/rkt ) is an alternative to Docker. You only need to install one of Docker or rkt.
377+ The minimum version required is [ v0.5.6] ( https://github.com/coreos/rkt/releases/tag/v0.5.6 ) .
376378
377- * TODO* : how to install and configure rkt.
379+ [ systemd] ( http://www.freedesktop.org/wiki/Software/systemd/ ) is required on your node to run rkt. The
380+ minimum version required to match rkt v0.5.6 is
381+ [ systemd 215] ( http://lists.freedesktop.org/archives/systemd-devel/2014-July/020903.html ) .
382+
383+ [ rkt metadata service] ( https://github.com/coreos/rkt/blob/master/Documentation/networking.md ) is also required
384+ for rkt networking support. You can start rkt metadata service by using command like
385+ ` sudo systemd-run rkt metadata-service `
386+
387+ Then you need to configure your kubelet with flag:
388+ - ` --container_runtime=rkt `
378389
379390### kubelet
380391
0 commit comments