无法启动MiniKube:卡在启动群集组件上

时间:2019-01-04 07:06:13

标签: minikube

我是minikube的新手。我按照以下步骤在oracle linux 7.5(内核3.10.0-327.28.3.el7.x86_64)上安装minikube

curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 && sudo install minikube-linux-amd64 /usr/local/bin/minikube

安装后,我运行了minikube

sudo minikube start --vm-driver=none

Minikube死于

    sudo minikube start --vm-driver=none
    Starting local Kubernetes v1.12.4 cluster...
    Starting VM...
    Waiting for SSH to be available...
    Detecting the provisioner...
    Setting Docker configuration on the remote daemon...
    Getting VM IP address...
    Moving files into cluster...
    Setting up certs...
    Connecting to cluster...
    Setting up kubeconfig...
    Stopping extra container runtimes...
    Starting cluster components...
E0105 13:00:41.436961   19330 start.go:343] Error starting cluster:  timed out waiting to elevate kube-system RBAC privileges: Temporary Error: creating clusterrolebinding: Post https://192.168.99.100:8443/apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings?timeout=1m0s: net/http: TLS handshake timeout
Temporary Error: creating clusterrolebinding: Post https://192.168.99.100:8443/apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings?timeout=1m0s: net/http: TLS handshake timeout
Temporary Error: creating clusterrolebinding: Post https://192.168.99.100:8443/apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings?timeout=1m0s: net/http: TLS handshake timeout
Temporary Error: creating clusterrolebinding: Post https://192.168.99.100:8443/apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings?timeout=1m0s: net/http: TLS handshake timeout
Temporary Error: creating clusterrolebinding: Post https://192.168.99.100:8443/apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings?timeout=1m0s: net/http: TLS handshake timeout

我还检查了日志,发现它陷入了某种循环并重试,但是我听不懂

I0105 12:24:24.522907   19330 utils.go:224] > Your Kubernetes master has initialized successfully!
I0105 12:24:24.522916   19330 utils.go:224] > To start using your cluster, you need to run the following as a regular user:
I0105 12:24:24.522919   19330 utils.go:224] >   mkdir -p $HOME/.kube
I0105 12:24:24.522925   19330 utils.go:224] >   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
I0105 12:24:24.522929   19330 utils.go:224] >   sudo chown $(id -u):$(id -g) $HOME/.kube/config
I0105 12:24:24.522934   19330 utils.go:224] > You should now deploy a pod network to the cluster.
I0105 12:24:24.522944   19330 utils.go:224] > Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
I0105 12:24:24.522950   19330 utils.go:224] >   https://kubernetes.io/docs/concepts/cluster-administration/addons/
I0105 12:24:24.522957   19330 utils.go:224] > You can now join any number of machines by running the following on each node
I0105 12:24:24.522959   19330 utils.go:224] > as root:
I0105 12:24:24.522972   19330 utils.go:224] >   kubeadm join localhost:8443 --token 5apexw.uv7nfpirz4on2e33 --discovery-token-ca-cert-hash sha256:6dcf73220b8bc229269bb8c6a350592fe6b0cd068ef8f336163cc5b3a384990e
I0105 12:24:45.792762   19330 utils.go:117] sleeping 500ms
I0105 12:24:46.292883   19330 utils.go:106] retry loop 1
I0105 12:25:07.561761   19330 utils.go:117] sleeping 500ms
I0105 12:25:08.062042   19330 utils.go:106] retry loop 2
I0105 12:25:29.330434   19330 utils.go:117] sleeping 500ms
I0105 12:25:29.830625   19330 utils.go:106] retry loop 3
I0105 12:25:51.096835   19330 utils.go:117] sleeping 500ms
I0105 12:25:51.597099   19330 utils.go:106] retry loop 4

1 个答案:

答案 0 :(得分:0)

我想您是在AWS中完成的。 删除所有内容并重新创建。只需复制即可,一切正常。

全部删除:

minikube delete
rm -rf ~/.minikube

我从乞讨中走出来(在根下):

curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 && sudo install minikube-linux-amd64 /usr/local/bin/minikube

sudo yum install docker-engine

systemctl enable docker.service

systemctl start docker.service

minikube start --vm-driver=none

结果:

  

=========================================启动本地Kubernetes v1.12.4集群...

     

正在启动VM ...

     

正在获取虚拟机IP地址...

     

正在将文件移至群集...

     

设置证书...

     

正在连接群集...

     

设置kubeconfig ...

     

停止额外的容器运行时...

     

启动集群组件...

     

正在验证kubelet的健康状况...

     

验证apiserver的运行状况... Kubectl现在已配置为使用   集群。

     

==================

     

警告:建议不要以个人身份运行无人驾驶   工作站“无”驱动程序将运行不安全的kubernetes   apiserver作为根目录,可能使主机容易受到CSRF攻击

     

使用none驱动程序时,kubectl配置和凭据   生成的文件将归root所有,并显示在root主目录中   目录。您将需要将文件移动到适当的位置   然后设置正确的权限。下面是一个示例:

     

sudo mv /root/.kube $ HOME / .kube#这将覆盖以前的任何配置   须藤chown -R $ USER $ HOME / .kube   须藤chgrp -R $ USER $ HOME / .kube

     

sudo mv /root/.minikube $ HOME / .minikube#这将覆盖以前的任何配置    须藤chown -R $ USER $ HOME / .minikube    须藤chgrp -R $ USER $ HOME / .minikube

     

这也可以通过设置env var自动完成   CHANGE_MINIKUBE_NONE_USER = true从配置文件加载缓存的图像。

     

一切看起来都很不错。请尽情享受minikube!