From 408d8d610ef6c3238a0ab2078fd1b39b23639710 Mon Sep 17 00:00:00 2001 From: Anthony Date: Tue, 15 Aug 2017 20:10:47 +0800 Subject: [PATCH] Update debug-application.md add "." to the sentence --- docs/tasks/debug-application-cluster/debug-application.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/debug-application-cluster/debug-application.md b/docs/tasks/debug-application-cluster/debug-application.md index 8b37fe7aa2..5a129be1d1 100644 --- a/docs/tasks/debug-application-cluster/debug-application.md +++ b/docs/tasks/debug-application-cluster/debug-application.md @@ -57,7 +57,7 @@ scheduled. In most cases, `hostPort` is unnecessary, try using a Service object If a Pod is stuck in the `Waiting` state, then it has been scheduled to a worker node, but it can't run on that machine. Again, the information from `kubectl describe ...` should be informative. The most common cause of `Waiting` pods is a failure to pull the image. There are three things to check: -* Make sure that you have the name of the image correct +* Make sure that you have the name of the image correct. * Have you pushed the image to the repository? * Run a manual `docker pull ` on your machine to see if the image can be pulled.