minikube windows, failing registry test inside the container

[SirRedan]

What Happened?

When starting a new cluster i notice that it always fails to connect to the registry from inside the minikube container.

using minikube start --alsologtostderr -v=7 i notice that it reports being unable to connect to the registry

W0115 16:42:44.610131 26748 start.go:867] [curl.exe -sS -m 2 https://registry.k8s.io/] failed: curl.exe -sS -m 2 https://registry.k8s.io/: Process exited with status 127
stdout:

stderr:
bash: line 1: curl.exe: command not found

from what i've managed to dig up it seems that because i'm running on windows the runtime.GOOS == "windows" is true. making the curl command become curl.exe

this happens in minikube/pkg/minikube/node/start.go line 862

but it also tries to perform curl.exe inside the container, which is the default minikube image. this image has "curl" but not "curl.exe"

unless "curl.exe" is somehow supposed to be inherited from outside the container this will always fail inside the container.

My theory on how to fix this would be to add logic to determine the environment of the container before trying to run curl.

Attach the log file

log.txt

Operating System

Windows

Driver

Docker

[shashikumaarb]

+1 I have the same problem.