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
+7-9Lines changed: 7 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}
@@ -215,8 +217,10 @@ To use image pull secrets for a Pod (or a Deployment, or other object that
215
217
has a pod template that you are using), you need to make sure that the appropriate
216
218
Secret does exist in the right namespace. The namespace to use is the same
217
219
namespace where you defined the Pod.
220
+
{{< /note >}}
218
221
219
222
Also, in case the Pod fails to start with the status `ImagePullBackOff`, view the Pod events:
223
+
220
224
```shell
221
225
kubectl describe pod private-reg
222
226
```
@@ -234,17 +238,11 @@ Events:
234
238
... FailedToRetrieveImagePullSecret ... Unable to retrieve some image pull secrets (<regcred>); attempting to pull the image may not succeed.
235
239
```
236
240
237
-
238
-
{{< /note >}}
239
-
240
-
241
-
242
-
243
241
## {{% heading "whatsnext" %}}
244
242
245
243
* Learn more about [Secrets](/docs/concepts/configuration/secret/)
246
244
* or read the API reference for {{< api-reference page="config-and-storage-resources/secret-v1" >}}
247
245
* Learn more about [using a private registry](/docs/concepts/containers/images/#using-a-private-registry).
248
246
* Learn more about [adding image pull secrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account).
249
247
* See [kubectl create secret docker-registry](/docs/reference/generated/kubectl/kubectl-commands/#-em-secret-docker-registry-em-).
250
-
* See the `imagePullSecrets` field within the [container definitions](/docs/reference/kubernetes-api/workload-resources/pod-v1/#containers) of a Pod
248
+
* See the `imagePullSecrets` field within the [container definitions](/docs/reference/kubernetes-api/workload-resources/pod-v1/#containers) of a Pod
0 commit comments