Minishift wont start on windows #2910
Comments
|
i just download minishift-1.18.0-windows-amd64 i have deploy a node.js app (the default app )with success and even deployed a spring boot app. Here is the log from gitbash and here is the log for spring boot app here is the build from minishift Everything works just fine.Or i think so I have to stop minishift shut down and restart to see if everything will work again as i have it now. |
|
I have stop and restart minishift |
|
@giorgoch The only difference here is |
|
@praveenkumar |
Not sure what you mean with 'giving the wrong ip'. IP addresses are handed out by the local DHCP service. What did you try to change in the but in short, if you have issues with the IP address changing, you probably ran into a certificate issue... and if so, it is best to delete the VM first. |
|
@Graab Hi graab what i mean is giving ip 192.168.99.101 and for this ip works fine. But if i stop the VM and restart then minishift has 192.168.99.100. Then i get this certificate error.I would look more to see if i can find other way to by pass ip error. |
|
Hi, I'm facing similar issues.. I'm using Windows 7 Professional with VirtualBox 5.2.20. Here's the minishift version: Here's the log when running I check the IP and port mentioned in the log. Telnet the port 8443, failed. Also tried telnet port 22, it succeed. I tried to create a specific outbound rule on my Windows Firewall for port 8443, but still cant telnet to the port. So, I tried to ssh into the VM: Regards, |
|
I have found a solution regarding minishift. I have downgrade to version minishift-1.15.1-windows-amd64 and 3.7.2 with Virtual box 5.2.6. Everything works fine stop restarting deploy etc ... |
|
@giorgoch as mentioned: |
|
@yayan19 how much memory did you assign to use for this instance? |
|
@gbraad I allocated 4GB memory. I just tried again with 8GB, but still got the same issue. |
|
@LalatenduMohanty See the previous error... This has been seen several times now. |
|
@gbraad I saw following error on Fedora 28 which is different than this issue I think. |
@gbraad The issue I seen is a known issue in |
|
@yayan19 have you been able to use v3.9 ? |
|
@gbraad yes, just tried OKD v3.9.0 using minishift v1.25.0 and it run successfully. Here's the config. And here's the log.. Also tried using the latest minishift v1.26.1 with both OKD v3.11.0 and v3.10.0, but still having the same issue. |
|
@praveenkumar @LalatenduMohanty deployment of v3.10 and v3.11 are not stable for some people. I have seen the same... |
|
@gbraad @yayan19 what about caching all the required images before hand and then using it instead depend on internet bandwidth at beginning. $ export MINISHIFT_ENABLE_EXPERIMENTAL=y
$ ./minishift start --no-provision
$ ./minishift image export docker.io/openshift/origin-cli:v3.11.0 \
docker.io/openshift/origin-control-plane:v3.11.0 \
docker.io/openshift/origin-deployer:v3.11.0 \
docker.io/openshift/origin-docker-registry:v3.11.0 \
docker.io/openshift/origin-haproxy-router:v3.11.0 \
docker.io/openshift/origin-hyperkube:v3.11.0 \
docker.io/openshift/origin-hypershift:v3.11.0 \
docker.io/openshift/origin-node:v3.11.0 \
docker.io/openshift/origin-pod:v3.11.0 \
docker.io/openshift/origin-service-serving-cert-signer:v3.11 \
docker.io/openshift/origin-web-console:v3.11.0
$ ./minishift delete
$ ./minishift image list
docker.io/openshift/origin-cli:v3.11.0
docker.io/openshift/origin-control-plane:v3.11.0
docker.io/openshift/origin-deployer:v3.11.0
docker.io/openshift/origin-docker-registry:v3.11.0
docker.io/openshift/origin-haproxy-router:v3.11.0
docker.io/openshift/origin-hyperkube:v3.11.0
docker.io/openshift/origin-hypershift:v3.11.0
docker.io/openshift/origin-node:v3.11.0
docker.io/openshift/origin-pod:v3.11.0
docker.io/openshift/origin-service-serving-cert-signer:v3.11
docker.io/openshift/origin-web-console:v3.11.0
$./minishift start |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
1 similar comment
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Probably related to openshift/origin#22194. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
General information
I have download the latest version and try to install. I am running minishift on Windows 7 from gitbash and with the minishift start --vm-driver=virtualbox command. After i install it the first time i run minishift start.
I have install and uninstall minishift many times
It run's on VM but not showing the web console at all.
Once i was even able to deploy a rubi application and a node.js but the most times is failing.
what can i do to fix this what have i done wrong?This must be easy to use . I have spend many hours but with no luck.
thanks
Steps to reproduce
Expected
To have a minishift running on web console to be able to deploy an application
Actual
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
if by accident minishift starts then i cannot deploy.
Logs
and here
You can start Minishift with
minishift start --show-libmachine-logs -v5to collect logs.Please consider posting this on http://gist.github.com/ and post the link in the issue.
The text was updated successfully, but these errors were encountered: