-
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
Error during first start: bash: -c: line 0: unexpected EOF while looking for matching `'' bash: -c: line 1: syntax error: unexpected end of file #1194
Comments
@Grovespaz Could you try running the command with an elevated Powershell? Trying to isolate if the issue has to do with the shell used. |
Running the command in Powershell after removing the VM from HyperV and removing ~/.minikube yields the same result. Just in case, here's the complete output:
|
Can you try running this with libmachine logging enabled |
I apologize for the late reply. Thanks for the guidance! The VM was indeed connected to the DockerNat switch but solving this didn't solve the original error. After going through the verbose log, I noticed a call to a stray file called ssh.bat helpfully left in my path by the chromium build tools :) After removing this from my path, minikube worked as expected. Thank you for your time and apologies for the noise. |
@Grovespaz we already accepted a PR to only use the native golang ssh method. This will be in the next version of minikube |
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report
Minikube version (use
minikube version
): v0.16.0Environment:
cat ~/.minikube/machines/minikube/config.json | grep DriverName
): hypervcat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
): minikube-v1.0.6.isoWhat happened:
When running
minikube start
for the first time (minikube start --vm-driver=hyperv
to be accurate), the terminal fills up with this message repeated multiple times:Repeating the command yields the same result.
Running
minikube status
results in:What you expected to happen:
minikube start not to fail
How to reproduce it (as minimally and precisely as possible):
Run
minikube start --vm-driver=hyperv
from an elevated command prompt on a Windows 10 machine.The text was updated successfully, but these errors were encountered: