Welcome to the Linux Foundation Forum!

LFD259 Paragraph 6 on Page 49

I tried running the code to show the ilike environment variable, but it gives me the error:

  1. error: unable to upgrade connection: container not found ("simpleapp")

This is what I get in terms of the pod state:

  1. kubectl get pods
  2. NAME READY STATUS RESTARTS AGE
  3. init-tester 1/1 Running 1 (57m ago) 5d21h
  4. nginx-79ff9c85db-t5qmq 1/1 Running 9 (57m ago) 24d
  5. registry-7d7db4bd8f-fk8lx 1/1 Running 9 (57m ago) 24d
  6. try1-7845d5b88-jddt8 1/2 ErrImagePull 0 16m
  7. try1-7845d5b88-jvtbg 1/2 ImagePullBackOff 0 16m
  8. try1-7845d5b88-ndbzp 1/2 ErrImagePull 0 16m
  9. try1-7845d5b88-rh4vv 1/2 ImagePullBackOff 0 16m
  10. try1-7845d5b88-rz8zt 1/2 ImagePullBackOff 0 16m
  11. try1-7845d5b88-v42hl 1/2 ImagePullBackOff 0 16m

I ran the command on both a pod with ErrImagePull and the one with ImagePullBackOff. Neither one finds simpleapp, which kind of makes if the image was not pulled correctly.

This is what I get when I use kubectl describe for the first pod:

  1. Name: init-tester
  2. Namespace: default
  3. Priority: 0
  4. Service Account: default
  5. Node: ip-172-31-5-160/172.31.5.160
  6. Start Time: Sun, 20 Aug 2023 23:38:57 +0000
  7. Labels: app=inittest
  8. Annotations: cni.projectcalico.org/containerID: aaa6f94cf5853f28c04bd15ccf98136adf2d7b82f8a4355072e7defe3c111a5b
  9. cni.projectcalico.org/podIP: 192.168.72.34/32
  10. cni.projectcalico.org/podIPs: 192.168.72.34/32
  11. Status: Running
  12. IP: 192.168.72.34
  13. IPs:
  14. IP: 192.168.72.34
  15. Init Containers:
  16. failed:
  17. Container ID: containerd://dfef68b8fc23835ddfb79c6181da8ca34b171be9e7d24301fb4322626d96f354
  18. Image: busybox
  19. Image ID: docker.io/library/busybox@sha256:3fbc632167424a6d997e74f52b878d7cc478225cffac6bc977eedfe51c7f4e79
  20. Port: <none>
  21. Host Port: <none>
  22. Command:
  23. /bin/true
  24. State: Terminated
  25. Reason: Completed
  26. Exit Code: 0
  27. Started: Sat, 26 Aug 2023 19:55:25 +0000
  28. Finished: Sat, 26 Aug 2023 19:55:25 +0000
  29. Ready: True
  30. Restart Count: 1
  31. Environment: <none>
  32. Mounts:
  33. /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9rjk6 (ro)
  34. Containers:
  35. webservice:
  36. Container ID: containerd://f42e45bb62d366f75746433b01dbd87041a7c9c75fcad0f3be35d7b03e36d2bc
  37. Image: nginx
  38. Image ID: docker.io/library/nginx@sha256:104c7c5c54f2685f0f46f3be607ce60da7085da3eaa5ad22d3d9f01594295e9c
  39. Port: <none>
  40. Host Port: <none>
  41. State: Running
  42. Started: Sat, 26 Aug 2023 19:55:26 +0000
  43. Last State: Terminated
  44. Reason: Unknown
  45. Exit Code: 255
  46. Started: Sun, 20 Aug 2023 23:38:59 +0000
  47. Finished: Sat, 26 Aug 2023 19:54:22 +0000
  48. Ready: True
  49. Restart Count: 1
  50. Environment: <none>
  51. Mounts:
  52. /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9rjk6 (ro)
  53. Conditions:
  54. Type Status
  55. Initialized True
  56. Ready True
  57. ContainersReady True
  58. PodScheduled True
  59. Volumes:
  60. kube-api-access-9rjk6:
  61. Type: Projected (a volume that contains injected data from multiple sources)
  62. TokenExpirationSeconds: 3607
  63. ConfigMapName: kube-root-ca.crt
  64. ConfigMapOptional: <nil>
  65. DownwardAPI: true
  66. QoS Class: BestEffort
  67. Node-Selectors: <none>
  68. Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
  69. node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
  70. Events: <none>
  71.  

Answers

  • Posts: 2,458

    Hi @rasputin312,

    Can you describe one of the try1-7845d5b88-xxxxx pods? Since those are the pods we would need to troubleshoot in this case. Recreate try1 deployment to have the events regenerated. Then describe a try1 pod with the ErrImagePull status and one with the ImagePullBackOff status.

    Also, what is the output of the following command:

    kubectl get pods -A -o wide

    The init-tester pod seems to be running as expected, so it does not help us in troubleshooting the try1 deployment.

    Regards,
    -Chris

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training