Successful installation of Docker for Windows
unable to get basic installation completed with beta7
Steps to reproduce the behavior
(all started with a Wireless Connection)
- This laptop started as a Windows 7 that was upgraded to Windows 10 Pro to accommodate requirements for Docker for Windows.
- Hyper-V role is not included as part of the Windows 7–> Windows 10 upgrade. I had removed VirtualBox before the upgrade but had not removed VMware Workstation 9.
- Download of Docker for Windows and installation proceed as one would think. Installation of Docker for Windows realizes that HyperV role does NOT exist and solicits a response to install HyperV.
- HyperV role gets added which requires a restart of laptop.
- Role is successfully added but Docker For Windows fails with ERROR: ‘MobyLinuxVM’ failed to start. ‘MobyLinuxVM’ failed to initialize.
- HyperV Manager was inspected and DockerNAT switch is connected to internal network.
- Removed all components (HyperV role, Docker For Windows) and restarted.
- Reinstall with same result
- Repeat removal process and this time I remove VMware Workstation 9.
- Reinstall with same results for MobyLinuxVM
- Try to change DockerNAT switch to connect to wireless adapter.
- Same result
- removed Docker For Windows and HyperV again
- connected laptop via hardwired connection — wireless device if now turned off.
- complete repeat of the above process and still unable to start MobyLinuxVM
Had to change the execution policy of the laptop to get .\DockerDebugInfo.ps1 to run. I am unaware of what would be the appropriate information to include to minimize privacy concerns. I have the output available if needed and if you could suggest what somewhat sanitized approach might be.
Suggestion: I might have compromised the entire process by having VMworkstation installed ahead of the Docker For Windows installation process. I seemed like it added the HyperV role successfully via your installation process but when I tried to install the role myself — it indicated that I had to remove Workstation. The same might be true for Parallels or other virtualization technologies. Probably want to guard against all things that can conflict/compromise a successful HyperV role addition for you installation process.