ctr 导入镜像后如何查看镜像

当我们使用了/拉建了kubeadm,kubelet,kubectl  都是1.24以上的版本,那么docker 拉取镜像就已经不太适用了,创建pod时也直接用的containerd

废话不多说,开干!

查看所有镜像的名称:版本号:ctr -n k8s.io i ls -q  或者 ctr -n k8s.io images list -q

查看所有镜像:ctr -n k8s.io images list   或者  crictl images

导入指定镜像:ctr -n k8s.io images import pause.tar.gz

导入当前目录所有镜像:ctr -n k8s.io images import ./*.tar.gz  或者  ctr -n k8s.io images import ./*(保证当前目录下都是离线镜像包)

导入指定镜像-给镜像改名:ctr -n k8s.io images import pause.tar.gz  registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.9

导出单个镜像到指定离线镜像包中:

ctr -n k8s.io images export calico3.18.tar.gz  docker.io/calico/cni:v3.18.0

导出多个镜像压缩到指定的离线镜像包中:

ctr -n k8s.io images export calico3.18.tar.gz docker.io/calico/cni:v3.18.0 docker.io/calico/kube-controllers:v3.18.0 docker.io/calico/node:v3.18.0 docker.io/calico/pod2daemon-flexvol:v3.18.0

查看1:

[root@node1 images]# ctr -n k8s.io images list -q | grep busybox:1.28
docker.io/library/busybox:1.28
[root@node1 images]#

查看2:

[root@master1 ~]# ctr -n k8s.io i ls -q
docker.io/calico/cni:v3.18.0
docker.io/calico/kube-controllers:v3.18.0
docker.io/calico/node:v3.18.0
docker.io/calico/pod2daemon-flexvol:v3.18.0
docker.io/library/busybox:1.28
registry.aliyuncs.com/google_containers/pause:3.7
registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.10.1
registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.9.3
registry.cn-hangzhou.aliyuncs.com/google_containers/coredns@sha256:90d3eeb2e2108a14fe2ecbef1bc1b5607834335d99c842a377f338aade9da028
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd-amd64:3.4.7-0
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.5.4-0
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.5.9-0
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd@sha256:b124583790d2407fa140c01f42166e3292cc8191ef5d37034fe5a89032081b90
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.25.0
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.28.0
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver@sha256:42ebad4ff7b72c7aa6988a6d4674f9391a80f2e0ba4bf20d705a1f844ba0a5c3
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.25.0
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.28.0
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager@sha256:71da477a3f5ae3be6d6b2d6dd23862036aa30346d0fe7660342a6fb54890232b
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.25.0
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.28.0
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy@sha256:a61eeb2562dc22fb158f7e00aff4343da2f67b4899a879b76002ce394d94b886
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.25.0
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.28.0
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler@sha256:cd2275aed550dca60fbccb136fdc407a8e9dd045a015762d7a769e4dee36b6c1
registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.8
registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.9
registry.cn-hangzhou.aliyuncs.com/google_containers/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097
sha256:1a54c86c03a673d4e046b9f64854c713512d39a0136aef76a4a450d5ad51273e
sha256:221177c6082a88ea4f6240ab2450d540955ac6f4d5454f0e15751b653ebda165
sha256:2a22066e9588d0da835a68d1cf39d735be555a3b99111866637edd2584711239
sha256:4873874c08efc72e9729683a83ffbb7502ee729e9a5ac097723806ea7fa13517
sha256:4be79c38a4bab6e1252a35697500e8a0d9c5c7c771d9fcc1935c9a7f6cdf4c62
sha256:4d2edfd10d3e3f4395b70652848e2a1efd5bd0bc38e9bc360d4ee5c51afacfe5
sha256:5185b96f0becf59032b8e3646e99f84d9655dff3ac9e2605e0dc77f9c441ae4a
sha256:58a9a0c6d96f2b956afdc831504e6796c23f5f90a7b5341393b762d9ba96f2f6
sha256:5a7c4970fbc29f122f97f65426add223d4da1253b63b6a02ab98ae0d27f4b3f5
sha256:727de170e4ce9d45d303d07c6147c78c21f1685cf6742a6bd4820343f09727d7
sha256:73deb9a3f702532592a4167455f8bf2e5f5d900bcc959ba2fd2d35c321de1af9
sha256:8c811b4aec35f259572d0f79207bc0678df4c736eeec50bc9fec37ed936a472a
sha256:9a154323fbf74983ed091e9ab196ed16d720aab79d1dd88d3cd9b7c43721dc38
sha256:a8a176a5d5d698f9409dc246f81fa69d37d4a2f4132ba5e62e72a78476b27f66
sha256:bb5e0dde9054c02d6badee88547be7e7bb7b7b818d277c8a61b4b29484bbff95
sha256:bef2cf3115095379b5af3e6c0fb4b0e6a8ef7a144aa2907bd0a3125e9d2e203e
sha256:e6f1816883972d4be47bd48879a08919b96afcd344132622e4d444987919323c
sha256:ea1030da44aa18666a7bf15fddd2a38c3143c3277159cb8bdd95f45c8ce62d7a
sha256:ead0a4a53df89fd173874b46093b6e62d8c72967bbf606d672c9e8c9b601a4fc
sha256:f6f496300a2ae7a6727ccf3080d66d2fd22b6cfc271df5351c976c23a28bb157
sha256:ff0da8ec66a57b9f944fb894d93525122fe8d0f6767f6e7b76c0c211b9592f26
[root@master1 ~]# 

查看3:

查看:
[root@master1 ~]# crictl images
IMAGE                                                                         TAG                 IMAGE ID            SIZE
docker.io/calico/cni                                                          v3.18.0             727de170e4ce9       131MB
docker.io/calico/kube-controllers                                             v3.18.0             9a154323fbf74       53.4MB
docker.io/calico/node                                                         v3.18.0             5a7c4970fbc29       177MB
docker.io/calico/pod2daemon-flexvol                                           v3.18.0             2a22066e9588d       21.8MB
docker.io/library/busybox                                                     1.28                8c811b4aec35f       1.36MB
registry.aliyuncs.com/google_containers/pause                                 3.7                 221177c6082a8       311kB
registry.cn-hangzhou.aliyuncs.com/google_containers/coredns                   v1.10.1             ead0a4a53df89       16.2MB
registry.cn-hangzhou.aliyuncs.com/google_containers/coredns                   v1.9.3              5185b96f0becf       14.8MB
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd-amd64                3.4.7-0             ff0da8ec66a57       104MB
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd                      3.5.4-0             a8a176a5d5d69       102MB
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd                      3.5.9-0             73deb9a3f7025       103MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver            v1.25.0             4d2edfd10d3e3       34.2MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver            v1.28.0             bb5e0dde9054c       34.6MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager   v1.25.0             1a54c86c03a67       31.3MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager   v1.28.0             4be79c38a4bab       33.4MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy                v1.25.0             58a9a0c6d96f2       20.3MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy                v1.28.0             ea1030da44aa1       24.6MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler            v1.25.0             bef2cf3115095       15.8MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler            v1.28.0             f6f496300a2ae       18.8MB
registry.cn-hangzhou.aliyuncs.com/google_containers/pause                     3.8                 4873874c08efc       311kB
registry.cn-hangzhou.aliyuncs.com/google_containers/pause                     3.9                 e6f1816883972       322kB
You have new mail in /var/spool/mail/root

导入:

[root@node1 ~]# ctr -n k8s.io images import pause.tar.gz registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.9

导出1:

[root@master1 ~]# ctr -n k8s.io i export pause.tar.gz registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.9
[root@master1 ~]# ll
total 328
-rw-------. 1 root root      0 Apr 30 14:38 anaconda-ks.cfg
-rw-r--r--  1 root root   1105 Apr 29 21:21 kubeadm.yaml
-rw-r--r--  1 root root 329728 Apr 30 14:46 pause.tar.gz
drwxr-xr-x  2 root root     25 Apr 30 11:30 yaml
[root@master1 ~]# 

导出2:

导出多个镜像压缩到指定的离线镜像包中:
ctr -n k8s.io images export calico3.18.tar.gz  docker.io/calico/cni:v3.18.0 docker.io/calico/kube-controllers:v3.18.0 docker.io/calico/node:v3.18.0 docker.io/calico/pod2daemon-flexvol:v3.18.0

  • 3
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
要在本地的 Kubernetes 集群中导入本地镜像文件,可以使用以下步骤: 1. 打标签:首先,需要给镜像打上标签,使其符合 Kubernetes 的要求。标签应该包含仓库地址、镜像名称和版本号。 例如,如果要将本地的镜像文件 hello-world.tar.gz 导入到 Kubernetes 中,则可以使用以下命令为其打标签: ``` docker tag hello-world:latest 127.0.0.1:5000/hello-world:latest ``` 其中,127.0.0.1:5000 是仓库地址,hello-world 是镜像名称,latest 是版本号。 2. 启动本地仓库:Kubernetes 默认使用 Docker Hub 作为镜像仓库,如果要使用本地镜像文件,需要启动一个本地仓库,可以使用以下命令启动: ``` docker run -d -p 5000:5000 --restart=always --name registry registry:2 ``` 这将在容器中启动一个名为 registry 的本地仓库,并将其映射到主机的 5000 端口。 3. 推送镜像到本地仓库:接下来,需要将标记后的镜像推送到本地仓库中。可以使用以下命令将其推送: ``` docker push 127.0.0.1:5000/hello-world:latest ``` 这将把镜像文件上传到本地仓库中。 4. 创建 Kubernetes Pod:最后,需要创建一个 Kubernetes Pod,并将其配置为使用刚才推送到本地仓库中的镜像。可以使用以下 YAML 文件来创建 Pod: ``` apiVersion: v1 kind: Pod metadata: name: hello-world spec: containers: - name: hello-world image: 127.0.0.1:5000/hello-world:latest ports: - containerPort: 80 ``` 将上述 YAML 文件保存为 hello-world.yaml,并使用以下命令创建 Pod: ``` kubectl create -f hello-world.yaml ``` 这将创建一个名为 hello-world 的 Pod,并将其配置为使用本地仓库中的 hello-world 镜像

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

无碍-心态而已

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值