From 800f1b588dbc2696ee7a9bc4ee7daa3ad5608cd0 Mon Sep 17 00:00:00 2001
From: Harsh Choudhary <shry.harsh@gmail.com>
Date: Tue, 18 Apr 2017 14:42:26 +0530
Subject: [PATCH] Correct secret creation command

Private Registry FQDN also needs to be included in secret creation, otherwise Kubernetes will not be able to pull images.
---
 .../configure-pod-container/pull-image-private-registry.md   | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/tasks/configure-pod-container/pull-image-private-registry.md b/docs/tasks/configure-pod-container/pull-image-private-registry.md
index cfac48989f..de1d5b54e2 100644
--- a/docs/tasks/configure-pod-container/pull-image-private-registry.md
+++ b/docs/tasks/configure-pod-container/pull-image-private-registry.md
@@ -47,10 +47,11 @@ The output contains a section similar to this:
 
 Create a Secret named `regsecret`:
 
-    kubectl create secret docker-registry regsecret --docker-username=<your-name> --docker-password=<your-pword> --docker-email=<your-email>
+    kubectl create secret docker-registry regsecret --docker-server=<your-registry-server> --docker-username=<your-name> --docker-password=<your-pword> --docker-email=<your-email>
 
 where:
 
+* `<your-registry-server>` is your Private Docker Registry FQDN.
 * `<your-name>` is your Docker username.
 * `<your-pword>` is your Docker password.
 * `<your-email>` is your Docker email.
@@ -87,7 +88,7 @@ readable format:
 
 The output is similar to this:
 
-    {"https://index.docker.io/v1/":{"username":"janedoe","password":"xxxxxxxxxxx","email":"jdoe@example.com","auth":"c3RldmU1MzpTdGV2ZURvY2tAIzE2"}}
+    {"yourprivateregistry.com":{"username":"janedoe","password":"xxxxxxxxxxx","email":"jdoe@example.com","auth":"c3RldmU1MzpTdGV2ZURvY2tAIzE2"}}
 
 Notice that the secret data contains the authorization token from your
 `config.json` file.