You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/tasks/configure-pod-container/pull-image-private-registry.md
+12-9Lines changed: 12 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,8 @@ docker login
38
38
When prompted, enter your Docker ID, and then the credential you want to use (access token,
39
39
or the password for your Docker ID).
40
40
41
-
The login process creates or updates a `config.json` file that holds an authorization token. Review [how Kubernetes interprets this file](/docs/concepts/containers/images#config-json).
41
+
The login process creates or updates a `config.json` file that holds an authorization token.
42
+
Review [how Kubernetes interprets this file](/docs/concepts/containers/images#config-json).
42
43
43
44
View the `config.json` file:
44
45
@@ -60,7 +61,8 @@ The output contains a section similar to this:
60
61
61
62
{{< note >}}
62
63
If you use a Docker credentials store, you won't see that `auth` entry but a `credsStore` entry with the name of the store as value.
63
-
In that case, you can create a secret directly. See [Create a Secret by providing credentials on the command line](#create-a-secret-by-providing-credentials-on-the-command-line).
64
+
In that case, you can create a secret directly.
65
+
See [Create a Secret by providing credentials on the command line](#create-a-secret-by-providing-credentials-on-the-command-line).
64
66
{{< /note >}}
65
67
66
68
## Create a Secret based on existing credentials {#registry-secret-existing-credentials}
@@ -211,7 +213,14 @@ kubectl get pod private-reg
211
213
```
212
214
213
215
{{< note >}}
214
-
In case the Pod fails to start with the status `ImagePullBackOff`, view the Pod events:
216
+
To use image pull secrets for a Pod (or a Deployment, or other object that
217
+
has a pod template that you are using), you need to make sure that the appropriate
218
+
Secret does exist in the right namespace. The namespace to use is the same
219
+
namespace where you defined the Pod.
220
+
{{< /note >}}
221
+
222
+
Also, in case the Pod fails to start with the status `ImagePullBackOff`, view the Pod events:
223
+
215
224
```shell
216
225
kubectl describe pod private-reg
217
226
```
@@ -229,12 +238,6 @@ Events:
229
238
... FailedToRetrieveImagePullSecret ... Unable to retrieve some image pull secrets (<regcred>); attempting to pull the image may not succeed.
230
239
```
231
240
232
-
233
-
{{< /note >}}
234
-
235
-
236
-
237
-
238
241
## {{% heading "whatsnext" %}}
239
242
240
243
* Learn more about [Secrets](/docs/concepts/configuration/secret/)
0 commit comments