- #BENEFITS OF WINDOWS 10 HYPER V VS VIRTUALBOX CODE#
- #BENEFITS OF WINDOWS 10 HYPER V VS VIRTUALBOX DOWNLOAD#
Since I already have virutalbox installed, I unchecked it. This time at least I am able to run the dockertoolbox.exe and get to installation selection.
#BENEFITS OF WINDOWS 10 HYPER V VS VIRTUALBOX DOWNLOAD#
Then I tried to download and set up DockerTool. (You would think that with 500MB, no additional packages are needed, but apparently not the case). Apparently it is trying to download additional packages over internet and got blocked by not able to get through the proxy. I run as admin, and a GUI popup saying Downloading packages… but not responding. After downloading a 500MB+ Docker for Windows Installer.exe. It is not clear what I gave up if I am going to Docker Toolbox even if I have an non-legacy windows… Any way, here is what I have done…įirst I tried Docker for Windows. So I am also facing the same question: Docker for Windows or Docker Toolbox? BTW, I am behind a proxy/firewall. Now I need to do docker development (build new docker). I have Virtual Box 5.2.x installed and running, and I am not inclined to give it up yet. That means theres no Virtual Machine or Hyper-V involved (unless you want), so Linux Containers run on Windows itself using Windows 10s built in container support. I am running Windows 10 Enterprise 2017 (so not really a legacy windows). With the latest version of Windows 10 (or 10 Server) and the beta of Docker for Windows, theres native Linux Container support on Windows. I suspect that the approach of steering all windows users down the the docker via hyper-v path may not prove popular for windows users which might be counter productive for Docker? I guess a new docker for windows user can just try installing docker to a Centos virtualbox vm but for new to docker windows users who may not be sufficiently skilled in linux etc, having an ‘officially supported’ installation approach that deals specifically with usage for non-Hyper-V windows users would be very helpful.
#BENEFITS OF WINDOWS 10 HYPER V VS VIRTUALBOX CODE#
Perhaps both a Docker for Windows (Hyper-V) and a Docker for Windows (Non-Hyper-V) approach can be officially adopted?įor all the many reasons mentioned by others on the docker forum it would appear to make sense if a “non-Hyper-V docker for windows” target was maintained with current docker code or if this is not going to be possible, perhaps Docker could ‘officially recommend’ another non-Hyper-V virutualisation process eg VMWare/Virtualbox distro and usage process for windows users who either don’t want to or can’t run Hyper-V? Legacy? I’m concerned if Docker Toolbox is to be described as ‘legacy’ if this means that no other ‘non-Hyper-V windows’ solution is to be officially supported by Docker going forward?