github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-03 09:22:44 +00:00
Code Issues Projects Releases Wiki Activity

Improve markdown highlighting in the rkt getting started guide.

Browse Source
This commit is contained in:
Alex Robinson 2015-07-18 18:53:23 -07:00
parent 51247069e4
commit 6ae88fc1dc
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/getting-started-guides/rkt/README.md
View File

@ -49,13 +49,13 @@ We still have [a bunch of work](https://github.com/GoogleCloudPlatform/kubernete
To start the `rkt metadata service`, you can simply run: To start the `rkt metadata service`, you can simply run:
```shell ```console
$ sudo rkt metadata-service $ sudo rkt metadata-service
``` ```
If you want the service to be running as a systemd service, then: If you want the service to be running as a systemd service, then:
```shell ```console
$ sudo systemd-run rkt metadata-service $ sudo systemd-run rkt metadata-service
``` ```
@ -66,7 +66,7 @@ We still have [a bunch of work](https://github.com/GoogleCloudPlatform/kubernete
To use rkt as the container runtime, you just need to set the environment variable `CONTAINER_RUNTIME`: To use rkt as the container runtime, you just need to set the environment variable `CONTAINER_RUNTIME`:
```shell ```console
$ export CONTAINER_RUNTIME=rkt $ export CONTAINER_RUNTIME=rkt
$ hack/local-up-cluster.sh $ hack/local-up-cluster.sh
``` ```
@ -75,7 +75,7 @@ $ hack/local-up-cluster.sh
To use rkt as the container runtime for your CoreOS cluster on GCE, you need to specify the OS distribution, project, image: To use rkt as the container runtime for your CoreOS cluster on GCE, you need to specify the OS distribution, project, image:
```shell ```console
$ export KUBE_OS_DISTRIBUTION=coreos $ export KUBE_OS_DISTRIBUTION=coreos
$ export KUBE_GCE_MINION_IMAGE=<image_id> $ export KUBE_GCE_MINION_IMAGE=<image_id>
$ export KUBE_GCE_MINION_PROJECT=coreos-cloud $ export KUBE_GCE_MINION_PROJECT=coreos-cloud
@ -84,13 +84,13 @@ $ export KUBE_CONTAINER_RUNTIME=rkt
You can optionally choose the version of rkt used by setting `KUBE_RKT_VERSION`: You can optionally choose the version of rkt used by setting `KUBE_RKT_VERSION`:
```shell ```console
$ export KUBE_RKT_VERSION=0.5.6 $ export KUBE_RKT_VERSION=0.5.6
``` ```
Then you can launch the cluster by: Then you can launch the cluster by:
```shell ```console
$ kube-up.sh $ kube-up.sh
``` ```
@ -100,7 +100,7 @@ Note that we are still working on making all containerized the master components
To use rkt as the container runtime for your CoreOS cluster on AWS, you need to specify the provider and OS distribution: To use rkt as the container runtime for your CoreOS cluster on AWS, you need to specify the provider and OS distribution:
```shell ```console
$ export KUBERNETES_PROVIDER=aws $ export KUBERNETES_PROVIDER=aws
$ export KUBE_OS_DISTRIBUTION=coreos $ export KUBE_OS_DISTRIBUTION=coreos
$ export KUBE_CONTAINER_RUNTIME=rkt $ export KUBE_CONTAINER_RUNTIME=rkt
@ -108,19 +108,19 @@ $ export KUBE_CONTAINER_RUNTIME=rkt
You can optionally choose the version of rkt used by setting `KUBE_RKT_VERSION`: You can optionally choose the version of rkt used by setting `KUBE_RKT_VERSION`:
```shell ```console
$ export KUBE_RKT_VERSION=0.5.6 $ export KUBE_RKT_VERSION=0.5.6
``` ```
You can optionally choose the CoreOS channel by setting `COREOS_CHANNEL`: You can optionally choose the CoreOS channel by setting `COREOS_CHANNEL`:
```shell ```console
$ export COREOS_CHANNEL=stable $ export COREOS_CHANNEL=stable
``` ```
Then you can launch the cluster by: Then you can launch the cluster by:
```shell ```console
$ kube-up.sh $ kube-up.sh
``` ```