From 8b00a588c4cb1f8ffbe79cc112eea2a770aed8b1 Mon Sep 17 00:00:00 2001 From: makocchi Date: Thu, 19 Jul 2018 08:50:49 +0900 Subject: [PATCH] tweak crictl.md (#9349) --- .../docs/tasks/debug-application-cluster/crictl.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/content/en/docs/tasks/debug-application-cluster/crictl.md b/content/en/docs/tasks/debug-application-cluster/crictl.md index 53874f40a72..39418bcaac0 100644 --- a/content/en/docs/tasks/debug-application-cluster/crictl.md +++ b/content/en/docs/tasks/debug-application-cluster/crictl.md @@ -56,7 +56,7 @@ To view or edit the current configuration, view or edit the contents of `/etc/crictl.yaml`. ```sh -$ cat /etc/crictl.yaml +cat /etc/crictl.yaml runtime-endpoint: unix:///var/run/dockershim.sock image-endpoint: unix:///var/run/dockershim.sock timeout: 10 @@ -68,7 +68,7 @@ debug: true The following examples show some `crictl` commands and and example output. {{< warning >}} -If you use `crictl` to create pod sandboxes or containers on a running +**Warning:** If you use `crictl` to create pod sandboxes or containers on a running Kubernetes cluster, the Kubelet will eventually delete them. `crictl` is not a general purpose workflow tool, but a tool that is useful for debugging. {{< /warning >}} @@ -309,8 +309,14 @@ crictl start 3e025dd50a72d956c4f14881fbb5b1080c9275674e95fb67f965f6478a957d60 ``` ```none 3e025dd50a72d956c4f14881fbb5b1080c9275674e95fb67f965f6478a957d60 +``` -$ crictl ps +Check the container has its state set to `Running`. + +```bash +crictl ps +``` +```none CONTAINER ID IMAGE CREATED STATE NAME ATTEMPT 3e025dd50a72d busybox About a minute ago Running busybox 0 ``` @@ -323,4 +329,4 @@ CONTAINER ID IMAGE CREATED STATE See [kubernetes-incubator/cri-tools](https://github.com/kubernetes-incubator/cri-tools) for more information. -{{% /capture %}} \ No newline at end of file +{{% /capture %}}