minikube service not working with Docker driver on Windows 10 Pro
#7644
Comments
priyawadhwa
added
kind/bug
|
@ps-feng one of the differnece for docker on windows is, you will have to keep your window open and open the URL in the browser. do you mind trying to keep the terminal open and hit the URL and tell me if u still have the same issue ? |
medyagh
added
co/docker-driver
|
@ps-feng if you verify those hints helped, we could add this to the documentation. |
|
@medyagh thanks for replying. I just tested it and the I've noticed what you've said for Tested both on CMD and PowerShell. |
|
Also, The error says "Error adding route: The object already exists". |
|
@ps-feng thanks for provding more details, could u please provide me the other version and also the full output of the commands by adding this to them
this sounds like a bug ! |
|
@ps-feng it seems like you found a bug ! I believe in this code we were supposed to include windows but missed it |
|
@ps-feng I am gonna make a PR woudl you be willing to try my PR to see if it works for you ? I can provide u the binary file to download |
|
@ps-feng thank you again for finding this bug and actually taking the time to file an issue ! I bet many other ppl faced this issue but you took the time and filed this issue. would you kindly try the binary from this PR to see if that solves the problem ? #7739 |
medyagh
removed
triage/needs-information
|
I was facing this issue as well, and the build 7739 linked above now allows me to access the target url in my host browser. I do however get an error when closing the tunnel via Ctrl+C - I'm unsure if this is related or belongs in a new ticket. CLI output below. CLI output |
|
@medyagh The build you've provided works for me! Both |
thank you very much for verifying, it will be included in minikube v1.10.0 |
@Nickoriuk do you mind retrying it ? and are you running int in a Admin user poweshell or a regular user powershell ? |
medyagh
added
the
priority/important-soon
I was using an admin user powershell. I've tried again and the error is no longer occurring. |
|
this issue was fixed by #7739 |
|
Hey, the binary file doesn't install anything, just open a cmd prompt and exits, did anyone else get the same issue? |
|
Hey, Getting this issue while doing minikube service spring-boot-docker-k8s --url and the url is not accessible. I am using minikube version: v1.25.2
|
|
I got the same issue with me, I am using Minikube version v1.25.2. |
|
Same error following minikube tutorial on windows using
But the alternative works well
|
|
Same issue on my Windows, port-forward suggsted by @santiagortiiz helped, thanks :) |
|
Same issue on my Windows. I'm using minikube v1.23.9. port-forward does not work for access minikube service. |
|
Faced the same issue on windows, but port-forwarding worked for me. Thanks @santiagortiiz! |
Steps to reproduce the issue:
On Windows 10 Pro Version 1909 and Docker v19.03.8, following the Hello-Minikube tutorial
minikube start(using Docker driver)kubectl create deployment hello-node --image=gcr.io/hello-minikube-zero-install/hello-nodekubectl expose deployment hello-node --type=LoadBalancer --port=8080minikube service hello-node --alsologtostderrAnd then the browser opens but tries to connect without success.
Full output of
minikube service hello-node --alsologtostderr:Full output of
minikube startcommand used:Full output of
minikube logscommand:The text was updated successfully, but these errors were encountered: