我使用镜像制作器的时候发现我的有两个镜像出问题了
[root@localhost ~]# kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system calico-kube-controllers-8545b68dd4-ppnhg 1/1 Running 4 15d
kube-system calico-node-6fjmn 1/1 Running 11 15d
kube-system coredns-7f87749d6c-btwnc 1/1 Running 5 15d
kube-system coredns-7f87749d6c-tgltz 1/1 Running 6 15d
kube-system kube-apiserver-localhost.localdomain 1/1 Running 9 15d
kube-system kube-controller-manager-localhost.localdomain 1/1 Running 15 15d
kube-system kube-proxy-6nb8r 1/1 Running 4 15d
kube-system kube-scheduler-localhost.localdomain 1/1 Running 14 15d
kube-system nodelocaldns-wvxf5 1/1 Running 4 15d
kube-system openebs-localpv-provisioner-5cddd6cbfc-fjvqr 0/1 ImagePullBackOff 19 15d
kube-system snapshot-controller-0 1/1 Running 4 15d
kubesphere-controls-system default-http-backend-5d7c68c698-q2gsh 1/1 Running 28 15d
kubesphere-controls-system kubectl-admin-68dc989bf8-rz5lg 1/1 Running 4 15d
kubesphere-controls-system kubectl-admin1-5758fbb6ff-gkgrp 1/1 Running 4 30h
kubesphere-devops-system ks-jenkins-8957dc768-kg8gc 1/1 Running 6 15d
kubesphere-devops-system s2ioperator-0 1/1 Running 4 15d
kubesphere-monitoring-system alertmanager-main-0 2/2 Running 10 15d
kubesphere-monitoring-system kube-state-metrics-577b8b4cf-jcmpr 3/3 Running 12 15d
kubesphere-monitoring-system node-exporter-kqcmp 2/2 Running 8 15d
kubesphere-monitoring-system notification-manager-deployment-97dfccc89-6f2ns 1/1 Running 4 15d
kubesphere-monitoring-system notification-manager-operator-59cbfc566b-qgdwf 2/2 Running 29 15d
kubesphere-monitoring-system prometheus-k8s-0 3/3 Running 15 15d
kubesphere-monitoring-system prometheus-operator-8f97cb8c6-ds6fq 2/2 Running 8 15d
kubesphere-system ks-apiserver-574658c9f5-h2h7m 1/1 Running 5 15d
kubesphere-system ks-console-58b965dbf5-tg72f 1/1 Running 4 15d
kubesphere-system ks-controller-manager-74b85b9fd6-5j29x 1/1 Running 20 15d
kubesphere-system ks-installer-769994b6ff-8ffg4 0/1 ImagePullBackOff 0 15d
kubesphere-system minio-d98b7c954-bxwnh 1/1 Running 7 15d
kubesphere-system openldap-0 1/1 Running 5 15d
mkcloud lpoiop-v1-846f667856-7tgz2 1/1 Running 4 32h
mkcloud mynginx-v1-9b4cdc685-8d5xk 1/1 Running 4 2d3h
describe之后发现是镜像拉不下来。
Events:
Type Reason Age From Message
Warning Unhealthy 144m (x55 over 15d) kubelet Liveness probe failed:
Normal Killing 144m (x6 over 15d) kubelet Container openebs-provisioner-hostpath failed liveness probe, will be restarted
Warning Failed 143m kubelet Failed to pull image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”: rpc error: code = Unknown desc = Error response from daemon: Get “https://registry.cn-beijing.aliyuncs.com/v2/”: dial tcp 47.95.181.38:443: connect: connection reset by peer
Warning Failed 143m kubelet Failed to pull image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”: rpc error: code = Unknown desc = Error response from daemon: Get “https://registry.cn-beijing.aliyuncs.com/v2/”: write tcp 192.168.80.130:33806->47.95.181.38:443: write: connection reset by peer
Warning Failed 142m kubelet Failed to pull image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”: rpc error: code = Unknown desc = Error response from daemon: Get “https://registry.cn-beijing.aliyuncs.com/v2/”: read tcp 192.168.80.130:34216->47.95.181.38:443: read: connection reset by peer
Warning Failed 142m (x3 over 143m) kubelet Error: ErrImagePull
Warning BackOff 141m (x8 over 143m) kubelet Back-off restarting failed container
Normal Pulling 141m (x24 over 15d) kubelet Pulling image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”
Warning Failed 125m kubelet Error: ImageInspectError
Warning InspectFailed 125m kubelet Failed to inspect image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”: rpc error: code = DeadlineExceeded desc = context deadline exceeded
Normal BackOff 111m (x93 over 143m) kubelet Back-off pulling image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”
Warning Failed 66m (x287 over 143m) kubelet Error: ImagePullBackOff
Warning Failed 60m kubelet Failed to pull image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”: rpc error: code = Unknown desc = Error response from daemon: Get “https://registry.cn-beijing.aliyuncs.com/v2/”: read tcp 192.168.80.130:40236->47.95.181.38:443: read: connection reset by peer
Warning Failed 60m kubelet Failed to pull image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”: rpc error: code = Unknown desc = Error response from daemon: Get “https://registry.cn-beijing.aliyuncs.com/v2/”: read tcp 192.168.80.130:40644->47.95.181.38:443: read: connection reset by peer
Warning Failed 59m kubelet Failed to pull image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”: rpc error: code = Unknown desc = Error response from daemon: Get “https://registry.cn-beijing.aliyuncs.com/v2/”: read tcp 192.168.80.130:41348->47.95.181.38:443: read: connection reset by peer
Normal Pulling 58m (x4 over 60m) kubelet Pulling image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”
Warning Failed 58m (x4 over 60m) kubelet Error: ErrImagePull
Warning Failed 58m kubelet Failed to pull image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”: rpc error: code = Unknown desc = Error response from daemon: Get “https://registry.cn-beijing.aliyuncs.com/v2/”: read tcp 192.168.80.130:42040->47.95.181.38:443: read: connection reset by peer
Normal SandboxChanged 27m (x9 over 61m) kubelet Pod sandbox changed, it will be killed and re-created.
Normal BackOff 16m (x182 over 59m) kubelet Back-off pulling image “registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1”
Warning Failed 92s (x249 over 59m) kubelet Error: ImagePullBackOff
急求解答。
docker pull registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1
[root@localhost ~]# docker pull registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:2.10.1
Error response from daemon: Get “https://registry.cn-beijing.aliyuncs.com/v2/”: read tcp 192.168.80.130:41722->47.95.181.38:443: read: connection reset by peer
有人有经验吗