Welcome to the Linux Foundation Forum!

LAB 3.4 - Ngnix pods deployment

Why we're getting erros and pos gettibg created ? what does that rpc error means , and if its there why we're able to create the pods.

so 1 pod failed & 1 created

[email protected]:~$ kubectl create deployment nginx --image=nginx
deployment.apps/nginx created
[email protected]:~$ kubectl get all
NAME READY STATUS RESTARTS AGE
pod/nginx-f89759699-wfg4l 0/1 ContainerCreating 0 7s
pod/ngnix-759889745c-gzcc4 0/1 ImagePullBackOff 0 5m7s

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.96.0.1 443/TCP 3d14h

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/nginx 0/1 1 0 7s
deployment.apps/ngnix 0/1 1 0 5m7s

NAME DESIRED CURRENT READY AGE
replicaset.apps/nginx-f89759699 1 1 0 7s
replicaset.apps/ngnix-759889745c 1 1 0 5m7s
[email protected]:~$ kubectl get events |grep 'pod/nginx-f89759699-wfg4l'
28s Normal Scheduled pod/nginx-f89759699-wfg4l Successfully assigned default/nginx-f89759699-wfg4l to worker
26s Normal Pulling pod/nginx-f89759699-wfg4l Pulling image "nginx"
21s Normal Pulled pod/nginx-f89759699-wfg4l Successfully pulled image "nginx"
20s Normal Created pod/nginx-f89759699-wfg4l Created container nginx
20s Normal Started pod/nginx-f89759699-wfg4l Started container nginx
[email protected]:~$ kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-f89759699-wfg4l 1/1 Running 0 39s
ngnix-759889745c-gzcc4 0/1 ImagePullBackOff 0 5m39s
[email protected]:~$ kubectl get events |grep 'ngnix-759889745c-gzcc4'
6m22s Normal Scheduled pod/ngnix-759889745c-gzcc4 Successfully assigned default/ngnix-759889745c-gzcc4 to worker
4m56s Normal Pulling pod/ngnix-759889745c-gzcc4 Pulling image "mgnix"
4m56s Warning Failed pod/ngnix-759889745c-gzcc4 Failed to pull image "mgnix": rpc error: code = Unknown desc = Error response from daemon: pull access denied for mgnix, repository does not exist or may require 'docker login'
4m56s Warning Failed pod/ngnix-759889745c-gzcc4 Error: ErrImagePull
4m41s Normal BackOff pod/ngnix-759889745c-gzcc4 Back-off pulling image "mgnix"
74s Warning Failed pod/ngnix-759889745c-gzcc4 Error: ImagePullBackOff
6m22s Normal SuccessfulCreate replicaset/ngnix-759889745c Created pod: ngnix-759889745c-gzcc4
[email protected]:~$ kubectl get events |grep 'nginx-f89759699-wfg4l'
93s Normal Scheduled pod/nginx-f89759699-wfg4l Successfully assigned default/nginx-f89759699-wfg4l to worker
91s Normal Pulling pod/nginx-f89759699-wfg4l Pulling image "nginx"
86s Normal Pulled pod/nginx-f89759699-wfg4l Successfully pulled image "nginx"
85s Normal Created pod/nginx-f89759699-wfg4l Created container nginx
85s Normal Started pod/nginx-f89759699-wfg4l Started container nginx
93s Normal SuccessfulCreate replicaset/nginx-f89759699 Created pod: nginx-f89759699-wfg4l
[email protected]:~$ kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-f89759699-wfg4l 1/1 Running 0 114s
ngnix-759889745c-gzcc4 0/1 ImagePullBackOff 0 6m54s
[email protected]:~$ kubectl get deployments
NAME READY UP-TO-DATE AVAILABLE AGE
nginx 1/1 1 1 2m12s

ngnix 0/1 1 0 7m12s

Comments

  • A successful is clean like this

    [email protected]:~$ kubectl create deployment nginx --image=nginx
    deployment.apps/nginx created
    [email protected]:~$ kubectl get pods
    NAME READY STATUS RESTARTS AGE
    nginx-f89759699-wldhl 1/1 Running 0 7s
    [email protected]:~$ kubectl get pods
    NAME READY STATUS RESTARTS AGE
    nginx-f89759699-wldhl 1/1 Running 0 13s
    [email protected]:~$ kubectl get events |grep nginx-f89759699-wldhl
    30s Normal Scheduled pod/nginx-f89759699-wldhl Successfully assigned default/nginx-f89759699-wldhl to worker
    28s Normal Pulling pod/nginx-f89759699-wldhl Pulling image "nginx"
    28s Normal Pulled pod/nginx-f89759699-wldhl Successfully pulled image "nginx"
    27s Normal Created pod/nginx-f89759699-wldhl Created container nginx
    27s Normal Started pod/nginx-f89759699-wldhl Started container nginx
    30s Normal SuccessfulCreate replicaset/nginx-f89759699 Created pod: nginx-f89759699-wldhl

  • Q? How its k8s ineracting with docker images (interanl or external) , from where its getting my ngnix image ?

  • I've successfully completed chapter 3 labs

    notes

    LAB 3.2.5

    This command works
    openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | openssl dgst -sha256 -hex

    vs the below

    openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | openssl dgst -sha256 -hex | sed's/ˆ.* //'

    LAB 3.4.7

    This command works
    kubectl create -f first.yaml --validate=false

    vs

    kubectl create -f first.yaml

  • @Prasad2282 I saw in the pod you failing having this error in the event log, (imagine you don't read the event log properly.)
    it says,
    4m56s Warning Failed pod/ngnix-759889745c-gzcc4 Failed to pull image "mgnix": rpc error: code = Unknown desc = Error response from daemon: pull access denied for mgnix, repository does not exist or may require 'docker login'

    So please login to the kubenetes worker node which pod ngnix-759889745c-gzcc4 is running and check weather you have docke installed and working in that worker node. you can also type "sudo docker login" to check weather you have successfully registered or not with docker hub.

  • chrispokorni
    chrispokorni Posts: 1,127
    edited December 2020

    Hi @Prasad2282,

    If you look closely at the output, you will notice a typo in your image name:

    4m56s Warning Failed pod/ngnix-759889745c-gzcc4 Failed to pull image "mgnix": rpc error: code = Unknown desc = Error response from daemon: pull access denied for mgnix, repository does not exist or may require 'docker login'

    The "mginx" image you attempted to use may not exist.

    I would recommend double-checking your commands and yaml manifests for typos and errors before attempting to deploy resources in your cluster.

    The openssl command you claim it does not work, it actually works. The one you provided includes a typo, and that is why it did not work for you. If the command is copy and pasted in its correct syntax, it works:

    openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | openssl dgst -sha256 -hex | sed 's/ˆ.* //'

    Yours was missing the space between sed and 's/ˆ.* //'.

    Then finally the kubectl create -f first.yaml command you claim it does not work, it actually works. However, you have to pay close attention while reading Step 5 of Excise 3.4 and follow the instruction to remove specific lines from the first.yaml file before attempting the create command.

    Since all issues reported have been caused by user typos, I would strongly recommend double checking your work before running commands, and reading very carefully the exercises in their entirety from the lab manual.

    Regards,
    -Chris

  • @amiladevops said:
    @Prasad2282 I saw in the pod you failing having this error in the event log, (imagine you don't read the event log properly.)
    it says,
    4m56s Warning Failed pod/ngnix-759889745c-gzcc4 Failed to pull image "mgnix": rpc error: code = Unknown desc = Error response from daemon: pull access denied for mgnix, repository does not exist or may require 'docker login'

    So please login to the kubenetes worker node which pod ngnix-759889745c-gzcc4 is running and check weather you have docke installed and working in that worker node. you can also type "sudo docker login" to check weather you have successfully registered or not with docker hub.

    ===yeap its typo===== Thanks for checking

  • @chrispokorni said:
    Hi @Prasad2282,

    If you look closely at the output, you will notice a typo in your image name:

    4m56s Warning Failed pod/ngnix-759889745c-gzcc4 Failed to pull image "mgnix": rpc error: code = Unknown desc = Error response from daemon: pull access denied for mgnix, repository does not exist or may require 'docker login'

    The "mginx" image you attempted to use may not exist.

    I would recommend double-checking your commands and yaml manifests for typos and errors before attempting to deploy resources in your cluster.

    The openssl command you claim it does not work, it actually works. The one you provided includes a typo, and that is why it did not work for you. If the command is copy and pasted in its correct syntax, it works:

    openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | openssl dgst -sha256 -hex | sed 's/ˆ.* //'

    Yours was missing the space between sed and 's/ˆ.* //'.

    Then finally the kubectl create -f first.yaml command you claim it does not work, it actually works. However, you have to pay close attention while reading Step 5 of Excise 3.4 and follow the instruction to remove specific lines from the first.yaml file before attempting the create command.

    Since all issues reported have been caused by user typos, I would strongly recommend double checking your work before running commands, and reading very carefully the exercises in their entirety from the lab manual.

    Regards,
    -Chris

    Agree ..Thanks for checking and replying on this!

Categories

Upcoming Training