-
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 creating host:: sudo systemctl -f restart docker: Process exited with status 1 #1952
Comments
Can you verify that the sha256 checksum of the minikube iso at
|
The checksum is correct::
I have tried starting minikube on a clean slate by deleting the Interestingly, if I also get an error when running
This is the result of running
Interestingly, since I am executing the command while the CWD is my desktop folder, this folder gets created: |
I'm getting the same error, the log from
When I ssh into minikube I can't see anything in |
I'm also seeing that weird |
Same problem for me on Windows 10 15063 with virtualbox driver. |
Same problem here on Windows 7 Build 7601 with virtualbox driver. Minikube 0.21.0 also works fine. |
Same here with Windows 8. |
Same issue here |
same issue |
same issue here on Windows 10 with VirtualBox |
same issue with windows7 and latest dockertoolbox+virtualbox (ndis5/ndis6 tested) |
I have the same Issue with Windows 10 and VirtualBox. |
This should be fixed by #1959 |
I had the same issue on Windows 10 with VirtualBox.. |
Same problem here too .. I'm using Hyper-V. |
Same problem using a mac.. |
Similar with mac OSX high sierra.
and then starting minikube results in...
|
Same issue with Windows Version 1709 build 16299 |
Update: I think that is a configuration problem on Windows10 using HyperV, I have my problem solved following this article: |
Check if docker service is running properly. I ran in same issue. Following were the steps followed
|
Steps above seem to have solved for me. I think the root cause was that I had multiple virtual switches and it wasn't picking the right one with external access. |
i used this ,fix it, hope help you, my friend |
I have same issue, restart docker fix it. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Environment:
Minikube version: minikube version: v0.22.1
What happened:
I ran
minikube start
and it produced a series of errors:I then ran
minikube delete
andminikube start
again:What you expected to happen:
Minikube should start a kubernetes cluster correctly
How to reproduce it (as minimally and precisely as possible):
Run
minikube start
.Output of
minikube logs
(if applicable):Anything else do we need to know:
The text was updated successfully, but these errors were encountered: