From f1966a871886d9a1d82ca752b5163fc9d5d57b89 Mon Sep 17 00:00:00 2001 From: Satnam Singh Date: Sun, 19 Jul 2015 00:18:12 +0100 Subject: [PATCH] Fix console output formatting for images doc --- docs/user-guide/images.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/user-guide/images.md b/docs/user-guide/images.md index d1fe4ef7e5b..aca1fb1136c 100644 --- a/docs/user-guide/images.md +++ b/docs/user-guide/images.md @@ -116,7 +116,7 @@ example, run these on your desktop/laptop: Verify by creating a pod that uses a private image, e.g.: -``` +```yaml $ cat < /tmp/private-image-test-1.yaml apiVersion: v1 kind: Pod @@ -136,14 +136,14 @@ $ If everything is working, then, after a few moments, you should see: -``` +```console $ kubectl logs private-image-test-1 SUCCESS ``` If it failed, then you will see: -``` +```console $ kubectl describe pods/private-image-test-1 | grep "Failed" Fri, 26 Jun 2015 15:36:13 -0700 Fri, 26 Jun 2015 15:39:13 -0700 19 {kubelet node-i2hq} spec.containers{uses-private-image} failed Failed to pull image "user/privaterepo:v1": Error: image user/privaterepo:v1 not found ``` @@ -189,7 +189,7 @@ Kubernetes supports specifying registry keys on a pod. First, create a `.dockercfg`, such as running `docker login `. Then put the resulting `.dockercfg` file into a [secret resource](secrets.md). For example: -``` +```console $ docker login Username: janedoe Password: ●●●●●●●●●●● @@ -227,7 +227,7 @@ This process only needs to be done one time (per namespace). Now, you can create pods which reference that secret by adding an `imagePullSecrets` section to a pod definition. -``` +```yaml apiVersion: v1 kind: Pod metadata: