From c942933fe989d1598ed8dd1db8e436fb2944a75e Mon Sep 17 00:00:00 2001 From: Satnam Singh Date: Sun, 19 Jul 2015 00:48:49 +0100 Subject: [PATCH] Fix console outout of logging doc --- docs/user-guide/logging.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/user-guide/logging.md b/docs/user-guide/logging.md index 5b4208e7885..9782e39eea7 100644 --- a/docs/user-guide/logging.md +++ b/docs/user-guide/logging.md @@ -43,7 +43,7 @@ The logs of a running container may be fetched using the command `kubectl logs`. this pod specification [counter-pod.yaml](../../examples/blog-logging/counter-pod.yaml), which has a container which writes out some text to standard output every second. (You can find different pod specifications [here](logging-demo/).) -``` +```yaml apiVersion: v1 kind: Pod metadata: @@ -58,14 +58,14 @@ output every second. (You can find different pod specifications [here](logging-d we can run the pod: -``` - $ kubectl create -f ./counter-pod.yaml - pods/counter +```console +$ kubectl create -f ./counter-pod.yaml +pods/counter ``` and then fetch the logs: -``` +```console $ kubectl logs counter 0: Tue Jun 2 21:37:31 UTC 2015 1: Tue Jun 2 21:37:32 UTC 2015 @@ -79,7 +79,7 @@ $ kubectl logs counter If a pod has more than one container then you need to specify which container's log files should be fetched e.g. -``` +```console $ kubectl logs kube-dns-v3-7r1l9 etcd 2015/06/23 00:43:10 etcdserver: start to snapshot (applied: 30003, lastsnap: 20002) 2015/06/23 00:43:10 etcdserver: compacted log at index 30003