Welcome to the Linux Foundation Forum!

LAB 3.2 section 18

Hi, I'm working with ubuntu 20.04 on AWS. I managed to configure the worker node to pull from local $repo.
I also managed to curl from from worker
~$curl $repo/v2/_catalog
answer: {"repositories":["simpleapp"]}
I created try1 deployment with image-$repo/simpleapp and added 6 replicas:
answer:
_NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
nginx-6488f757bc-f4sqg 1/1 Running 2 (163m ago) 20h 192.168.182.22 ip-172-31-13-118
registry-d4cf9fd7d-jl8cf 1/1 Running 2 (163m ago) 20h 192.168.182.23 ip-172-31-13-118
try1-5467785d4d-55cw2 1/1 Running 0 157m 192.168.182.26 ip-172-31-13-118
try1-5467785d4d-gbx5d 1/1 Running 0 157m 192.168.182.25 ip-172-31-13-118
try1-5467785d4d-n9589 1/1 Running 0 157m 192.168.182.142 ip-172-31-3-233
try1-5467785d4d-rkxq6 1/1 Running 0 158m 192.168.182.24 ip-172-31-13-118
try1-5467785d4d-wj5vx 1/1 Running 0 157m 192.168.182.143 ip-172-31-3-233
try1-5467785d4d-wk4lq 1/1 Running 0 157m 192.168.182.27 ip-172-31-13-118 _

The problem is in worker node. When I check the list of containers with:
worker:~$:sudo crictl ps | grep simple
I receive the list of containers that created in the cp, but with errors and warnings:

WARN[0000] runtime connect using default endpoints: [unix:///var/run/dockershim.sock unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead.
ERRO[0000] unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /var/run/dockershim.sock: connect: no such file or directory"
WARN[0000] image connect using default endpoints: [unix:///var/run/dockershim.sock unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead.
ERRO[0000] unable to determine image API version: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /var/run/dockershim.sock: connect: no such file or directory"
b5be6b5c1f549 5a160028c56e9 3 hours ago Running simpleapp 0 9d9318f45a2bc try1-5467785d4d-wk4lq
1fad538623c32 5a160028c56e9 3 hours ago Running simpleapp 0 211bc4337d7af try1-5467785d4d-55cw2
f65c0051056e4 5a160028c56e9 3 hours ago Running simpleapp 0 34711771fa87c try1-5467785d4d-gbx5d
01fd909e40d8d 5a160028c56e9 3 hours ago Running simpleapp 0 d0e412f46a33f try1-5467785d4d-rkxq6

Is this a problem? If so, how can I solve it?

Answers

  • Posts: 2,453
    edited September 2022

    Hi @zite,

    Crictl requires its runtime and image endpoints to be set prior to running the crictl CLI tool. This can be done by creating the /etc/crictl.yaml file.
    You can create the crictl.yaml file as such:

    1. student@worker:~$ sudo -c sh 'cat <<EOF > /etc/crictl.yaml
    2. runtime-endpoint: unix:///run/containerd/containerd.sock
    3. image-endpoint: unix:///run/containerd/containerd.sock
    4. timeout: 2
    5. debug: false
    6. pull-image-on-create: false
    7. EOF'

    This assumes that you have the containerd runtime installed on your nodes.

    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