【Containerd】解決輸入crictl images命令報錯問題
文章目錄
- 【Containerd】解決輸入crictl images命令報錯問題
- 問題復現
- 解決辦法
- 驗證結果
- 參考鏈接
問題復現
[root@master01 ~]# crictl images
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.
E0613 21:51:15.528305 2707 remote_image.go:119] "ListImages with filter from image service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/dockershim.sock: connect: no such file or directory\"" filter="&ImageFilter{Image:&ImageSpec{Image:,Annotations:map[string]string{},},}"
FATA[0000] listing images: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /var/run/dockershim.sock: connect: no such file or directory"
解決辦法
[root@master01 ~]# cat > /etc/crictl.yaml <<EOF
runtime-endpoint: unix:///var/run/containerd/containerd.sock
image-endpoint: unix:///var/run/containerd/containerd.sock
timeout: 0
debug: false
pull-image-on-create: false
EOF
參數說明
- runtime-endpoint:指定容器運行時的端點。這里使用的是一個 Unix 域套接字。
- image-endpoint:指定鏡像服務的端點。這里使用的是一個 Unix 域套接字。
- timeout:設置
crictl
命令的超時時間。- debug: 設置是否啟用調試模式。
- pull-image-on-create: 設置在創建容器時是否自動拉取鏡像。
驗證結果
[root@master01 ~]# crictl images
IMAGE TAG IMAGE ID SIZE
registry.aliyuncs.com/google_containers/kube-proxy v1.28.2 c120fed2beb84 24.6MB
registry.aliyuncs.com/google_containers/pause 3.6 6270bb605e12e 302kB
參考鏈接
[1] crictl導入鏡像-CSDN博客
[2] Docker - 實現本地鏡像的導出、導入(export、import、save、load)
[3] Docker將鏡像導出到本地,上傳至內網服務器上-騰訊云開發者社區-騰訊云
[4] crictl報錯 - 個人記錄 - 博客園