From 5588e0ce24bde87b48a78cb85c17585b3dbe4e26 Mon Sep 17 00:00:00 2001 From: Mengjiao Liu Date: Thu, 14 Apr 2022 18:43:20 +0800 Subject: [PATCH] [zh]Sync debug-application.md --- .../tasks/debug-application-cluster/debug-application.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/zh/docs/tasks/debug-application-cluster/debug-application.md b/content/zh/docs/tasks/debug-application-cluster/debug-application.md index 2e71c22af0..99678b817a 100644 --- a/content/zh/docs/tasks/debug-application-cluster/debug-application.md +++ b/content/zh/docs/tasks/debug-application-cluster/debug-application.md @@ -102,8 +102,9 @@ If a Pod is stuck in the `Waiting` state, then it has been scheduled to a worker 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. -* Have you pushed the image to the repository? -* Run a manual `docker pull ` on your machine to see if the image can be pulled. +* Have you pushed the image to the registry? +* Try to manually pull the image to see if the image can be pulled. For example, + if you use Docker on your PC, run `docker pull `. --> #### Pod 停滞在 Waiting 状态 @@ -113,7 +114,7 @@ Again, the information from `kubectl describe ...` should be informative. The m * 确保镜像名字拼写正确 * 确保镜像已被推送到镜像仓库 -* 用手动命令 `docker pull <镜像>` 试试看镜像是否可拉取 +* 尝试手动是否能拉取镜像。例如，如果你在你的 PC 上使用 Docker，请运行 `docker pull <镜像>`。