无法在本地小型安装中安装舵柄
无法在本地小型安装中安装舵柄
提问于 2019-07-07 14:56:30
我有一个使用超级工具包VM的本地迷你库设置。我在我的系统上安装了helm，并且成功安装了客户机，但是tiller没有在集群中安装。吊舱的状态是ImagePullBackOff
我试着安装不同版本的图像，但仍然失败。如果我在我的系统中做一个正常的码头拉同样的图像，它可以工作。
命令helm version给出了这个结果：
Client: &version.Version{SemVer:"v2.12.1", GitCommit:"02a47c7249b1fc6d8fd3b94e6b4babf9d818144e", GitTreeState:"clean"}
Error: could not find a ready tiller pod命令kubectl -n kube-system get pods给出了以下结果：
NAME READY STATUS RESTARTS AGE
coredns-fb8b8dccf-bh6w7 1/1 Running 0 146m
coredns-fb8b8dccf-gskc8 1/1 Running 1 146m
etcd-minikube 1/1 Running 0 145m
kube-addon-manager-minikube 1/1 Running 0 145m
kube-apiserver-minikube 1/1 Running 0 145m
kube-controller-manager-minikube 1/1 Running 0 145m
kube-proxy-jqb9b 1/1 Running 0 146m
kube-scheduler-minikube 1/1 Running 0 145m
storage-provisioner 1/1 Running 0 146m
tiller-deploy-548df79d66-xsngk 0/1 ImagePullBackOff 0 27m命令kubectl -n kube-system describe pod tiller-deploy-548df79d66-xsngk可以获得以下结果：
Name: tiller-deploy-548df79d66-xsngk
Namespace: kube-system
Priority: 0
PriorityClassName: <none>
Node: minikube/192.168.64.56
Start Time: Sat, 06 Jul 2019 22:41:54 +0530
Labels: app=helm
name=tiller
pod-template-hash=548df79d66
Annotations: <none>
Status: Pending
IP: 172.17.0.5
Controlled By: ReplicaSet/tiller-deploy-548df79d66
Containers:
tiller:
Container ID:
Image: gcr.io/kubernetes-helm/tiller:v2.12.1
Image ID:
Ports: 44134/TCP, 44135/TCP
Host Ports: 0/TCP, 0/TCP
State: Waiting
Reason: ImagePullBackOff
Ready: False
Restart Count: 0
Liveness: http-get http://:44135/liveness delay=1s timeout=1s period=10s #success=1 #failure=3
Readiness: http-get http://:44135/readiness delay=1s timeout=1s period=10s #success=1 #failure=3
Environment:
TILLER_NAMESPACE: kube-system
TILLER_HISTORY_MAX: 0
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-6w54d (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
default-token-6w54d:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-6w54d
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 21h default-scheduler Successfully assigned kube-system/tiller-deploy-548df79d66-xsngk to minikube
Warning Failed 21h kubelet, minikube Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.12.1": rpc error: code = Unknown desc = Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on 192.168.64.1:53: read udp 192.168.64.56:46818->192.168.64.1:53: read: connection refused
Warning Failed 21h kubelet, minikube Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.12.1": rpc error: code = Unknown desc = Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on 192.168.64.1:53: read udp 192.168.64.56:32929->192.168.64.1:53: read: connection refused
Warning Failed 21h kubelet, minikube Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.12.1": rpc error: code = Unknown desc = Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on 192.168.64.1:53: read udp 192.168.64.56:59446->192.168.64.1:53: read: connection refused
Warning Failed 21h (x4 over 21h) kubelet, minikube Error: ErrImagePull
Normal Pulling 21h (x4 over 21h) kubelet, minikube Pulling image "gcr.io/kubernetes-helm/tiller:v2.12.1"
Warning Failed 21h kubelet, minikube Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.12.1": rpc error: code = Unknown desc = Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on 192.168.64.1:53: read udp 192.168.64.56:58643->192.168.64.1:53: read: connection refused
Warning Failed 21h (x7 over 21h) kubelet, minikube Error: ImagePullBackOff
Normal BackOff 21h (x110 over 21h) kubelet, minikube Back-off pulling image "gcr.io/kubernetes-helm/tiller:v2.12.1"如果这有帮助的话，我不会支持任何代理。
更新1:
我试着手动提取对接者的图像，但是我得到了错误：
Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on 192.168.64.1:53: read udp 192.168.64.56:46912->192.168.64.1:53: read: connection refused更新2:
这个问题不仅是为了掌舵，也是为了任何形象。我用Quay.io获取图像，而集群也无法到达，我尝试了卡夫卡，但也失败了。如果我的ssh进入小库贝，更新立体式，然后手动做一个码头拉在迷你库贝，吊舱旋转。
回答 1
Stack Overflow用户
发布于 2019-07-07 18:09:01
eval $(minikube docker-env)然后像这样画出分蘖的图像，
docker pull gcr.io/kubernetes-helm/tiller:v2.12.1现在，minikube将下载图像。使用此命令删除现有的分蘖荚，
kubectl delete pod tiller-deploy-548df79d66-xsngk -n kube-system解释是这样的。因为看起来在分蘖部署中没有提到ImagePullPolicy，而且默认的ImagePullPolicy是IfNotPresent，minikube可能不会下载映像，并且会尝试使用已经加载的映像。
Update：helm无法安装舵柄的原因是，minikube容器的resolv.conf文件在创建集群时从以前的网络连接到nameserver 192.168.64.1。因此，minikube无法拉起舵坞的图像。这可能是因为对接者根据连接到的网络设置名称服务器。
这个链接可能会有所帮助。
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/56923258
复制相关文章
相似问题
腾讯云开发者
