k8s在创建dashboard的时候，提示镜像不无法下载，但实际本地已经有镜像了！
现象：1、在安装完k8s以后，加载ui面：kubectl create -f kubernetes-dashboard.yaml 2、查看容器状态：[root@k8s-master software]# kubectl get pods --namespace kube-systemNAME READY STATUS RESTARTS AGEkuberne...显示全部
查看其它 1 个回答wanggeng的回答
初步怀疑是你的docker环境问题，你可以检查一下docker环境，比如网络代理设置。
浏览19326
- 您说的网络代理设置是什么？如何检查呢？
- 在yaml文件中指定镜像拉取的策略，默认是awlays，修改为IfNotPresent
- [此评论已删除]
- 修改了以后，提示的错误信息依然相同，信息如下： [root@k8s-master software]# kubectl delete -f kubernetes-dashboard.yaml serviceaccount "kubernetes-dashboard" deleted clusterrolebinding "kubernetes-dashboard" deleted deployment "kubernetes-dashboard" deleted service "kubernetes-dashboard" deleted [root@k8s-master software]# kubectl create -f kubernetes-dashboard.yaml serviceaccount "kubernetes-dashboard" created clusterrolebinding "kubernetes-dashboard" created deployment "kubernetes-dashboard" created service "kubernetes-dashboard" created [root@k8s-master software]# kubectl get pods --namespace kube-system NAME READY STATUS RESTARTS AGE kubernetes-dashboard-3852341777-r9txq 0/1 ContainerCreating 0 10s [root@k8s-master software]# kubectl describe pod kubernetes-dashboard-3852341777-r9txq --namespace kube-system Name: kubernetes-dashboard-3852341777-r9txq Namespace: kube-system Node: 10.1.108.79/10.1.108.79 Start Time: Tue, 27 Jun 2017 20:14:02 +0800 Labels: k8s-app=kubernetes-dashboard pod-template-hash=3852341777 Annotations: kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"kube-system","name":"kubernetes-dashboard-3852341777","uid":"1a9f1b34-5b32-11e7-a... Status: Pending IP: Controllers: ReplicaSet/kubernetes-dashboard-3852341777 Containers: kubernetes-dashboard: Container ID: Image: registry.sinosafe.com.cn:5000/sinosafe/kubernetes/kubernetes-dashboard:1.5.1 Image ID: Port: 9090/TCP Args: --apiserver-host=http://10.1.108.77:8080 State: Waiting Reason: ContainerCreating Ready: False Restart Count: 0 Liveness: http-get http://:9090/ delay=30s timeout=30s period=10s #success=1 #failure=3 Environment: <none> Mounts: <none> Conditions: Type Status Initialized True Ready False PodScheduled True Volumes: <none> QoS Class: BestEffort Node-Selectors: <none> Tolerations: node-role.kubernetes.io/master=:NoSchedule Events: FirstSeen LastSeen Count From SubObjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 6m 6m 1 default-scheduler Normal Scheduled Successfully assigned kubernetes-dashboard-3852341777-r9txq to 10.1.108.79 5m 5m 1 kubelet, 10.1.108.79 Warning FailedSync Error syncing pod, skipping: failed to "CreatePodSandbox" for "kubernetes-dashboard-3852341777-r9txq_kube-system(1aa5e3fc-5b32-11e7-a69f-842b2b5e0f11)" with CreatePodSandboxError: "CreatePodSandbox for pod \"kubernetes-dashboard-3852341777-r9txq_kube-system(1aa5e3fc-5b32-11e7-a69f-842b2b5e0f11)\" failed: rpc error: code = 2 desc = unable to pull sandbox image \"gcr.io/google_containers/pause-amd64:3.0\": Error response from daemon: {\"message\":\"Get https://gcr.io/v1/_ping: dial tcp 74.125.203.82:443: i/o timeout\"}" 4m 26s 5 kubelet, 10.1.108.79 Warning FailedSync Error syncing pod, skipping: failed to "CreatePodSandbox" for "kubernetes-dashboard-3852341777-r9txq_kube-system(1aa5e3fc-5b32-11e7-a69f-842b2b5e0f11)" with CreatePodSandboxError: "CreatePodSandbox for pod \"kubernetes-dashboard-3852341777-r9txq_kube-system(1aa5e3fc-5b32-11e7-a69f-842b2b5e0f11)\" failed: rpc error: code = 2 desc = unable to pull sandbox image \"gcr.io/google_containers/pause-amd64:3.0\": Error response from daemon: {\"message\":\"Get https://gcr.io/v1/_ping: dial tcp 74.125.204.82:443: i/o timeout\"}" 6m 11s 7 kubelet, 10.1.108.79 Warning MissingClusterDNS kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to DNSDefault policy
- [此评论已删除]
- yaml文件如下： apiVersion: v1 kind: ServiceAccount metadata: labels: k8s-app: kubernetes-dashboard name: kubernetes-dashboard namespace: kube-system --- apiVersion: rbac.authorization.k8s.io/v1beta1 kind: ClusterRoleBinding metadata: name: kubernetes-dashboard labels: k8s-app: kubernetes-dashboard roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: cluster-admin subjects: - kind: ServiceAccount name: kubernetes-dashboard namespace: kube-system --- kind: Deployment apiVersion: extensions/v1beta1 metadata: labels: k8s-app: kubernetes-dashboard name: kubernetes-dashboard namespace: kube-system spec: replicas: 1 revisionHistoryLimit: 10 selector: matchLabels: k8s-app: kubernetes-dashboard template: metadata: labels: k8s-app: kubernetes-dashboard spec: containers: - name: kubernetes-dashboard image: registry.sinosafe.com.cn:5000/sinosafe/kubernetes/kubernetes-dashboard:1.5.1 imagePullPolicy: IfNotPresent ports: - containerPort: 9090 protocol: TCP args: # Uncomment the following line to manually specify Kubernetes API server Host # If not specified, Dashboard will attempt to auto discover the API server and connect # to it. Uncomment only if the default does not work. - --apiserver-host=http://10.1.108.77:8080 livenessProbe: httpGet: path: / port: 9090 initialDelaySeconds: 30 timeoutSeconds: 30 serviceAccountName: kubernetes-dashboard # Comment the following tolerations if Dashboard must not be deployed on master tolerations: - key: node-role.kubernetes.io/master effect: NoSchedule --- kind: Service apiVersion: v1 metadata: labels: k8s-app: kubernetes-dashboard name: kubernetes-dashboard namespace: kube-system spec: ports: - port: 80 targetPort: 9090 selector: k8s-app: kubernetes-dashboard
- 昨天在测试的时候提示报错，但是今天早上再次查询的时候，发现已经正常了：估计应该和镜像拉取策略有关系，因为昨天只修改了镜像拉取策略，目前已经正常： [root@k8s-master ~]# kubectl get pods --namespace kube-system NAME READY STATUS RESTARTS AGE kubernetes-dashboard-3852341777-r9txq 1/1 Running 0 12h