-
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
minikube docker-env doesn't understand powershell core #9183
Comments
Complete guess: Change
to
|
Inherited from docker/machine#4789 and docker/machine#4826 I think you mean |
At the moment, we defer to |
It looks like docker/machine#4826 identifies this issue there, and docker/machine#4827 is set to fix it ... but currently yields a broken build. @afbjorklund you are completely correct. Comment updated. And I see the rest of my comment is redundant to your post too. :D |
We have already forked the code, so will have to fix it (as you outlined, just look for the new name and blame the lack of backwards compatibility on Windows) |
@afbjorklund do we have a plan to pull that code ? |
I didn't see any PR, but it should be straightforward to fix ? Apparently there is another place, in "hyperv.go":
|
I've closed my issue & PR in favor of docker/machine#4788 who solved it first with the exact same fix, and lucked out to not have a broken build. |
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. |
Unstale please. In theory this is a 2-line fix. I definitely don't have enough perspective to criticize, but a few months of inactivity seems a mistake. What's the fastest path to resolution? |
/remove-lifecycle stale let's fix this |
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. |
Unstale please. |
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. |
Unstale please |
Steps to reproduce the issue:
pwsh.exe
)minikube start ...
minikube docker-env
Full output of failed command:
Expected output
Note how passing in
--shell powershell
yielded the correct results, but using the default auto-detect did not detect powershell.Note: running on regular powershell works just fine. This issue only affects powershell core.
The text was updated successfully, but these errors were encountered: