From 2b2fb7d84b0497146d07db10a1a1a2f919711e8b Mon Sep 17 00:00:00 2001 From: Suraj Deshmukh Date: Thu, 19 Oct 2017 22:36:48 +0530 Subject: [PATCH] add instructions to install ps utility (#5936) The doc asks users to use `ps` command inside the nginx container, when ps is not installed inside the container. So this commit adds that command to install ps. --- .../communicate-containers-same-pod-shared-volume.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md b/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md index 2edb8e379b..e64076b035 100644 --- a/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md +++ b/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md @@ -88,6 +88,8 @@ Get a shell to nginx Container: In your shell, verify that nginx is running: + root@two-containers:/# apt-get update + root@two-containers:/# apt-get install curl procps root@two-containers:/# ps aux The output is similar to this: @@ -98,8 +100,6 @@ The output is similar to this: Recall that the debian Container created the `index.html` file in the nginx root directory. Use `curl` to send a GET request to the nginx server: - root@two-containers:/# apt-get update - root@two-containers:/# apt-get install curl root@two-containers:/# curl localhost The output shows that nginx serves a web page written by the debian container: