Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

kubernetes deployment- container not starting- error- InvalidImageName

Below is the Kubernetes deployment yaml file -container image section:

image: https://registry.ng.bluemix.net/****/test-service:test-branch-67

imagePullPolicy: Always

Below is the error message after deploying:

ubuntu@ip-xxxx:~$ kubectl logs test-deployment-69c6d8xxx -n test

Error from server (BadRequest): container "test-deployment" in pod "test-deployment-ccccxxx" is waiting to start: InvalidImageName

Another error log:

Failed to apply default image tag "https://registry.ng.bluemix.net/test/test-service:test-branch-66": couldn't parse image reference "https://registry.ng.bluemix.net/test/test-service:test-branch-66": invalid reference format

Any idea why the pod is not coming up?

like image 955
Raj kumar Avatar asked Mar 22 '19 14:03

Raj kumar


People also ask

How do you fix Errimagepull?

To resolve it, double check the pod specification and ensure that the repository and image are specified correctly. If this still doesn't work, there may be a network issue preventing access to the container registry. Look in the describe pod text file to obtain the hostname of the Kubernetes node.

Why is my Kubernetes deployment not ready?

If a Pod is Running but not Ready it means that the Readiness probe is failing. When the Readiness probe is failing, the Pod isn't attached to the Service, and no traffic is forwarded to that instance.


1 Answers

Remove the https:// from the image name, and if you are using a private registry, make sure to use imagePullSecrets.

like image 53
cookiedough Avatar answered Sep 22 '22 06:09

cookiedough