Windows 10 Support #77

Closed
dave-tucker opened this Issue Aug 13, 2015 · 63 comments

Comments

Projects
None yet
@dave-tucker
Member

dave-tucker commented Aug 13, 2015

Download a test version of the Toolbox for Windows 10 here.

Currently, the latest stable version of VirtualBox that is shipped in the toolbox does not support Windows 10.

A user trying to use Toolbox on Windows 10 will be able to install the package succesfully, but the VM will not be able to be created because of the following issue: virtualbox#14040

This appears to be fixed in the latest test build 5.0.1r102010

Suggestions:

  • Disable installation of Toolbox on Windows 10 for now
  • Release an experimental version of toolbox that packages the latest test build of virtualbox
  • Remove any installation restrictions when a stable version of VirtualBox ships that supports Windows 10
@dave-tucker

This comment has been minimized.

Show comment
Hide comment
@dave-tucker

dave-tucker Aug 13, 2015

Member

As an FYI, anybody who has installed this on Win 10 and wants to fix their installation manually can follow these steps:

  1. Download and install the latest test build of Virtualbox here
  2. Open a Command Prompt and docker-machine rm default
  3. Open Kitematic and let it create a new VM
  4. Test that it's working - I deployed a Jenkins container and it seems to be ok!
Member

dave-tucker commented Aug 13, 2015

As an FYI, anybody who has installed this on Win 10 and wants to fix their installation manually can follow these steps:

  1. Download and install the latest test build of Virtualbox here
  2. Open a Command Prompt and docker-machine rm default
  3. Open Kitematic and let it create a new VM
  4. Test that it's working - I deployed a Jenkins container and it seems to be ok!

@jmorganca jmorganca added feature bug and removed feature labels Aug 13, 2015

@jmorganca jmorganca changed the title from Feature: Windows 10 Support to Windows 10 Support Aug 13, 2015

@lexxpavlov

This comment has been minimized.

Show comment
Hide comment
@lexxpavlov

lexxpavlov Aug 13, 2015

I have win10. I installed latest Virtualbox (5.0.1r102010), then try to run Kitematic. Kitematic first removes this my Virtualbox and installs 5.0.0r101573 instead. If I setup Virtualbox via Kitematic, then I have several troubles with it. I can't run Kitematic with new Virtualbox (r102010) without reinstall to previous Virtualbox.

I have win10. I installed latest Virtualbox (5.0.1r102010), then try to run Kitematic. Kitematic first removes this my Virtualbox and installs 5.0.0r101573 instead. If I setup Virtualbox via Kitematic, then I have several troubles with it. I can't run Kitematic with new Virtualbox (r102010) without reinstall to previous Virtualbox.

@jmorganca

This comment has been minimized.

Show comment
Hide comment
@jmorganca

jmorganca Aug 14, 2015

Member

@lexxpavlov thanks for the note, looks like there may be a bug in how KM checks VBox versions.

Member

jmorganca commented Aug 14, 2015

@lexxpavlov thanks for the note, looks like there may be a bug in how KM checks VBox versions.

@StefanScherer

This comment has been minimized.

Show comment
Hide comment
@StefanScherer

StefanScherer Aug 14, 2015

@jeffdm VirtualBox 5.0.2 is available. I've just seen a new Chocolatey package.

@jeffdm VirtualBox 5.0.2 is available. I've just seen a new Chocolatey package.

@lexxpavlov

This comment has been minimized.

Show comment
Hide comment
@lexxpavlov

lexxpavlov Aug 14, 2015

@StefanScherer I insalled VirtualBox 5.0.2 (not test build), but Kitematic don't want use it.
I created a issue in Kitematic repo (docker/kitematic#932).

@StefanScherer I insalled VirtualBox 5.0.2 (not test build), but Kitematic don't want use it.
I created a issue in Kitematic repo (docker/kitematic#932).

@iprastha

This comment has been minimized.

Show comment
Hide comment
@iprastha

iprastha Aug 14, 2015

Just confirmed this on Windows 10, successfully run my container using dave's comment.
However in my case, using "docker-machine rm default" was not successful (seems like stuck forever), so I fired up virtualbox user interface and removed the default VM from there, then run kinematic which created a working VM.

Just confirmed this on Windows 10, successfully run my container using dave's comment.
However in my case, using "docker-machine rm default" was not successful (seems like stuck forever), so I fired up virtualbox user interface and removed the default VM from there, then run kinematic which created a working VM.

@Grafikart

This comment has been minimized.

Show comment
Hide comment
@Grafikart

Grafikart Aug 14, 2015

I think the warning shouldn't prevent the installation, if we want to install only docker-machine to work with Hyper-V on Windows 10.

I think the warning shouldn't prevent the installation, if we want to install only docker-machine to work with Hyper-V on Windows 10.

@mysticmind

This comment has been minimized.

Show comment
Hide comment
@mysticmind

mysticmind Aug 14, 2015

Docker team have released a Windows 10 test version which already uses Virtualbox (5.0.1r102010). If you are installing fresh, you could directly download and use this version.

Everything works fine using the above installer except for Kitematic which on launch messes up the host VM if you have created one using the commandline. I would suggest not to use Kitematic for the time being.

Note that I haven't tried creating the host VM via Kitematic as a first step, given the comments from others, I guess it would work.

Docker team have released a Windows 10 test version which already uses Virtualbox (5.0.1r102010). If you are installing fresh, you could directly download and use this version.

Everything works fine using the above installer except for Kitematic which on launch messes up the host VM if you have created one using the commandline. I would suggest not to use Kitematic for the time being.

Note that I haven't tried creating the host VM via Kitematic as a first step, given the comments from others, I guess it would work.

@lexxpavlov

This comment has been minimized.

Show comment
Hide comment
@lexxpavlov

lexxpavlov Aug 14, 2015

@mysticmind This version was released yesterday, I tried it. It version has VirtualBox 5.0.0r101573, as I said above.

@mysticmind This version was released yesterday, I tried it. It version has VirtualBox 5.0.0r101573, as I said above.

@dgmdevelopment

This comment has been minimized.

Show comment
Hide comment
@dgmdevelopment

dgmdevelopment Aug 15, 2015

I have the Win 10 test version working great. if you have any version of the toolbox installed prior to the 1.8.1a - uninstall it first. Then install VBox 5.0.1r102010. Remove the old default vm if present. I already had Mysys-git on the machine. Install the Win 10 test version, uncheck Vbox and Mysys-git naturally because already installed. Both the Quickstart and Kitematic fire up. Hope that works for you too!

I have the Win 10 test version working great. if you have any version of the toolbox installed prior to the 1.8.1a - uninstall it first. Then install VBox 5.0.1r102010. Remove the old default vm if present. I already had Mysys-git on the machine. Install the Win 10 test version, uncheck Vbox and Mysys-git naturally because already installed. Both the Quickstart and Kitematic fire up. Hope that works for you too!

@luisrudge

This comment has been minimized.

Show comment
Hide comment
@luisrudge

luisrudge Aug 17, 2015

I'm having this error on a windows 10 box:

image

image

I'm having this error on a windows 10 box:

image

image

@luisrudge

This comment has been minimized.

Show comment
Hide comment
@luisrudge

luisrudge Aug 17, 2015

With the 1.8.1b release, it gets stuck here:

image

image

With the 1.8.1b release, it gets stuck here:

image

image

@luisrudge

This comment has been minimized.

Show comment
Hide comment
@luisrudge

luisrudge Aug 17, 2015

If I recreate the VM, I get the same result as #77 (comment)

If I recreate the VM, I get the same result as #77 (comment)

@luisrudge

This comment has been minimized.

Show comment
Hide comment
@luisrudge

luisrudge Aug 17, 2015

So, I just formatted my pc. Installed Windows 10 from scratch and docker toolbox 1.8.1b. Everything works as expected! I'm not sure what was causing the issue, but I can confirm this release works on win10.

So, I just formatted my pc. Installed Windows 10 from scratch and docker toolbox 1.8.1b. Everything works as expected! I'm not sure what was causing the issue, but I can confirm this release works on win10.

@luisrudge

This comment has been minimized.

Show comment
Hide comment
@luisrudge

luisrudge Aug 17, 2015

Sadly, it stops working after I install visual studio :(

Sadly, it stops working after I install visual studio :(

@luisrudge

This comment has been minimized.

Show comment
Hide comment
@luisrudge

luisrudge Aug 17, 2015

Sorry to comment again. I removed the virtualbox machine and opened kitematic again and it's working again :)

Sorry to comment again. I removed the virtualbox machine and opened kitematic again and it's working again :)

@bpuglisi

This comment has been minimized.

Show comment
Hide comment
@bpuglisi

bpuglisi Aug 19, 2015

Wanted to share my solution that worked when all other Windows 10 ones out there weren't. Docker Toolbox + Docker Compose - Enjoy!

http://brianpuglisi.com/how-to-get-docker-compose-working-on-windows-10/

Wanted to share my solution that worked when all other Windows 10 ones out there weren't. Docker Toolbox + Docker Compose - Enjoy!

http://brianpuglisi.com/how-to-get-docker-compose-working-on-windows-10/

@StefanScherer

This comment has been minimized.

Show comment
Hide comment
@StefanScherer

StefanScherer Aug 19, 2015

@bpuglisi Thanks for sharing! So is it possible to build a docker-compose.exe with pyInstaller with your setup?

@bpuglisi Thanks for sharing! So is it possible to build a docker-compose.exe with pyInstaller with your setup?

@FrenchBen FrenchBen referenced this issue in docker/kitematic Aug 19, 2015

Closed

Cannot use latest VirtualBox #932

@jmorganca

This comment has been minimized.

Show comment
Hide comment
@jmorganca

jmorganca Aug 24, 2015

Member

Closing for now since there's a version of VirtualBox that works with Windows 10

Member

jmorganca commented Aug 24, 2015

Closing for now since there's a version of VirtualBox that works with Windows 10

@jmorganca jmorganca closed this Aug 24, 2015

@gbisheimer

This comment has been minimized.

Show comment
Hide comment
@gbisheimer

gbisheimer Aug 27, 2015

Hi. I'm still having problems creating host-only interface using DockerToolbox-1.8.1b running on Windows 10.0.10240. I also tried using VirtualBox testbuild 5.0.3-102322 without luck. I followed every troubleshooting guide I found on the internet and couldn't make it work.

Neither it works creating the interface directly from VirtualBox interface. The interface actually gets created on Windows, but VirtualBox is not aware of that, as it isn't listed on the host-only interface list.

I also have VMWare installed on the same machine. There are any known incompatibilities with this software?

Any help will be appreciated!!

Here is the console transcript after executing Docker Quickstart Terminal:

STDERR:
Creating VirtualBox VM...
Creating SSH key...
Creating disk image...
Creating 20000 MB hard disk image...
Converting from raw image file="stdin" to file="C:\Users\gbisheimer\.docker\machine\machines\default\disk.vmdk"...
Creating dynamic image with size 20971520000 bytes (20000MB)...
executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe createvm --basefolder C:\Users\gbisheimer\.docker\machine\machines\default --name default --register
STDOUT: Virtual machine 'default' is created and registered.
UUID: e8838696-b567-4f58-9ba8-85a7705db7cc
Settings file: 'C:\Users\gbisheimer\.docker\machine\machines\default\default\default.vbox'

STDERR:
VM CPUS: 1
VM Memory: 2048
executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe modifyvm default --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --ostype Linux26_64 --cpus 1 --memory 2048 --acpi on --ioapic on --rtcuseutc on --natdnshostresolver1 off --natdnsproxy1 off --cpuhotplug off --pae on --hpet on --hwvirtex on --nestedpaging on --largepages on --vtxvpid on --accelerate3d off --boot1 dvd
STDOUT:
STDERR:
executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe modifyvm default --nic1 nat --nictype1 82540EM --cableconnected1 on
STDOUT:
STDERR:
using 192.168.99.1 for dhcp address
executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe list hostonlyifs
STDOUT:
STDERR:
executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe hostonlyif create
STDOUT:
STDERR: 0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 71 of file VBoxManageHostonly.cpp

Error creating machine: exit status 1
You will want to check the provider to make sure the machine and associated resources were properly removed.
Looks like something went wrong... Press any key to continue...

Hi. I'm still having problems creating host-only interface using DockerToolbox-1.8.1b running on Windows 10.0.10240. I also tried using VirtualBox testbuild 5.0.3-102322 without luck. I followed every troubleshooting guide I found on the internet and couldn't make it work.

Neither it works creating the interface directly from VirtualBox interface. The interface actually gets created on Windows, but VirtualBox is not aware of that, as it isn't listed on the host-only interface list.

I also have VMWare installed on the same machine. There are any known incompatibilities with this software?

Any help will be appreciated!!

Here is the console transcript after executing Docker Quickstart Terminal:

STDERR:
Creating VirtualBox VM...
Creating SSH key...
Creating disk image...
Creating 20000 MB hard disk image...
Converting from raw image file="stdin" to file="C:\Users\gbisheimer\.docker\machine\machines\default\disk.vmdk"...
Creating dynamic image with size 20971520000 bytes (20000MB)...
executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe createvm --basefolder C:\Users\gbisheimer\.docker\machine\machines\default --name default --register
STDOUT: Virtual machine 'default' is created and registered.
UUID: e8838696-b567-4f58-9ba8-85a7705db7cc
Settings file: 'C:\Users\gbisheimer\.docker\machine\machines\default\default\default.vbox'

STDERR:
VM CPUS: 1
VM Memory: 2048
executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe modifyvm default --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --ostype Linux26_64 --cpus 1 --memory 2048 --acpi on --ioapic on --rtcuseutc on --natdnshostresolver1 off --natdnsproxy1 off --cpuhotplug off --pae on --hpet on --hwvirtex on --nestedpaging on --largepages on --vtxvpid on --accelerate3d off --boot1 dvd
STDOUT:
STDERR:
executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe modifyvm default --nic1 nat --nictype1 82540EM --cableconnected1 on
STDOUT:
STDERR:
using 192.168.99.1 for dhcp address
executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe list hostonlyifs
STDOUT:
STDERR:
executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe hostonlyif create
STDOUT:
STDERR: 0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 71 of file VBoxManageHostonly.cpp

Error creating machine: exit status 1
You will want to check the provider to make sure the machine and associated resources were properly removed.
Looks like something went wrong... Press any key to continue...
@raghunandy

This comment has been minimized.

Show comment
Hide comment
@raghunandy

raghunandy Sep 2, 2015

After many trial and errors I am able to run Docker (Docker Toolbox , Kitamatic ) in Windows 10.

Solution:
VirtualBox-4.3.30-101610-Win.exe

Remove your old virtualbox and install the above version.

thank you

After many trial and errors I am able to run Docker (Docker Toolbox , Kitamatic ) in Windows 10.

Solution:
VirtualBox-4.3.30-101610-Win.exe

Remove your old virtualbox and install the above version.

thank you

@wiradikusuma

This comment has been minimized.

Show comment
Hide comment
@wiradikusuma

wiradikusuma Sep 5, 2015

I installed VirtualBox-5.0.3-102467-Win.exe and DockerToolbox-1.8.1c.exe (deselecting Virtual Box). It doesn't work.

Creating Machine default...
Creating VirtualBox VM...
Creating SSH key...
Starting VirtualBox VM...
Starting VM... <-- stays there forever

Anyone?

I installed VirtualBox-5.0.3-102467-Win.exe and DockerToolbox-1.8.1c.exe (deselecting Virtual Box). It doesn't work.

Creating Machine default...
Creating VirtualBox VM...
Creating SSH key...
Starting VirtualBox VM...
Starting VM... <-- stays there forever

Anyone?

@phauer

This comment has been minimized.

Show comment
Hide comment
@phauer

phauer Sep 5, 2015

I have the same problem with VirtualBox-5.0.3-102467-Win.exe as wiradikusuma. Using VirtualBox-4.3.30-101610-Win.exe as visummagic supposed doesn't work either.

phauer commented Sep 5, 2015

I have the same problem with VirtualBox-5.0.3-102467-Win.exe as wiradikusuma. Using VirtualBox-4.3.30-101610-Win.exe as visummagic supposed doesn't work either.

@javafun

This comment has been minimized.

Show comment
Hide comment
@javafun

javafun Sep 8, 2015

Same as phauer. Neither 5.0 or latest 4.3 worked.

javafun commented Sep 8, 2015

Same as phauer. Neither 5.0 or latest 4.3 worked.

@wiradikusuma

This comment has been minimized.

Show comment
Hide comment
@wiradikusuma

wiradikusuma Sep 8, 2015

I installed the Toolbox yesterday on Windows 7 (I still have problem with Windows 10 as well), same problem.

I installed the Toolbox yesterday on Windows 7 (I still have problem with Windows 10 as well), same problem.

@raghunandy

This comment has been minimized.

Show comment
Hide comment
@raghunandy

raghunandy Sep 8, 2015

First time, it worked for me. I was able to see nice UI of Toolbox. But not
again same issue. I was able to install containers from kitematic UI. After
couple of days, it's not working. Now I switched to my old technique, using
Virtualbox with Ubuntu inside it which has docker.

=RrAaGgHhUu

On Sat, Sep 5, 2015 at 10:29 AM, Philipp Hauer notifications@github.com
wrote:

I have the same problem with VirtualBox-5.0.3-102467-Win.exe as
wiradikusuma. Using VirtualBox-4.3.30-101610-Win.exe as visummagic supposed
doesn't work either.


Reply to this email directly or view it on GitHub
#77 (comment).

First time, it worked for me. I was able to see nice UI of Toolbox. But not
again same issue. I was able to install containers from kitematic UI. After
couple of days, it's not working. Now I switched to my old technique, using
Virtualbox with Ubuntu inside it which has docker.

=RrAaGgHhUu

On Sat, Sep 5, 2015 at 10:29 AM, Philipp Hauer notifications@github.com
wrote:

I have the same problem with VirtualBox-5.0.3-102467-Win.exe as
wiradikusuma. Using VirtualBox-4.3.30-101610-Win.exe as visummagic supposed
doesn't work either.


Reply to this email directly or view it on GitHub
#77 (comment).

@dheerajbhaskar

This comment has been minimized.

Show comment
Hide comment
@dheerajbhaskar

dheerajbhaskar Sep 9, 2015

I followed @dave-tucker 's method. When I click on docker quickstart terminal shortcut, it gets stuck at the point mentioned by @wiradikusuma . If I remove the vm from virtualbox and start kitematic, it tries to download its own version of virtualbox, then I get the following error:

C:\Program Files\Docker Toolbox\kitematic\resources\resources\docker-machine.exe -D create -d virtualbox --virtualbox-memory 2048 default returned non zero exit code. Stderr: Error creating machine: exec: "VBoxManage": executable file not found in %PATH% You will want to check the provider to make sure the machine and associated resources were properly removed.

kitematic error

Has anyone figured this out?

I followed @dave-tucker 's method. When I click on docker quickstart terminal shortcut, it gets stuck at the point mentioned by @wiradikusuma . If I remove the vm from virtualbox and start kitematic, it tries to download its own version of virtualbox, then I get the following error:

C:\Program Files\Docker Toolbox\kitematic\resources\resources\docker-machine.exe -D create -d virtualbox --virtualbox-memory 2048 default returned non zero exit code. Stderr: Error creating machine: exec: "VBoxManage": executable file not found in %PATH% You will want to check the provider to make sure the machine and associated resources were properly removed.

kitematic error

Has anyone figured this out?

@dheerajbhaskar

This comment has been minimized.

Show comment
Hide comment
@dheerajbhaskar

dheerajbhaskar Sep 9, 2015

  • I've uninstalled everything
  • Restarted
  • installed Vbox 5.0.4
  • Restarted
  • installed docker toolbox 1.8.1(c)
  • Launched quickstart terminal shortcut
  • stuck on starting vm; the vm says its running in the vbox interface though
  • disappointed

I see a few people have gotten it to work on win 10 in this thread and elsewhere on the internets. How is that?

  • I've uninstalled everything
  • Restarted
  • installed Vbox 5.0.4
  • Restarted
  • installed docker toolbox 1.8.1(c)
  • Launched quickstart terminal shortcut
  • stuck on starting vm; the vm says its running in the vbox interface though
  • disappointed

I see a few people have gotten it to work on win 10 in this thread and elsewhere on the internets. How is that?

@yourchanges

This comment has been minimized.

Show comment
Hide comment
@yourchanges

yourchanges Sep 12, 2015

win 10 pro 64bit
docker toolbox 1.8.2
Starting VM... <-- stays there forever

win 10 pro 64bit
docker toolbox 1.8.2
Starting VM... <-- stays there forever

@dheerajbhaskar

This comment has been minimized.

Show comment
Hide comment
@dheerajbhaskar

dheerajbhaskar Sep 12, 2015

I went back to using boot2docker with 5.0.2 vbox. Seems to be working so
far.
On 12-Sep-2015 3:32 pm, "Giannis Halvatzakis" notifications@github.com
wrote:

I have also the same problem...


Reply to this email directly or view it on GitHub
#77 (comment).

I went back to using boot2docker with 5.0.2 vbox. Seems to be working so
far.
On 12-Sep-2015 3:32 pm, "Giannis Halvatzakis" notifications@github.com
wrote:

I have also the same problem...


Reply to this email directly or view it on GitHub
#77 (comment).

@rorisme

This comment has been minimized.

Show comment
Hide comment
@rorisme

rorisme Sep 13, 2015

I have managed it to work on my Windows 10 Pro 64bit
I've used a test build found on a post from the Docker Community Forum

rorisme commented Sep 13, 2015

I have managed it to work on my Windows 10 Pro 64bit
I've used a test build found on a post from the Docker Community Forum

@dheerajbhaskar

This comment has been minimized.

Show comment
Hide comment
@dheerajbhaskar

dheerajbhaskar Sep 13, 2015

Hi Rijkaard, could you please share the steps which got your setup working?
On 13-Sep-2015 4:39 pm, "Rijkaard Orismé" notifications@github.com wrote:

I have managed it to work on my Windows 10 Pro 64bit
I've used a test build found on a post from the Docker Community Forum
https://forums.docker.com/t/docker-toolbox-on-windows-10-is-it-possible/2822


Reply to this email directly or view it on GitHub
#77 (comment).

Hi Rijkaard, could you please share the steps which got your setup working?
On 13-Sep-2015 4:39 pm, "Rijkaard Orismé" notifications@github.com wrote:

I have managed it to work on my Windows 10 Pro 64bit
I've used a test build found on a post from the Docker Community Forum
https://forums.docker.com/t/docker-toolbox-on-windows-10-is-it-possible/2822


Reply to this email directly or view it on GitHub
#77 (comment).

@autoferrit

This comment has been minimized.

Show comment
Hide comment
@autoferrit

autoferrit Sep 22, 2015

I am still having this issue.l just downloaded toolbox and installed the latest test build of Virtualbox and installed the guest additions addon as well.

@jeffdm So I do not belive this issue should be marked as closed. I have also tried with the normal VBox release as well and get the same results. Other people seem to be having this issue as well.

I am still having this issue.l just downloaded toolbox and installed the latest test build of Virtualbox and installed the guest additions addon as well.

@jeffdm So I do not belive this issue should be marked as closed. I have also tried with the normal VBox release as well and get the same results. Other people seem to be having this issue as well.

@painhardcore

This comment has been minimized.

Show comment
Hide comment
@painhardcore

painhardcore Sep 22, 2015

DockerToolbox-1.8.2a not working on windows 10 and windows 8.1
docker

DockerToolbox-1.8.2a not working on windows 10 and windows 8.1
docker

@painhardcore

This comment has been minimized.

Show comment
Hide comment
@painhardcore

painhardcore Sep 22, 2015

Some strange errors.
Second when i remove VM and trying to start kinematic as administrator
docker2
docker3

Some strange errors.
Second when i remove VM and trying to start kinematic as administrator
docker2
docker3

@hakabe

This comment has been minimized.

Show comment
Hide comment
@hakabe

hakabe Sep 23, 2015

Workaround is to install the Docker Toolbox normally and then uninstall Virtualbox, plus the %userprofile%/.Virtualbox folder. Download the newest Virtualbox testbuild from https://www.virtualbox.org/wiki/Testbuilds (5.x) and install it.

Kinematic gave me error on the first run. Just click Delete vm and retry setup. There, you are set to go.

hakabe commented Sep 23, 2015

Workaround is to install the Docker Toolbox normally and then uninstall Virtualbox, plus the %userprofile%/.Virtualbox folder. Download the newest Virtualbox testbuild from https://www.virtualbox.org/wiki/Testbuilds (5.x) and install it.

Kinematic gave me error on the first run. Just click Delete vm and retry setup. There, you are set to go.

@git-bub

This comment has been minimized.

Show comment
Hide comment
@git-bub

git-bub Oct 3, 2015

I just ran into the issue others are reporting of getting stuck on the "Starting VM..." step when trying to launch the Docker Toolbox (Docker Quickstart Terminal) and was able to solve my situation. Your situation may be different, but for me the issue was that virtualization was disabled on my CPU.

I found this by opening VirtualBox while docker was stuck on that Starting VM step, and saw that the VM (named default) was running so I clicked the Show button in the toolbar. When it attempted to show the VM I got an error message from VirtualBox with the details regarding the virtualization issue and so I checked my BIOS and found I needed to enable it. Potentially you could go the opposite route and disable hardware virtualization for the docker VM and try launching the Docker Toolbox again, but I have not tested this.

Even if your issue is not virtualization, you may be able to get some details about what is holding you up by going into VirtualBox while stuck on that Starting VM step. Good luck.

git-bub commented Oct 3, 2015

I just ran into the issue others are reporting of getting stuck on the "Starting VM..." step when trying to launch the Docker Toolbox (Docker Quickstart Terminal) and was able to solve my situation. Your situation may be different, but for me the issue was that virtualization was disabled on my CPU.

I found this by opening VirtualBox while docker was stuck on that Starting VM step, and saw that the VM (named default) was running so I clicked the Show button in the toolbar. When it attempted to show the VM I got an error message from VirtualBox with the details regarding the virtualization issue and so I checked my BIOS and found I needed to enable it. Potentially you could go the opposite route and disable hardware virtualization for the docker VM and try launching the Docker Toolbox again, but I have not tested this.

Even if your issue is not virtualization, you may be able to get some details about what is holding you up by going into VirtualBox while stuck on that Starting VM step. Good luck.

@jouana

This comment has been minimized.

Show comment
Hide comment
@jouana

jouana Oct 5, 2015

Hi,
For start sorry for my english isn't my best skill.
So, I made what dave said on the top of this topic but before launch kitematic i deleted all virtualbox host-only eternet adapter and in control panel -> programe & features -> windows features, disabled Hyper-V

hope this can help you
+

jouana commented Oct 5, 2015

Hi,
For start sorry for my english isn't my best skill.
So, I made what dave said on the top of this topic but before launch kitematic i deleted all virtualbox host-only eternet adapter and in control panel -> programe & features -> windows features, disabled Hyper-V

hope this can help you
+

@extensionsapp

This comment has been minimized.

Show comment
Hide comment
@extensionsapp

extensionsapp Oct 6, 2015

Windows 10
VirtualBox-5.0.5-103003-Win
DockerToolbox-1.8.2c

Machine default already exists in VirtualBox.
Starting machine default...
Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
exit status 255

Looks like something went wrong... Press any key to continue...

Windows 10
VirtualBox-5.0.5-103003-Win
DockerToolbox-1.8.2c

Machine default already exists in VirtualBox.
Starting machine default...
Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
exit status 255

Looks like something went wrong... Press any key to continue...
@daodao10

This comment has been minimized.

Show comment
Hide comment
@daodao10

daodao10 Oct 7, 2015

Please make sure intel virtualization technology enabled in bios.
http://www.sysprobs.com/disable-enable-virtualization-technology-bios

daodao10 commented Oct 7, 2015

Please make sure intel virtualization technology enabled in bios.
http://www.sysprobs.com/disable-enable-virtualization-technology-bios

@whatwho

This comment has been minimized.

Show comment
Hide comment
@whatwho

whatwho Oct 8, 2015

I've tried to install docker toolbox on a windows 10 machine running in VirtualBox on OS X, but had the same problems as above. The interesting thing is, that I also tried to install it on my wife's windows 7 machine, and had no luck, the problem is the same (creating vm halts, kitematic also at 99%).

whatwho commented Oct 8, 2015

I've tried to install docker toolbox on a windows 10 machine running in VirtualBox on OS X, but had the same problems as above. The interesting thing is, that I also tried to install it on my wife's windows 7 machine, and had no luck, the problem is the same (creating vm halts, kitematic also at 99%).

@jouana

This comment has been minimized.

Show comment
Hide comment
@jouana

jouana Oct 8, 2015

Hi, delete the vm and relaunch.
Have a good day.
Antoine jouan
Le 6 oct. 2015 7:42 PM, "Surinam" notifications@github.com a écrit :

Windows 10
VirtualBox-5.0.5-103003-Win
DockerToolbox-1.8.2c

Machine default already exists in VirtualBox.
Starting machine default...
Started machines may have new IP addresses. You may need to re-run the docker-machine env command.
exit status 255

Looks like something went wrong... Press any key to continue...


Reply to this email directly or view it on GitHub
#77 (comment).

jouana commented Oct 8, 2015

Hi, delete the vm and relaunch.
Have a good day.
Antoine jouan
Le 6 oct. 2015 7:42 PM, "Surinam" notifications@github.com a écrit :

Windows 10
VirtualBox-5.0.5-103003-Win
DockerToolbox-1.8.2c

Machine default already exists in VirtualBox.
Starting machine default...
Started machines may have new IP addresses. You may need to re-run the docker-machine env command.
exit status 255

Looks like something went wrong... Press any key to continue...


Reply to this email directly or view it on GitHub
#77 (comment).

@danistefanovic

This comment has been minimized.

Show comment
Hide comment
@danistefanovic

danistefanovic Oct 14, 2015

I've had the same problem with the stucking Starting VM.... When I opened the default VM in VirtualBox, I've seen that the boot2docker whale banner was printed. It seems that it somehow worked but the Docker Quickstart Terminal was not "notified" about that.

The following steps fixed it for me:

  1. Install the newest VirtualBox test build
  2. Delete the default machine: docker-machine rm default
  3. Start Kitematic and let it create the default virtual machine again

Don't forget to connect your shell with the default machine: eval $(docker-machine env default)

I've had the same problem with the stucking Starting VM.... When I opened the default VM in VirtualBox, I've seen that the boot2docker whale banner was printed. It seems that it somehow worked but the Docker Quickstart Terminal was not "notified" about that.

The following steps fixed it for me:

  1. Install the newest VirtualBox test build
  2. Delete the default machine: docker-machine rm default
  3. Start Kitematic and let it create the default virtual machine again

Don't forget to connect your shell with the default machine: eval $(docker-machine env default)

@cmlval

This comment has been minimized.

Show comment
Hide comment
@cmlval

cmlval Oct 19, 2015

Hello, i have a query about docker on windows, recently i installed it but i want to change the folder .docker to another place for example D:/.docker ... is posible to do that???

cmlval commented Oct 19, 2015

Hello, i have a query about docker on windows, recently i installed it but i want to change the folder .docker to another place for example D:/.docker ... is posible to do that???

@Kapusch

This comment has been minimized.

Show comment
Hide comment
@Kapusch

Kapusch Oct 25, 2015

@danistefanovic It worked for me, thanks a lot ! Too much time spoiled for that, it was great to read your answer.

Kapusch commented Oct 25, 2015

@danistefanovic It worked for me, thanks a lot ! Too much time spoiled for that, it was great to read your answer.

@numediaweb

This comment has been minimized.

Show comment
Hide comment
@numediaweb

numediaweb Oct 26, 2015

@danistefanovic Thanks! Installing latset virtualbox version fixed it; VirtualBox-5.0.9-103625-Win.exe on windows 10 (64bit).

@danistefanovic Thanks! Installing latset virtualbox version fixed it; VirtualBox-5.0.9-103625-Win.exe on windows 10 (64bit).

@greha

This comment has been minimized.

Show comment
Hide comment
@greha

greha Nov 3, 2015

@danistefanovic
How can i run the eval $(docker-machine env default) command on a win10 box?

greha commented Nov 3, 2015

@danistefanovic
How can i run the eval $(docker-machine env default) command on a win10 box?

@danistefanovic

This comment has been minimized.

Show comment
Hide comment
@danistefanovic

danistefanovic Nov 3, 2015

@greha Use Git Bash/MinGW

@greha Use Git Bash/MinGW

@jjmartin

This comment has been minimized.

Show comment
Hide comment
@jjmartin

jjmartin Nov 3, 2015

i'm finding that after starting kitmatic and havingit build the vm and get docker running - docker-machine does not show the vm running when in administrator powershell but non-admin shows it fine

jjmartin commented Nov 3, 2015

i'm finding that after starting kitmatic and havingit build the vm and get docker running - docker-machine does not show the vm running when in administrator powershell but non-admin shows it fine

@jjmartin

This comment has been minimized.

Show comment
Hide comment
@jjmartin

jjmartin Nov 3, 2015

@greha if you run from powershell - you can do docker-machine env --shell powerhsell default |Invoke-expression

jjmartin commented Nov 3, 2015

@greha if you run from powershell - you can do docker-machine env --shell powerhsell default |Invoke-expression

@kjitin

This comment has been minimized.

Show comment
Hide comment
@kjitin

kjitin Nov 15, 2015

Got docker 1.9.0c working on windows 10, first installed docker ...removed the virtualbox 5.0.1 associated with it...uninstalled it from the machine....restarted windows...and installed VirtualBox 5.0.11-104101....docker started working after it detected the new Virtualbox

kjitin commented Nov 15, 2015

Got docker 1.9.0c working on windows 10, first installed docker ...removed the virtualbox 5.0.1 associated with it...uninstalled it from the machine....restarted windows...and installed VirtualBox 5.0.11-104101....docker started working after it detected the new Virtualbox

@francoishill

This comment has been minimized.

Show comment
Hide comment
@francoishill

francoishill Nov 16, 2015

See if there any processes (images) with the name docker-machine-driver-virtualbox.exe running in Windows' Resource Monitor under the Network section. Mine got stuck at "busy creating" for about 30 minutes while downloading this.

See if there any processes (images) with the name docker-machine-driver-virtualbox.exe running in Windows' Resource Monitor under the Network section. Mine got stuck at "busy creating" for about 30 minutes while downloading this.

@nitind

This comment has been minimized.

Show comment
Hide comment
@nitind

nitind Nov 24, 2015

@greha Append "--shell cmd", e.g. docker-machine env default --shell cmd, will emit something that works there.

nitind commented Nov 24, 2015

@greha Append "--shell cmd", e.g. docker-machine env default --shell cmd, will emit something that works there.

@dreamcat4

This comment has been minimized.

Show comment
Hide comment
@dreamcat4

dreamcat4 Dec 5, 2015

Installed via chocolatey pkg manager:

  • VirtualBox 5.10
  • docker client
  • docker compose
  • docker machine

Installed docker toolbox silently with args: /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-

Then:

start.sh

and

KiteMatic

I think I'll try again after reinstalling Windows 10. But AFAIK the error message from Kiematic isn't right. As docker-machine.exe files are all present in C:\Program Files\Docker Toolbox folder.

Installed via chocolatey pkg manager:

  • VirtualBox 5.10
  • docker client
  • docker compose
  • docker machine

Installed docker toolbox silently with args: /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-

Then:

start.sh

and

KiteMatic

I think I'll try again after reinstalling Windows 10. But AFAIK the error message from Kiematic isn't right. As docker-machine.exe files are all present in C:\Program Files\Docker Toolbox folder.

@jjmartin

This comment has been minimized.

Show comment
Hide comment
@jjmartin

jjmartin Dec 11, 2015

still having issues with win 10 now - i don't know if recent updates screwed it up or what - but it was working at one point, now i have uninstalled and resinstalleed toolbox and virtualbox a number of times and can't seem to get it to go... i also seemed to run into this issue on virtual box - https://forums.virtualbox.org/viewtopic.php?f=6&t=70199
but i don't know if anything i did on that actually got me any closer to running docker again...

still having issues with win 10 now - i don't know if recent updates screwed it up or what - but it was working at one point, now i have uninstalled and resinstalleed toolbox and virtualbox a number of times and can't seem to get it to go... i also seemed to run into this issue on virtual box - https://forums.virtualbox.org/viewtopic.php?f=6&t=70199
but i don't know if anything i did on that actually got me any closer to running docker again...

@Zugwalt

This comment has been minimized.

Show comment
Hide comment
@Zugwalt

Zugwalt Feb 17, 2016

Latest docker toolbox for windows I got, version 1.10.1 came with VirtualBox 5.0.14. Didn't install Kitematic (I used cli) and git (already had it installed). Worked out of the box for me! If we are indeed all set now without having to use a test build of docker toolbox, @dave-tucker you may want to edit your topmost reply again with this information.

Zugwalt commented Feb 17, 2016

Latest docker toolbox for windows I got, version 1.10.1 came with VirtualBox 5.0.14. Didn't install Kitematic (I used cli) and git (already had it installed). Worked out of the box for me! If we are indeed all set now without having to use a test build of docker toolbox, @dave-tucker you may want to edit your topmost reply again with this information.

@ryanmaclean

This comment has been minimized.

Show comment
Hide comment
@ryanmaclean

ryanmaclean Apr 17, 2016

This appears to have reared it's head again: Windows 10, no virtualbox installed, clean install, virtualization enabled in BIOS.

Kitematic:

Command failed: C:\Program Files\Docker Toolbox\docker-machine.exe -D create -d virtualbox --virtualbox-memory 2048 default,Docker Machine Version: 0.7.0, build a650a40,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:51593,() 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:51597,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(default) Calling .GetMachineName,(default) Calling .DriverName,(default) Calling .GetCreateFlags,(default) Calling .SetConfigFromFlags,(default) Calling .PreCreateCheck,(default) DBG | COMMAND: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe --version,(default) DBG | STDOUT:,(default) DBG | {,(default) DBG | 5.0.16r105871,(default) DBG | },(default) DBG | STDERR:,(default) DBG | {,(default) DBG | },Error with pre-create check: "Hyper-V is installed. VirtualBox won't boot a 64bits VM when Hyper-V is activated. If it's installed but deactivated, you can use --virtualbox-no-vtx-check to try anyways",Opting out of crash reporting.,

Docker Quickstart Terminal:

Running pre-create checks...
Error with pre-create check: "Hyper-V is installed. VirtualBox won't boot a 64bits VM when Hyper-V is activated. If it's installed but deactivated, you can use --virtualbox-no-vtx-check to try anyways"
Looks like something went wrong in step ´Checking if machine default exists´... Press any key to continue...

Following the suggestion in the first comment:

$ docker-machine rm default
About to remove default
Are you sure? (y/n): y
Error removing host "default": Host does not exist: "default"

ryanmaclean commented Apr 17, 2016

This appears to have reared it's head again: Windows 10, no virtualbox installed, clean install, virtualization enabled in BIOS.

Kitematic:

Command failed: C:\Program Files\Docker Toolbox\docker-machine.exe -D create -d virtualbox --virtualbox-memory 2048 default,Docker Machine Version: 0.7.0, build a650a40,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:51593,() 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:51597,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(default) Calling .GetMachineName,(default) Calling .DriverName,(default) Calling .GetCreateFlags,(default) Calling .SetConfigFromFlags,(default) Calling .PreCreateCheck,(default) DBG | COMMAND: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe --version,(default) DBG | STDOUT:,(default) DBG | {,(default) DBG | 5.0.16r105871,(default) DBG | },(default) DBG | STDERR:,(default) DBG | {,(default) DBG | },Error with pre-create check: "Hyper-V is installed. VirtualBox won't boot a 64bits VM when Hyper-V is activated. If it's installed but deactivated, you can use --virtualbox-no-vtx-check to try anyways",Opting out of crash reporting.,

Docker Quickstart Terminal:

Running pre-create checks...
Error with pre-create check: "Hyper-V is installed. VirtualBox won't boot a 64bits VM when Hyper-V is activated. If it's installed but deactivated, you can use --virtualbox-no-vtx-check to try anyways"
Looks like something went wrong in step ´Checking if machine default exists´... Press any key to continue...

Following the suggestion in the first comment:

$ docker-machine rm default
About to remove default
Are you sure? (y/n): y
Error removing host "default": Host does not exist: "default"
@autoferrit

This comment has been minimized.

Show comment
Hide comment
@autoferrit

autoferrit Apr 20, 2016

I have the same issue as @ryanmaclean . I have a clean install of windows 10 with virtualization enabled. I also get it when dual booting with bootcamp on a 2013 macbook pro.

I have the same issue as @ryanmaclean . I have a clean install of windows 10 with virtualization enabled. I also get it when dual booting with bootcamp on a 2013 macbook pro.

@JohnBernardsson

This comment has been minimized.

Show comment
Hide comment
@JohnBernardsson

JohnBernardsson Apr 25, 2016

@ryanmaclean @SkiftCreative For me this was fixed disabling Hyper-V: http://www.eightforums.com/tutorials/42041-hyper-v-enable-disable-windows-8-a.html

I had to disable it anyways to use Android emulator with x86 emulation so...

Hope this helps!

@ryanmaclean @SkiftCreative For me this was fixed disabling Hyper-V: http://www.eightforums.com/tutorials/42041-hyper-v-enable-disable-windows-8-a.html

I had to disable it anyways to use Android emulator with x86 emulation so...

Hope this helps!

@azarudeen90

This comment has been minimized.

Show comment
Hide comment
@azarudeen90

azarudeen90 Jun 3, 2016

@JohnBernardsson Thanks for link with clear cut idea to disable Hyper-V setting completely.

It clearly solved my problem in my Windows 10 system. But still its just a hard way as the change setting needs a sys restart. My VMware workstation does needs the Hyper-V for startup certain machines.

@JohnBernardsson Thanks for link with clear cut idea to disable Hyper-V setting completely.

It clearly solved my problem in my Windows 10 system. But still its just a hard way as the change setting needs a sys restart. My VMware workstation does needs the Hyper-V for startup certain machines.

@scetix

This comment has been minimized.

Show comment
Hide comment
@scetix

scetix Sep 6, 2016

Solution for me was to discover that HV Host Service was not running/would not start. After googling i found this:

http://www.rovermarinho.org/hyper-v-could-not-be-started-because-the-hypervisor-is-not-running/

TLDR;
Open CMD in Admin mode, run BCDEDIT /set hypervisorlaunchtype auto and restart

scetix commented Sep 6, 2016

Solution for me was to discover that HV Host Service was not running/would not start. After googling i found this:

http://www.rovermarinho.org/hyper-v-could-not-be-started-because-the-hypervisor-is-not-running/

TLDR;
Open CMD in Admin mode, run BCDEDIT /set hypervisorlaunchtype auto and restart

@ruthyaneth

This comment has been minimized.

Show comment
Hide comment
@ruthyaneth

ruthyaneth Nov 12, 2017

Install docker, tensorflow and python
https://youtu.be/OiPjSnKAmSI

Install docker, tensorflow and python
https://youtu.be/OiPjSnKAmSI

@ruthyaneth

This comment has been minimized.

Show comment
Hide comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment