When generally managing containerized apps at work, container images are maintained on private docker registry.

According to a blog I found, Pod with a status of either ‘ErrPullImage’ or ‘ImagePullBackOff’ are caused by two reasons :

• Specifying the wrong container image
• Trying to use private images without providing registry credentials.

Renaming wrong container image is pretty straight forward. if absence of the registry credentials is the case, I need to add a secret to pass.

In order to create a new secret,

kubectl create secret docker-registry dockersecret --docker-server=https://index.docker.io/v1/ --docker-username=<username> --docker-password=<password> --docker-email=<emailj>

New added secret can be confirmed by,

kubectl get secret docker-registry --output=yaml
# OR
kubectl get secret docker-registry --output="jsonpath={.data.\.dockerconfigjson}" | base64 -d

Describe the secret file in YAML file in .spec.containers.imagePullSecrets

apiVersion: v1
kind: Pod
metadata:
  name: A_POD
spec:
  containers:
  - name: container-name
    image: <registry URL>/<image Name>:<image Tag>
  imagePullSecrets:
  - name: docker-registry

• Linux (4)

• Docker (2) ,
• Kubernetes (2)