私はubuntuを実行している私のデスクトップにminikubeでkubernetes体験版をインストールしました。しかし、ポッドを持ち出すことにはいくつかの問題があるようです。 Kubectlはポッドを取得します--all-namespacesは、ContainerCreating状態のすべてのポッドを表示し、Readyに移行しません。ポッド・キュビットを起動する際にエラーが発生しました。ポッドはContainerCreating状態のまま残っています
も、私はkubernetes-dahboardを行うとき、私は
Waiting, endpoint for service is not ready yet.
Minikubeバージョンを取得：の/ etc/OS-から
OS（例：v0.20.0
環境をリリース）：Ubuntu 12.04.5 LTS
VMドライバ "DriverName"： "virtualbox"
ISOバージョン "Boot2DockerURL"： "ファイル：///home/nszig/.minikube/cache/iso/minikube-v0.20.0.iso" 私はUbuntuでminikubeとkubectlをインストールしている
。しかし、私はCLIとGUIを通してダッシュボードにアクセスすることはできません。
http://127.0.0.1:8001/uiは、ダッシュボードを開きません以下のエラーにCLI上
{ "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "no endpoints available for service "kubernetes-dashboard"", "reason": "ServiceUnavailable", "code": 503 }
そしてminikubeダッシュボードを与える：出力
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
.......
Could not find finalized endpoint being pointed to by kubernetes-dashboard: Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
kubectlバージョン：Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.0", GitCommit:"d3ada0119e776222f11ec7945e6d860061339aad", GitTreeState:"clean", BuildDate:"2017-06-29T23:15:59Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4", GitCommit:"d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae", GitTreeState:"dirty", BuildDate:"2017-06-22T04:31:09Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
minikubeログもエラーを報告します以下： .....
Jul 10 08:46:12 minikube localkube[3237]: I0710 08:46:12.901880 3237 kuberuntime_manager.go:458] Container {Name:php-redis Image:gcr.io/google-samples/gb-frontend:v4 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:80 Protocol:TCP HostIP:}] EnvFrom:[] Env:[{Name:GET_HOSTS_FROM Value:dns ValueFrom:nil}] Resources:{Limits:map[] Requests:map[cpu:{i:{value:100 scale:-3} d:{Dec:} s:100m Format:DecimalSI} memory:{i:{value:104857600 scale:0} d:{Dec:} s:100Mi Format:BinarySI}]} VolumeMounts:[{Name:default-token-gqtvf ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath:}] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it. Jul 10 08:46:14 minikube localkube[3237]: E0710 08:46:14.139555 3237 remote_runtime.go:86] RunPodSandbox from runtime service failed: rpc error: code = 2 desc = unable to pull sandbox image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v1/_ping: x509: certificate signed by unknown authority ....
Name: kubernetes-dashboard-2039414953-czptd Namespace: kube-system Node: minikube/192.168.99.102 Start Time: Fri, 14 Jul 2017 09:31:58 +0530 Labels: k8s-app=kubernetes-dashboard pod-template-hash=2039414953 Annotations: kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"kube-system","name":"kubernetes-dashboard-2039414953","uid":"2eb39682-6849-11e7-8... Status: Pending IP: Created By: ReplicaSet/kubernetes-dashboard-2039414953 Controlled By: ReplicaSet/kubernetes-dashboard-2039414953 Containers:
kubernetes-dashboard: Container ID: Image: gcr.io/google_containers/kubernetes-dashboard-amd64:v1.6.1 Image ID:
Port: 9090/TCP 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: Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kubernetes-dashboard-token-12gdj (ro) Conditions: Type Status
Initialized True Ready False PodScheduled True Volumes:
kubernetes-dashboard-token-12gdj: Type: Secret (a volume populated by a Secret) SecretName: kubernetes-dashboard-token-12gdj Optional: false QoS Class: BestEffort Node-Selectors: Tolerations: node-role.kubernetes.io/master:NoSchedule Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ ------- 1h 11s 443 kubelet, minikube Warning FailedSync Error syncing pod, skipping: failed to "CreatePodSandbox" for "kubernetes-dashboard-2039414953-czptd_kube-system(2eb57d9b-6849-11e7-8a56-080027206461)" with CreatePodSandboxError: "CreatePodSandbox for pod \"kubernetes-dashboard-2039414953-czptd_kube-system(2eb57d9b-6849-11e7-8a56-080027206461)\" failed: rpc error: code = 2 desc = unable to pull sandbox image \"gcr.io/google_containers/pause-amd64:3.0\": Error response from daemon: Get https://gcr.io/v1/_ping : x509: certificate signed by unknown authority"
あなたに役立つ情報ではありません。たとえば、使用しているドライバはわかりません。私の勘違いは、十分なリソースが割り当てられていないことです。たとえば、 '--memory'パラメータでRAMを増やしてみてください。初心者はhttps://kubernetes.io/docs/getting-started-guides/minikubeをご覧ください。 –
@MichaelHausenblasリンクをありがとうございます。私は詳細を含むように私の質問を編集しました – NSP
私はあなたがヒットするかもしれないと思うhttps://github.com/kubernetes/minikube/issues/311 –