Skip to content
This repository has been archived by the owner on Jun 11, 2021. It is now read-only.

Kitematic Refuse to start after update docker in Windows 10 #4175

Open
sumpokemonster opened this issue Oct 14, 2018 · 3 comments
Open

Kitematic Refuse to start after update docker in Windows 10 #4175

sumpokemonster opened this issue Oct 14, 2018 · 3 comments

Comments

@sumpokemonster
Copy link

sumpokemonster commented Oct 14, 2018

Expected behavior

Kitematic should start properly

Actual behavior

Kitematic setup always stopps at ~10% and generates error messages below:

Command failed: C:\Program Files\Docker Toolbox\docker-machine.exe -D create -d virtualbox --virtualbox-memory 2048 default,Docker Machine Version: 0.14.0, build 89b8332,Found binary path at C:\Program Files\Docker Toolbox\docker-machine.exe,Launching plugin server for driver virtualbox,Plugin server listening at address 127.0.0.1:50400,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(flag-lookup) Calling .GetMachineName,(flag-lookup) Calling .DriverName,(flag-lookup) Calling .GetCreateFlags,Found binary path at C:\Program Files\Docker Toolbox\docker-machine.exe,Launching plugin server for driver virtualbox,Plugin server listening at address 127.0.0.1:50404,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(default) Calling .GetMachineName,(default) Calling .DriverName,(default) Calling .GetCreateFlags,(default) Calling .SetConfigFromFlags,Reading certificate data from C:\Users\hongb.docker\machine\certs\ca.pem,Decoding PEM data...,Parsing certificate...,Reading certificate data from C:\Users\hongb.docker\machine\certs\cert.pem,Decoding PEM data...,Parsing certificate...,(default) Calling .PreCreateCheck,(default) DBG | COMMAND: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe --version,(default) DBG | STDOUT:,(default) DBG | {,(default) DBG | 5.2.8r121009,(default) DBG | },(default) DBG | STDERR:,(default) DBG | {,(default) DBG | },(default) DBG | COMMAND: wmic computersystem get hypervisorpresent,(default) DBG | STDOUT:,(default) DBG | {,(default) DBG | HypervisorPresent ,(default) DBG | TRUE ,(default) DBG | ,(default) DBG | },Error with pre-create check: "This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)",open C:\Users\hongb.docker\machine\machines\default\default\Logs\VBox.log: The system cannot find the path specified.,notifying bugsnag: [Error with pre-create check: "This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)"],

Information about the Issue

Docker has been reminding me to update to the latest version since this July (or even earlier) but I refused to. And Docker and Kitematic could run perfectly. But this changed completely after I accidentally clicked 'install' buton today. I looked for possible reasons and solutions online and tried to disable Hyper-V while reinstalling Docker and then either enable or disable Hyper-V while starting Docker. But Kitematic still refuse to properly start...

Did any one experience the same issue after updating Docker?

@sumpokemonster sumpokemonster changed the title Kitematic Generates refuse to start after update docker in Windows 10 Kitematic Refuse to start after update docker in Windows 10 Oct 14, 2018
@mithuns
Copy link

mithuns commented Nov 9, 2018

I faced the same issue and I disabled the Hyper-V hypervisor and rebooted.

image

Now docker wont start because docker needs it.
image

So, what I understand is, Hyper-V is essential for Docker on windows, either the message coming from Kitematic should be updated to not suggest disabling Hyper-V Hypervisor or include help on how to use Hyper-V as a driver ?

@ThomasCollignon
Copy link

Could you try the solution written in this post ?

You only need to delete Kitematic folder in %APPDATA% (C:\Users{User}\AppData\Roaming) and run Kitematic again.

@imadamtoo
Copy link

Could you try the solution written in this post ?

You only need to delete Kitematic folder in %APPDATA% (C:\Users{User}\AppData\Roaming) and run Kitematic again.

Hey Thomas, that worked like a charm! Thank you. I had the exact issue as the author of this post and this solved my problem.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants