d4win troubleshooting topic on wifi, networking issues (docker#3497)

* d4win troubleshooting topic on wifi, networking issues Signed-off-by: Victoria Bialas <[email protected]> * copyedit on WiFi capitalization Signed-off-by: Victoria Bialas <[email protected]>
patrickbaber · Jun 7, 2017 · 96f528f · 96f528f
1 parent 947bf04
commit 96f528f
Show file tree

Hide file tree

Showing 5 changed files with 61 additions and 5 deletions.
diff --git a/docker-for-windows/images/hyper-v-enable-status.png b/docker-for-windows/images/hyper-v-enable-status.png
diff --git a/docker-for-windows/images/hyperv-manager.png b/docker-for-windows/images/hyperv-manager.png
diff --git a/docker-for-windows/troubleshoot.md b/docker-for-windows/troubleshoot.md
@@ -265,19 +265,70 @@ Virtualization needs to be enabled in the BIOS. The steps to do so are Vendor
 specific, but typically the BIOS option is called `Virtualization Technology
 (VTx)` or similar.
 
+Once Hyper-V is enabled, it will show up as such on "Turn Windows features on or
+off".
+
+![Hyper-V on Windows features](images/hyper-v-enable-status.png )
+
 ### Virtualization must be enabled
 
 In addition to [Hyper-V](#hyper-v), virtualization must be enabled.
 
-If, at some point, if you manually uninstall Hyper-V or disable virtualization, Docker for Windows will not start.
+If, at some point, if you manually uninstall Hyper-V or disable virtualization,
+Docker for Windows will not start.
 
-Verify that virtualization is enabled on Task Manager.
+Verify that virtualization is enabled by checking the Performance tab on the
+Task Manager.
 
 ![Task Manager](images/win-virtualization-enabled.png)
 
 See also, the user reported issue [Unable to run Docker for Windows on Windows
 10 Enterprise](https://github.com/docker/for-win/issues/74)
 
+### Networking and WiFi problems upon Docker for Windows install
+
+Some users have encountered networking issues during install and startup of
+Docker for Windows. For example, upon install or auto-reboot, network adapters
+and/or WiFi gets disabled. In some scenarios, problems are due to having
+VirtualBox or its network adapters still installed, but in other scenarios this
+is not the case. (See also, Docker for Windows issue on GitHub: [Enabling
+Hyper-V feature turns my wi-fi off
+](https://github.com/docker/for-win/issues/139).)
+
+Here are some steps to take if you encounter similar problems:
+
+1.	Make sure virtualization is enabled, as described in the [Virtualization
+troubleshooting topic](#virtualization-must-be-enabled).
+
+2.	Make sure the Hyper-V is installed and enabled, as described in the previous
+[Hyper-V troubleshooting topic](#hyper-v).
+
+3.	Check your network switches to see if `DockerNAT` is enabled.
+
+	Open the **Hyper-V Manager**. (On Windows 10, just search for the
+	Hyper-V Manager in the search field in the lower left search field.)
+
+	Select the Virtual Switch Manager on the left-side **Actions** panel.
+
+	![Hyper-V manager](images/hyperv-manager.png)
+
+4.	Set up an external network switch. If you plan at any point to use [Docker
+Machine](/machine/overview.md) to set up multiple local VMs, you will need this
+anyway, as described in the topic on the [Hyper-V driver for [Docker
+Machine](/machine/drivers/hyper-v.md#example). You can replace `DockerNAT` with
+this switch.
+
+5.	If previous steps fail to solve the problems, follow steps on the
+[Cleanup README]((https://github.com/Microsoft/Virtualization-Documentation/blob/master/windows-server-container-tools/CleanupContainerHostNetworking/README.md)).
+
+	>Read full description of consequences before you run Windows cleanup script
+	>
+  >The cleanup command has a `-Cleanup` flag and a
+	 `-ForceDeleteAllSwitches` flag. Be sure to read the whole page
+	 before running any scripts, especially the warnings with regard
+	 to the `-ForceDeleteAllSwitches` option.
+	 {: .warning-vanilla}
+
 ### Windows containers and Windows Server 2016
 
 If you have questions about how to set up and run Windows containers on Windows

diff --git a/machine/drivers/hyper-v.md b/machine/drivers/hyper-v.md
@@ -24,6 +24,7 @@ Hyper-V](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick
 > [Internet Connection Sharing](http://www.packet6.com/allowing-windows-8-1-hyper-v-vm-to-work-with-wifi/).
 >
 > * This reference page includes an [example](hyper-v.md#example) that shows how to use an elevated (Administrator-level) PowerShell and how to create and use an external network switch.
+{: .note-vanilla}
 
 ## Usage
 

diff --git a/machine/get-started.md b/machine/get-started.md
@@ -40,9 +40,13 @@ Therefore, you cannot run the two solutions simultaneously. But you can still
 use `docker-machine` to create more local VMs by using the Microsoft Hyper-V
 driver.
 
-* The only prerequisite is to have Docker for Windows installed. If you want to create multiple local machines, use the
-Microsoft `hyperv` driver to create them. (See the [Docker Machine driver for
-Microsoft Hyper-V](drivers/hyper-v.md).)
+The prerequisites are:
+
+* Have Docker for Windows installed, and running (which requires that virtualization and Hyper-V are enabled, as described in [What to know before you install Docker for Windows](/docker-for-windows/install.md#what-to-know-before-you-install)).
+
+* Set up the Hyper-V driver to use an external virtual network switch See
+the [Docker Machine driver for Microsoft Hyper-V](drivers/hyper-v.md) topic,
+which includes an /machine/drivers/hyper-v.md#example of how to do this.
 
 #### If you are using Docker for Mac