User Guide

  • 04/24/2019
  • Public Content

Troubleshooting Docker for Windows

This section contains troubleshooting topics you can use to insure that Docker has been properly installed and configured on your system.

Docker is partially installed or misconfigured

A Windows system on which Docker has been installed but has a configuration issue will respond with something like the following to the "docker version" command:
> docker version Client: Version: 17.09.0-ce API version: 1.32 Go version: go1.8.3 Git commit: afdb6d4 Built: Tue Sep 26 22:40:09 2017 OS/Arch: windows/amd64 error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.32/version: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.
To start the Docker for Windows subsystem, type the following (including the double-quote " characters):
> "%ProgramFiles%\Docker\Docker\Docker for Windows.exe"

Verify that Docker is installed and running

A configured and running Docker installation will respond similarly to this:
> docker version Client: Version: 17.09.0-ce API version: 1.32 Go version: go1.8.3 Git commit: afdb6d4 Built: Tue Sep 26 22:40:09 2017 OS/Arch: windows/amd64 Server: Version: 17.09.0-ce API version: 1.32 (minimum version 1.12) Go version: go1.8.3 Git commit: afdb6d4 Built: Tue Sep 26 22:45:38 2017 OS/Arch: linux/amd64 Experimental: true

"Hardware assisted virtualization and data execution protection must be enabled in the BIOS"

Typically, this problem is due to a disabled Hyper-V or because the hypervisor agent is not running.
  1. Open a Windows shell 
    as administrator
     and enable Hyper-V with:
    > dism /Online /Enable-Feature:Microsoft-Hyper-V /All
  2. Reboot your machine and see if Docker for Windows starts.
  3. If the above doesn't work, open a Windows shell 
    as administrator
     and enable the hypervisor with:
    > bcdedit /set hypervisorlaunchtype auto
If Docker for Windows is still not working properly, try the following additional solutions, which are based on instructions extracted from this Docker for Windows issue thread.
  1. Reboot your machine and see if Docker for Windows starts.
  2. Copy this path: 
    Control Panel\Programs\Programs and Features
    into a File Explorer address bar.
  3. Click
    Turn Windows feature on or off
    on the left side of the Control Panel.
  4. Clear the 
    Hyper-V
     check box in the list of Windows features.
  5. Reboot your machine and start Docker for Windows (or reinstall if necessary). If the above doesn't work, then Virtualization Based Security (VBS) might be interfering and needs to be disabled. Try the following to disable VBS:
  6. Open the
    Local Group Policy Editor
    (
    gpedit.msc
    )
  7. Go to
    Computer Configuration\Administrative Templates\System\Device Guard
If the above doesn't work, then try this VMware KB article, which is designed to enable the use of an alternate hypervisor and will disable VBS and Hyper-V.

Product and Performance Information

1

Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804