VirtualBox & Hyper-V

[andrevtg]

This can be a non-issue (sorry for that) but the swarm lab suggests installing Docker for Mac in order to use docker-machine later on for provisioning local VirtualBox VMs.

Isn't there an issue about having both virtualization products on the same box (like VirtualBox breaking after Hyper-V runs)? I don't have a Windows box anymore, so I can't test it myself.

If this is something as simple as "do not run Docker for Windows after boot" perhaps it should be mentioned. Looking up the "disabling Hyper-V" subject looks kinda scary (https://marcofranssen.nl/switch-between-hyper-v-and-virtualbox-on-windows/).

Once again, if this is a non-issue please ignore.

[ManoMarks]

It's a good documentation issue. We need to test the lab in Powershell. Virtualbox will not run with Hyper-V enabled. However you should be able to use the hyperv driver instead.

[londoncalling]

@andrevtg @ManoMarks Docker for Mac and Windows both install Docker Machine as part of the install (along with Docker Compose).

On Mac, we have a detailed description of how these components interact: https://docs.docker.com/docker-for-mac/docker-toolbox/

On Windows, I need to update the docs to be clearer, but you should be able to switch off Hyper-V, and then run Docker Machine with Virtual Box with no repercussions. I did this the other day to test a different scenario and all worked fine. I will re-test this particular entire workflow today (testing Swarm as well) to be sure, then document it. More soon. Thanks for raising the question.
Cc'ing @friism

[StefanScherer]

@andrevtg I'm running VMware Fusion + VirtualBox + Docker for Mac on my MBP. Each hypervisor has its strengths so I can switch projects and run them in parallel. Two for Vagrant, all three for Docker.

On Windows 7 I have a notebook with VMware Workstation + VirtualBox, also works fine and in parallel. Both for Vagrant or Docker. There is no Hyper-V on Windows 7 so I have this "freedom".

But on a Windows 10 machine you probably switch to Hyper-V and then you are locked in to it as it does not support other hypervisors in parallel. This might change in the future, but for now you have to reboot your host to switch hypervisors.

Hm, while writing this I think of that we should update the swarm docs to use docker-machine -d hyperv which should work in parallel to a Docker for Windows installation.

[londoncalling]

@andrevtg @StefanScherer thanks Stefan. I am just testing all this now, and figured out what I need to add to the docs. On Docker for Mac, users can use Toolbox-installed Docker machine (which installs VirtualBox) or the Docker Machine that comes with Docker for Mac to create machines on a cloud provider (e.g., AWS, Digital Ocean, etc.) then use either of those sets of machines as swarm nodes.

On Docker for Windows it's a little more restrictive and you guys are right, you can't use Docker Machine to create local machines (because your only option there would be to create them using VirtualBox, which you can't have running with Hyper-V). But what you can do, is use the Docker Machine that comes with Docker for Windows to create remote machines on a cloud provider (then use them as swarm nodes). This scenario doesn't rely on VirtualBox, and doesn't conflict with Hyper-V at all. And it's a way to use your d4win install to experiment with multi-node Swarm.

I'm going to just finish this test with Docker for Windows creating cloud nodes, and if it works I'll update the Swarm docs to clarify this. I'll ping you on the exact wording with which I plan to update the docs if you want to chime in. More soon, thanks!

[londoncalling]

@StefanScherer I'll ask @friism about your suggestion re: docker-machine -d hyperv idea and also get him to review everything

[andrevtg]

Instead of cloud nodes maybe the docs should point to using the hyper-v
driver for Docker-machine.

Haven't tested them myself, tho...

Em quarta-feira, 21 de setembro de 2016, Victoria Bialas <
notifications@github.com> escreveu:

@andrevtg https://github.com/andrevtg @StefanScherer
https://github.com/StefanScherer thanks Stefan. I am just testing all
this now, and figured out what I need to add to the docs. On Docker for
Mac, users can use Toolbox-installed Docker machine (which installs
VirtualBox) or the Docker Machine that comes with Docker for Mac to create
machines on a cloud provider (e.g., AWS, Digital Ocean, etc.) then use
either of those sets of machines as swarm nodes.

On Docker for Windows it's a little more restrictive and you guys are
right, you can't use Docker Machine to create local machines (because your
only option there would be to create them using VirtualBox, which you can't
have running with Hyper-V). But what you can do, is use the Docker Machine
that comes with Docker for Windows to create remote machines on a cloud
provider (then use them as swarm nodes). I'm going to just finish this test
with Docker for Windows creating cloud nodes, and if it works I'll update
the Swarm docs to clarify this. I'll ping you on the exact wording with
which I plan to update the docs if you want to chime in. More soon, thanks!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#55 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJ3LO8G4x7qfqnt9xt4a9pWD5H9FLG6aks5qsZ6rgaJpZM4KCxxz
.

André Fernandes
Founder, Board Advisor
+55 21 2232-0123
+55 21 98191-1299
andre@vertigo.com.br

[londoncalling]

@andrevtg well, I don't think that will work but will give it a try, and let you know. If it did, it would be fantastic :-)

[londoncalling]

@andrevtg https://github.com/andrevtg , it totally works with the hyper-v
driver ! I'll have the documentation all updated tomorrow regarding this
(yay!)

On Wednesday, September 21, 2016, André Fernandes notifications@github.com
wrote:

Instead of cloud nodes maybe the docs should point to using the hyper-v
driver for Docker-machine.

Haven't tested them myself, tho...

Em quarta-feira, 21 de setembro de 2016, Victoria Bialas <
notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');> escreveu:

@andrevtg https://github.com/andrevtg @StefanScherer
https://github.com/StefanScherer thanks Stefan. I am just testing all
this now, and figured out what I need to add to the docs. On Docker for
Mac, users can use Toolbox-installed Docker machine (which installs
VirtualBox) or the Docker Machine that comes with Docker for Mac to
create
machines on a cloud provider (e.g., AWS, Digital Ocean, etc.) then use
either of those sets of machines as swarm nodes.

On Docker for Windows it's a little more restrictive and you guys are
right, you can't use Docker Machine to create local machines (because
your
only option there would be to create them using VirtualBox, which you
can't
have running with Hyper-V). But what you can do, is use the Docker
Machine
that comes with Docker for Windows to create remote machines on a cloud
provider (then use them as swarm nodes). I'm going to just finish this
test
with Docker for Windows creating cloud nodes, and if it works I'll update
the Swarm docs to clarify this. I'll ping you on the exact wording with
which I plan to update the docs if you want to chime in. More soon,
thanks!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#55 (comment), or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/
AJ3LO8G4x7qfqnt9xt4a9pWD5H9FLG6aks5qsZ6rgaJpZM4KCxxz>
.

André Fernandes
Founder, Board Advisor
+55 21 2232-0123
+55 21 98191-1299
andre@vertigo.com.br
javascript:_e(%7B%7D,'cvml','andre@vertigo.com.br');

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#55 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALHuA0hwM1Fyx7LnbPiNXCvx_Jq5s0dcks5qsaBXgaJpZM4KCxxz
.

[ManoMarks]

@andrevtg There's updated documentation in the Hyper V driver:
https://docs.docker.com/machine/drivers/hyper-v/
And I've added a Powershell script to the Swarm Mode tutorial.