minishift start on windows

[onderson]

General information

• Minishift version: minishift-1.26.1-windows-amd64
• OS: Windows
• Hypervisor: VirtualBox

Steps to reproduce

1. Connect to VPN - Cisco Anyconnect - route all traffic configuration, also in corporate network the same situation happens.
2. minishift start as the following

minishift start --http-proxy=http://username:password@ip:port --https-proxy=https://username:password@ip:port --no-proxy=192.168.99.100,localhost,127.0.0.1

password contains "!" char. i replace it with "%21"

HTTP_PROXY and HTTPS_PROXY and NO_PROXY settings are already done properly.
Below minishift start is not properly running.

Expected

-- Checking if https://github.com is reachable ... OK

Actual

-- Checking if https://github.com is reachable ... FAIL

minishift-start.log

[gbraad]

Can you post the whole log? This test can FAIL, but it would not prevent the deployment to start. More information is needed to determine what the problem is...

For instance, does the proxy do re-encryption?

[onderson]

Log is attached in first issue description.

Note: Without proxy and outside of corporate network, it seems ok. it is very hard to enable&disable those kind of settings while flipping between networks.

[onderson]

@gbraad , did you have a chance to look?

[gbraad]

I just returned from a short trip and have focussed on a different problem during that time. I'll examine to logs soon.

…

On Wed, Nov 7, 2018, 16:49 önder sezgin ***@***.*** wrote: @gbraad <https://github.com/gbraad> , did you have a chance to look? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2972 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAHZie9Jzebfqtw120l4DgRpUDlsINKks5usp6ogaJpZM4YM4CL> .

[gbraad]

 Error starting the VM: Error creating the VM. Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.102:2376": dial tcp 192.168.99.102:2376: i/o timeout

This would usually indicate that the IP address changed between runs. You have to make sure the address does not change between runs (or make use of minishift ip --set-static).

[gbraad]

Also, VPN with a route all is known to cause issues when needed to reach the VM from the local machine.

[onderson]

is this #1127

what i need to follow?

[onderson]

I tried --set-static in
both with proxy in corp network and also VPN. i have the same result.

Error: Get https://192.168.99.100:8443/apis/apiregistration.k8s.io/v1beta1/apiservices: dial tcp 192.168.99.100:8443: connect: connection refused

BTW, I can not ping 192.168.99.100

Upgraded virtualbox,
Minishift is latest.

Please suggest a solution or guidance. I read up many issues and tried lots of things and obviously getting nowhere.

@gbraad , @praveenkumar

[gbraad]

I can not ping 192.168.99.100

This is due to the VPN and the route all. You should ask your local admins to allow traffic to 192.168., 172.16, etc. See #1127 (comment)

[onderson]

@gbraad , please accept my ignorance / being novice about the nextworking part of the requirements of minishift.
could you please guide me through the required settings on windows?
i can see an example setting on macos here docker/machine#1500 (comment)

however, not sure how to do something similar either windows or on linux?
I know it is a bit out of scope but it will be helpful for me to have set up minishift in local environment?

[stale]

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.

[onderson]

@gbraad ,even behind proxy and with vpn route all traffic configuration. i can run minishift start successful with openshift v3.11.0. thanks. closing.

[gbraad]

Great to hear! If you have other issues, open a new issue or find us on freenode IRC.

…

On Sat, Jan 26, 2019, 16:13 önder sezgin ***@***.*** wrote: Closed #2972 <#2972>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2972 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAHZhmBBxtaOw7s3XHYhQoBqsCgYF_yks5vHHCBgaJpZM4YM4CL> .