Skip to content

部署asm实例时,即使是在香港节点,argo-workflows镜像下载也会失败 #10

Open

Description

@leveryd
➜  ~ kubectl get pods -n test
NAME                                                      READY   STATUS             RESTARTS        AGE
argo-workflows-app-server-d9b5c846b-pzhw4                 0/1     ImagePullBackOff   0               10m
argo-workflows-app-workflow-controller-74d9ddd8c5-bq2ns   0/1     ImagePullBackOff   0               10m
console-56986fc6ff-r5nqm                                  3/3     Running            4 (7m35s ago)   10m
crawler-7cd599fd46-zfhn5                                  2/2     Running            0               10m
minio-6c74487844-zqd4d                                    1/1     Running            0               10m
postgres-546d9d68b-9rjjr                                  0/1     ImagePullBackOff   0               10m
release-name-kafka-0                                      0/1     Pending            0               10m
release-name-zookeeper-0                                  0/1     Pending            0               10m
xray-proxy-795f9bf696-9qdp4                               1/1     Running            0               10m
xray-webhook-6fb5544f8f-9dbzj                             1/1     Running            0               10m
➜  ~ kubectl describe pod argo-workflows-app-server-d9b5c846b-pzhw4 -n test
Name:         argo-workflows-app-server-d9b5c846b-pzhw4
Namespace:    test
...
Events:
  Type     Reason     Age                     From               Message
  ----     ------     ----                    ----               -------
  Normal   Scheduled  9m59s                   default-scheduler  Successfully assigned test/argo-workflows-app-server-d9b5c846b-pzhw4 to 192.168.0.7
  Normal   Pulling    7m52s (x4 over 9m58s)   kubelet            Pulling image "quay.io/argoproj/argocli:v3.4.4"
  Warning  Failed     7m37s (x4 over 9m43s)   kubelet            Failed to pull image "quay.io/argoproj/argocli:v3.4.4": rpc error: code = Unknown desc = Error response from daemon: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
  Warning  Failed     7m37s (x4 over 9m43s)   kubelet            Error: ErrImagePull
  Warning  Failed     7m13s (x6 over 9m42s)   kubelet            Error: ImagePullBackOff
  Normal   BackOff    4m48s (x15 over 9m42s)  kubelet            Back-off pulling image "quay.io/argoproj/argocli:v3.4.4"
➜  ~ kubectl describe pod postgres-546d9d68b-9rjjr -n test
...
Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  16m                  default-scheduler  Successfully assigned test/postgres-546d9d68b-9rjjr to 192.168.0.7
  Normal   Pulling    10m (x4 over 16m)    kubelet            Pulling image "postgres:12-alpine"
  Warning  Failed     9m11s (x4 over 15m)  kubelet            Error: ErrImagePull
  Warning  Failed     8m42s (x7 over 15m)  kubelet            Error: ImagePullBackOff
  Warning  Failed     6m11s (x5 over 15m)  kubelet            Failed to pull image "postgres:12-alpine": rpc error: code = Unknown desc = Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
  Normal   BackOff    106s (x24 over 15m)  kubelet            Back-off pulling image "postgres:12-alpine"

带来的影响:部署失败

可能的解决办法:

  • 在节点上多执行几次docker pull获取对应的镜像
  • 将quay.io/argoproj/argocli:v3.4.4等镜像同步到国内的镜像仓库,同时修改本仓库yaml种对应的镜像名
  • 使用国内docker镜像加速

镜像加速配置,比如下面这样

[root@192 ~]# cat /etc/docker/daemon.json
{
  "exec-opts": ["native.cgroupdriver=systemd"],
  "registry-mirrors": ["https://bdasxx8n.mirror.aliyuncs.com"],
}

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions