-
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
tunnel on windows: "sudo": executable file not found in %PATH% #9078
Comments
Hey @smacdav thanks for opening this issue. I"m just curious, does this work if you don't enable contour? I'd also suggest upgrading to the latest version of minikube, v1.13.0. |
It does work if I don't enable contour. Interesting. Not useful to me, but interesting. I went ahead and upgraded the system I was doing this on to v1.13.0. I have another system, however, on which v1.13.0 doesn't seem to work: it fails to connect to the controller-manager and scheduler, so they fail their health-checks. I rolled that system back to 1.12.2. It would be nice to be able to upgrade, though. |
The problem I had with 1.13.0 appears to only be an issue if I start "fresh" and therefore run kubernetes v1.19.0. Then I get
If I run an existing kubernetes v1.18.3 image then it runs just fine. I should probably file a separate ticket for that, huh? |
Same issue on v1.13.0 Running on Windows using gitbash.
|
Yeah, I'd say we really screwed this up for Windows users when we added this forwarding feature. "sudo" isn't necessary there for binding to ports <1024. |
I suspected #6833 at first - but that was merged already back in February. |
hi, any solution for this error? ssh_tunnel.go:113] error starting ssh tunnel: exec: "sudo": executable file not found in %PATH% |
I will pick this up. /assign |
I am facing the same issue on windows. with WSL 2. ssh_tunnel.go:113] error starting ssh tunnel: exec: "sudo": executable file not found in %PATH% hi, any solution for this error yet? |
I am also looking for a solution. Please suggest if there is any solution. |
I am still working on this :)
…On Tue 3 Nov, 2020, 11:14 PM anuanju89, ***@***.***> wrote:
I am also looking for a solution. Please suggest if there is any solution.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#9078 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVJQI5UYS32H733ZXEHA2LSOA6O5ANCNFSM4QKZJO2A>
.
|
Same issue here. Painful flaw as it makes minikube useless on a Windows machine. |
The same problem, any solution? |
Not from me. I use my own AKS cluster and not minikube, docker compose and docker desktop (has also k8) might be other options? |
It was v1.16.0... But this problem is still not be solved. 💢 |
in gitbash its work for me and access |
Steps to reproduce the issue:
minikube start --driver=docker
kubectl apply -f https://projectcontour.io/quickstart/contour.yaml
minikube tunnel
Get the following output:
Full output of failed command:
Full output of
minikube start
command used, if not already included:Optional: Full output of
minikube logs
command:The text was updated successfully, but these errors were encountered: