Windowsのdockerでhelmを使用するとエラーが報告されます。理由は、ティラーのイメージのプルが失敗するためです。処理方法は次のとおりです
。1. tiller-deploy-xxxコンテナー名を表示します。kubectlget pods --namespace kube-system
2.詳細を表示：kubectl --namespace kube-system describe pod tiller-deploy-7d6dbd958-sb92l
エラーの内容を確認できます。
Normal Scheduled 22m default-scheduler Successfully assigned kube-system/tiller-deploy-7d6dbd958-sb92l to docker-desktop
Normal Pulling 20m (x4 over 22m) kubelet, docker-desktop Pulling image "gcr.io/kubernetes-helm/tiller:v2.16.6"
Warning Failed 19m (x4 over 22m) kubelet, docker-desktop Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.16.6": rpc error: code = Unknown desc = Error response from daemon: Get https://gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Warning Failed 19m (x4 over 22m) kubelet, docker-desktop Error: ErrImagePull
Normal BackOff 17m (x15 over 22m) kubelet, docker-desktop Back-off pulling image "gcr.io/kubernetes-helm/tiller:v2.16.6"
Warning Failed 7m10s (x56 over 22m) kubelet, docker-desktop Error: ImagePullBackOff
3. Alibaba Cloudプルでイメージの名前を変更します
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.16.6
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.16.6 gcr.io/kubernetes-helm/tiller:v2.16.6
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.16.6
4.コンテナーtiller-deploy-xxxを再起動します