5
  • Windows 10
  • CDK v3.9 / Minishift 1.34
  • VirtualBox v5.2.32 (also tried v6.0.10)

I'm trying to start minishift/cdk but keep getting an error. After reading many other reports with a similar error it's not clear what the solution might be.

  • I'm not on a slow computer or slow network connection
  • I've tried disabling the firewall. Doesn't help but I don't think that's the problem since the server partially starts and I can do a minishift ssh into the server
  • I've tried using a command prompt with admin rights I'm new to Minishift so am unsure where to look next.
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
Bill
  • 85
  • 1
  • 8

2 Answers2

3

You can probably report this issue also here or you can add a comment under already existing issue.

Besides that, you can try to start over with:

  1. minishift delete
  2. delete ~/.minishift folder
  3. delete ~/.kube folder
  4. Verify that you have no leftover VMs up in virtual box manager, just in case
  5. and finally minishift start

But be aware that this will purge any actual configuration and apps you were using on minishift/local openshift, see more reference. Unfortunately there is no better workaround than trying to start again AFAIK.

Ondrej Dockal
  • 118
  • 4
  • Thanks. I've deleted those folders so many times I can't even count. I'll keep at it and will try posting to github. – Bill Aug 14 '19 at 19:49
  • 1
    Try to run `minishift start` with `--show-libmachine-logs --v 5` flags. This will show more detailed log. Also, maybe giving underlying VM more resources could help `minishift start --memory XGB --cpus Y` where, by default, X is 4 and Y is 2. Depends on how many resources you can spare. – Ondrej Dockal Aug 16 '19 at 08:22
  • It worked but not sure what I did differently. I had been trying various combinations of memory and cpus. Decided to try setting the logging as mentioned above and it started this time. – Bill Aug 19 '19 at 22:11
  • @Bill I'm facing the same problem, and these steps did not helped me after deleting/starting minishift – lpkej Oct 08 '19 at 07:36
  • 1
    Minishift seems awfully finicky. It starts now most of the time, but sometimes fails and I have to retry a number of times before it works. It's not clear what's going on with it. One thing I'd be sure to do is run the minishift command from an administrator command prompt if you're using a Windows host. – Bill Oct 13 '19 at 21:27
1

I just face this issue too and its seems to be with credentials. what i did was, as user Ondrej Dockal says,

  1. stop vm's minishift stop
  2. delete vm's with minishift delete
  3. using a priviledged cmd run minishift with valid credentials: minishift --username {RH-USERNAME} --password {RH-PASSWORD} start.

For me that was enough. Let me know if this was usefull to you.

Marcelo Hualoto
  • 23
  • 4