minikube service` not working with Docker driver on Windows 10 Pro 10.0.19041 -Build 19041

[AmitVishwash]

I started minikube service on windows 10 pro build 19041.

Please find the attached screenshots

1. The resource are not accessible at 172.17.0.3:30001. i;e NodeAddress:Nodeport mentioned in service.yaml file
2. Neither the resource is available at http://127.0.0.1:50367 which I have found after running

.\minikube-windows-amd64.exe service selenium-srv

• Starting tunnel for service selenium-srv.
  |-----------|--------------|-------------|------------------------|
  | NAMESPACE | NAME | TARGET PORT | URL |
  |-----------|--------------|-------------|------------------------|
  | default | selenium-srv | | http://127.0.0.1:50367 |
  |-----------|--------------|-------------|------------------------|

[AmitVishwash]

@medyagh please have a look on this. FYI @tstromberg

[AmitVishwash]

@tstromberg any findings?

[sharifelgamal]

So what happens when you try to ping the URL? It just hangs?

[AmitVishwash]

@sharifelgamal i will not say it hangs. It says the site cant be reached when i ping the node url with the the port exposed in the browser. However when i try .\minikube-windows-amd64.exe service selenium-srv it opens a browser with the url but that also says the site cant be reached.

[medyagh]

@AmitVishwash

The resource are not accessible at 172.17.0.3:30001. i;e NodeAddress:Nodeport mentioned in service.yaml file
Neither the resource is available at http://127.0.0.1:50367 which I have found after running

the 172 ip is internal to docker and not accessible from outside.
but you should have access to http://127.0.0.1:50367

can you try in browser with CURL and also make sure your browser is not changing http to https ?

and also there might be proxy or VPN that is preventing you from accessing, are you using a corp network or a proxy?

[AmitVishwash]

@medyagh I tried this also but didn't able to access it. I tried the url after running
.\minikube-windows-amd64.exe service selenium-srv

Starting tunnel for service selenium-srv.
|-----------|--------------|-------------|------------------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|-----------|--------------|-------------|------------------------|
| default | selenium-srv | | http://127.0.0.1:50367 |
|-----------|--------------|-------------|------------------------|
But http://127.0.0.1:50367 is not accessible and I am not using any vpn or proxy. I connected to personal wifi.

Is there any specific command pertaining to curl, i will try this also. Could you please provide me the exact command?
This was happening on Windows 10 Pro Edition when I checked.

[medyagh]

@AmitVishwash when you start the service command, you would need to keep it open in the termianl and open it in another terminal.

could you confirm that if if you keep the terminal open, and then try to open it in another terminal it works?

[AmitVishwash]

@medyagh I am keeping the terminal open only and then trying to access the URL. But the url is not accessible.

[viswanathareddy04]

@AmitVishwash Amit any luck onthis? even I'm facing same issue.

[rconrardy]

@AmitVishwash I am facing the same issue, has there been any progress on a solution?

[sharifelgamal]

We definitely need someone to take a deeper look at the service command on windows. Help wanted!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[sharifelgamal]

This is likely still an issue, freezing to avoid it getting closed.

[dddmityaMD]

here are the workarounds
for service of type nodePort assigned to internal port of 8080 the command will be
kubectl port-forward service/service_name 30000:8080
for service of type loadBalancer the command will be
minikube tunnel

Please see https://minikube.sigs.k8s.io/docs/start/ -> 4Deploy applications for more information

[dellraja]

here are the workarounds for service of type nodePort assigned to internal port of 8080 the command will be kubectl port-forward service/service_name 30000:8080 for service of type loadBalancer the command will be minikube tunnel

Please see https://minikube.sigs.k8s.io/docs/start/ -> 4Deploy applications for more information

WORKED

[kavaldeep]

here are the workarounds for service of type nodePort assigned to internal port of 8080 the command will be kubectl port-forward service/service_name 30000:8080 for service of type loadBalancer the command will be minikube tunnel

Please see https://minikube.sigs.k8s.io/docs/start/ -> 4Deploy applications for more information

thanks you very much. It worked

[campbellja]

here are the workarounds for service of type nodePort assigned to internal port of 8080 the command will be kubectl port-forward service/service_name 30000:8080 for service of type loadBalancer the command will be minikube tunnel

Please see https://minikube.sigs.k8s.io/docs/start/ -> 4Deploy applications for more information

@dddmityaMD Thank you very much, you are a genuine legend! Not all heros wear capes!

[Carewj00]

This issue persists - you can get to the local host 127.0.0.1 address as the browser opens automatically...the public IP is not working seems some issue in the cluster... and you need to keep the terminal open to start the service, pretty annoying....

C:\home\kuber>minikube service mongo-express-service
|-----------|-----------------------|-------------|---------------------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|-----------|-----------------------|-------------|---------------------------|
| default | mongo-express-service | 8081 | http://192.168.49.2:30006 |
|-----------|-----------------------|-------------|---------------------------|

• Starting tunnel for service mongo-express-service.
  |-----------|-----------------------|-------------|------------------------|
  | NAMESPACE | NAME | TARGET PORT | URL |
  |-----------|-----------------------|-------------|------------------------|
  | default | mongo-express-service | | http://127.0.0.1:59581 |
  |-----------|-----------------------|-------------|------------------------|
• Opening service default/mongo-express-service in default browser...
  ! Because you are using a Docker driver on windows, the terminal needs to be open to run it.