Bil*_*ill 5 redhat-containers minishift
我正在尝试启动 minishift/cdk,但一直出现错误。在阅读了许多其他具有类似错误的报告后,尚不清楚解决方案可能是什么。
minishift ssh进入服务器C:\cdk>minishift start
-- Starting profile 'minishift'
<snip>
-- Copying oc binary from the OpenShift container image to VM ... OK
-- Starting OpenShift cluster .................................................................Error during 'cluster up' execution: Error starting the cluster. ssh command error:
command : /var/lib/minishift/bin/oc cluster up --image 'registry.access.redhat.com/openshift3/ose-${component}:v3.11.104' --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 registry.access.redhat.com/openshift3/ose-control-plane:v3.11.104 is available ...
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 registry.access.redhat.com/openshift3/ose-control-plane:v3.11.104 is available ...
Starting OpenShift using registry.access.redhat.com/openshift3/ose-control-plane:v3.11.104 ...
I0809 19:32:23.621656 2964 flags.go:30] Running "create-kubelet-flags"
I0809 19:32:24.474547 2964 run_kubelet.go:49] Running "start-kubelet"
I0809 19:32:24.921489 2964 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0809 19:37:24.935726 2964 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
Run Code Online (Sandbox Code Playgroud)
小智 3
您也可以在此处报告此问题,或者您可以在现有问题下添加评论。
除此之外,您可以尝试从头开始:
minishift deleteminishift start但请注意,这将清除您在 minishift/local openshift 上使用的任何实际配置和应用程序,请参阅更多参考。不幸的是,没有比尝试重新开始更好的解决方法了。
| 归档时间: |
|
| 查看次数: |
3606 次 |
| 最近记录: |