Skip to content

Commit 16fdb34

Browse files
authored
Update pull-image-private-registry.md
1 parent aa6e463 commit 16fdb34

File tree

1 file changed

+7
-9
lines changed

1 file changed

+7
-9
lines changed

content/en/docs/tasks/configure-pod-container/pull-image-private-registry.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,8 @@ docker login
3838
When prompted, enter your Docker ID, and then the credential you want to use (access token,
3939
or the password for your Docker ID).
4040

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).
4243

4344
View the `config.json` file:
4445

@@ -60,7 +61,8 @@ The output contains a section similar to this:
6061

6162
{{< note >}}
6263
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).
6466
{{< /note >}}
6567

6668
## 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
215217
has a pod template that you are using), you need to make sure that the appropriate
216218
Secret does exist in the right namespace. The namespace to use is the same
217219
namespace where you defined the Pod.
220+
{{< /note >}}
218221

219222
Also, in case the Pod fails to start with the status `ImagePullBackOff`, view the Pod events:
223+
220224
```shell
221225
kubectl describe pod private-reg
222226
```
@@ -234,17 +238,11 @@ Events:
234238
... FailedToRetrieveImagePullSecret ... Unable to retrieve some image pull secrets (<regcred>); attempting to pull the image may not succeed.
235239
```
236240

237-
238-
{{< /note >}}
239-
240-
241-
242-
243241
## {{% heading "whatsnext" %}}
244242

245243
* Learn more about [Secrets](/docs/concepts/configuration/secret/)
246244
* or read the API reference for {{< api-reference page="config-and-storage-resources/secret-v1" >}}
247245
* Learn more about [using a private registry](/docs/concepts/containers/images/#using-a-private-registry).
248246
* 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).
249247
* 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

Comments
 (0)