1

我正在尝试在我的机器上启动 minishift。它成功创建了 minishift VM，但引发了超时错误。

配置：

Minishift 版本：v1.34.0+f5db7cb

操作系统：Windows 10

管理程序：Virtual Box v6.0.10

PS C:\WINDOWS\system32> minishift start

-- Starting OpenShift cluster .......................................................................Error during 'cluster up' execution: Error starting the cluster. ssh command error:
command : /var/lib/minishift/bin/oc cluster up --image 'openshift/origin-${component}:v3.11.0' --public-hostname 192.168.99.100 --routing-suffix 192.168.99.100.nip.io --base-dir /var/lib/minishift/base
err : exit status 1
output : Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11.0 is available ...
Pulling image openshift/origin-cli:v3.11.0
E0725 17:15:42.919928 5316 helper.go:173] Reading docker config from /home/docker/.docker/config.json failed: open /home/docker/.docker/config.json: no such file or directory, will attempt to pull image docker.io/openshift/origin-cli:v3.11.0 anonymously
Image pull complete
E0725 17:15:44.643860 5316 helper.go:173] Reading docker config from /home/docker/.docker/config.json failed: open /home/docker/.docker/config.json: no such file or directory, will attempt to pull image docker.io/openshift/origin-node:v3.11.0 anonymously
Pulling image openshift/origin-node:v3.11.0
Pulled 5/6 layers, 85% complete
Pulled 6/6 layers, 100% complete
Extracting
Image pull complete
Checking type of volume mount ...
Determining server IP ...
Using public hostname IP 192.168.99.100 as the host IP
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11.0 is available ...
I0725 17:16:20.775520 5316 config.go:40] Running "create-master-config"
Starting OpenShift using openshift/origin-control-plane:v3.11.0 ...
I0725 17:16:31.108342 5316 config.go:46] Running "create-node-config"
I0725 17:16:35.237968 5316 flags.go:30] Running "create-kubelet-flags"
I0725 17:16:36.785234 5316 run_kubelet.go:49] Running "start-kubelet"
I0725 17:16:37.288388 5316 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0725 17:21:37.300062 5316 run_self_hosted.go:571] API server error: Get https://192.168.99.100:8443/healthz?timeout=32s: dial tcp 192.168.99.100:8443: connect: connection refused ()
Error: timed out waiting for the condition

预期结果：它应该为我提供打开 Web 控制台的无错误链接

4

1 回答 1

2

这有时也会发生在我身上。

解决方案包括：

  • minishift stop && minishift start（将其关闭并重新打开）
  • 重新启动 Windows（可能 VBox 再次损坏了自己）

有关我的 minishift 设置的更多信息在这里：

http://divby0.blogspot.com/2019/07/configuring-minishift-for-use-with.html

值得我使用 Windows 10 中的 linux shell 组合来与 minishift / docker 守护进程交互：

  • Git Bash（通常是最好的）
  • Docker Toolbox（在 Git Bash shell 中无法运行时的 B 计划）
  • WSL（基于 ubuntu，绝望中的 C 计划）
于 2019-07-26T17:30:29.010 回答