• EN
Solved

catalog-svc pod is not running.

N
Userlevel 3

when i am describe pod getting below error. Please help me this is important.

kubectl describe pod catalog-svc-5847d4fd78-zglgx -n kasten-io

Events:
  Type     Reason                  Age                     From                     Message
  ----     ------                  ----                    ----                     -------
  Normal   Scheduled               9m39s                                            Successfully assigned kasten-io/catalog-svc-5847d4fd78-zglgx to znlapcdp07443v
  Warning  FailedCreatePodSandBox  9m37s                   kubelet, znlapcdp07443v  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "cf03969714a36fbd87688bc756b5e51a3dc89c3a868ace6b8981caf595bc8858" network for pod "catalog-svc-5847d4fd78-zglgx": networkPlugin cni failed to set up pod "catalog-svc-5847d4fd78-zglgx_kasten-io" network: Calico CNI panicked during ADD: runtime error: invalid memory address or nil pointer dereference
  Normal   SandboxChanged          9m36s                   kubelet, znlapcdp07443v  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulling                 9m34s                   kubelet, znlapcdp07443v  Pulling image "gcr.io/kasten-images/upgrade:5.5.2"
  Normal   Created                 9m33s                   kubelet, znlapcdp07443v  Created container upgrade-init
  Normal   Pulled                  9m33s                   kubelet, znlapcdp07443v  Successfully pulled image "gcr.io/kasten-images/upgrade:5.5.2" in 699.458988ms
  Normal   Started                 9m33s                   kubelet, znlapcdp07443v  Started container upgrade-init
  Normal   Pulled                  9m32s                   kubelet, znlapcdp07443v  Successfully pulled image "gcr.io/kasten-images/catalog:5.5.2" in 558.557648ms
  Normal   Pulling                 9m32s                   kubelet, znlapcdp07443v  Pulling image "gcr.io/kasten-images/catalog:5.5.2"
  Normal   Created                 9m32s                   kubelet, znlapcdp07443v  Created container schema-upgrade-check
  Normal   Started                 9m31s                   kubelet, znlapcdp07443v  Started container schema-upgrade-check
  Normal   Pulling                 9m30s                   kubelet, znlapcdp07443v  Pulling image "gcr.io/kasten-images/catalog:5.5.2"
  Normal   Pulled                  9m30s                   kubelet, znlapcdp07443v  Successfully pulled image "gcr.io/kasten-images/catalog:5.5.2" in 548.119273ms
  Normal   Created                 9m30s                   kubelet, znlapcdp07443v  Created container catalog-svc
  Normal   Pulling                 9m29s                   kubelet, znlapcdp07443v  Pulling image "ghcr.io/kanisterio/kanister-tools:0.85.0"
  Normal   Started                 9m29s                   kubelet, znlapcdp07443v  Started container catalog-svc
  Warning  Failed                  9m29s                   kubelet, znlapcdp07443v  Failed to pull image "ghcr.io/kanisterio/kanister-tools:0.85.0": rpc error: code = Unknown desc = Error response from daemon: Get https://ghcr.io/v2/: read tcp 10.147.155.173:34264->140.82.114.34:443: read: connection reset by peer
  Warning  Failed                  9m29s                   kubelet, znlapcdp07443v  Error: ErrImagePull
  Normal   BackOff                 9m28s                   kubelet, znlapcdp07443v  Back-off pulling image "ghcr.io/kanisterio/kanister-tools:0.85.0"
  Warning  Failed                  9m28s                   kubelet, znlapcdp07443v  Error: ImagePullBackOff

icon

Best answer by jaiganeshjk 3 February 2023, 08:45

View original

5 comments

Madi.Cristil
Userlevel 7
Badge +7

@jaiganeshjk 

Madi Cristil
jaiganeshjk
Userlevel 6
Badge +2

@ntiwari38 Thank you for posting the question.

From the events, I could see that the kanister-sidecar container from the catalog-svc is failing as it couldn’t pull the image from ghcr.io.

Can you confirm if your environment allows pulling images from github container registry (ghcrio) ?

 

If yes, it could be transient problem, You can try recreating the pod.
You can also try to confirm if the image is accessible from you environment by running another pod with that image.

kubectl run kanister-tools --rm -it --image ghcr.io/kanisterio/kanister-tools:0.85.0 -n kasten-io -- bash

 

BTW, I can confirm that this image is available and accessible without any problem

❯ docker pull ghcr.io/kanisterio/kanister-tools:0.85.0

0.85.0: Pulling from kanisterio/kanister-tools
1d6f30850896: Pull complete 
97d7b37e7232: Pull complete 
196b571ab112: Pull complete 
74d0dc5eeb47: Pull complete 
187f5a0f24c6: Pull complete 
701b65989276: Pull complete 
Digest: sha256:0c8da74a06fcfba32c7c278861b1e7e29b40e40f2a5e38c195f4339b81ca640b
Status: Downloaded newer image for ghcr.io/kanisterio/kanister-tools:0.85.0

 

Jaiganesh
N
Userlevel 3

@jaiganeshjk Thanks for good Answer 

It worked now pod is in running state.

 

jaiganeshjk
Userlevel 6
Badge +2

@ntiwari38 Thanks for confirming. Glad that it worked for you.

Would you be able to mark the comment as answer ?

Jaiganesh
A

also it’s worth to mention that catalog has PVC and you might have out of capacity issue, then you just need to expand it.

 

Best Regards,

Abdennour

https://sa.linkedin.com/in/abdennour

Comment


Terms & Conditions