-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.13.0 tunnel on Windows: not listening at port #9189
Comments
I wonder if this has to do with the native ssh change in v1.13. Are you able to replicate this, @sharifelgamal ? |
@tstromberg I just tried version 1.12.3 and had the same problem. |
Interestingly, if I invoke |
Same issue( and no solution |
I've tried running powershell as administrator. Open SSH was installed. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
I'm sorry. I'm not set up to test this at the moment. I would need to disable hardware virtualization in Windows and so on and I haven't worked with Docker for months. Is someone else able to confirm this is fixed? |
@cowwoc No worries, thanks for responding. I'm going to close this issue since I'm pretty sure this is resolved, but if someone comments saying otherwise I'll be happy to reopen this issue. |
Steps to reproduce the issue:
minikube start --driver=docker
returns:2.
kubectl create deployment hello-minikube --image=k8s.gcr.io/echoserver:1.10
returns:
returns:
minikube service hello-minikube --url --alsologtostderr
returns:
netstat -an
and sure enough no process is listening on that portOptional: Full output of
minikube logs
command:The text was updated successfully, but these errors were encountered: