Docker On Windows 10 Pro

2/13/2022by admin

Estimated reading time: 16 minutes

Welcome to Docker Desktop! The Docker Desktop for Windows user manual provides information on how to configure and manage your Docker Desktop settings.

Download And Install Docker On Windows 10 Pro; Windows Live Messenger (MSN Messenger) is a instant messaging software provides by the Microsoft. Windows Live Messenger is a part of Windows Essentials 2012 suite, which is not installed by default on Windows 10. How to install Docker Toolbox on Windows: A step by step guide to install docker. Docker works cross-platform and such supports execution on a Windows host, including Windows 10 (Pro or Enterprise). This makes Windows 10 a perfect development environment for Docker use-cases. On top of this, Windows is also the only platform, for now at least, that can run Windows and Linux based containers.

For information about Docker Desktop download, system requirements, and installation instructions, see Install Docker Desktop.


The Docker Desktop menu allows you to open the Docker Dashboard, run the Quick Start Guide, configure your Docker settings such as installation, updates, version channels, Docker Hub login, and more.

This section explains the configuration options accessible from the Settings dialog.

  1. To open the Docker Desktop menu, right-click the Docker icon in the Notifications area (or System tray):

  2. Select Settings to open the Settings dialog:

Oct 31, 2020 With Windows 10 introducing WSL2 you can now run Docker image from Ubuntu running via WSL2 that’s connected to your Host’s Docker Desktop app. That’s just insane! It’s inception in OS level. Today we will take a look at how to turn on this integration, so you can run Docker inside Ubuntu that’s running inside Windows 10 via WSL2. Here is what worked for me: Turn off the Hyper-V setting in Control Panel-Programs and Features -'Turn Windows features on or off'. Restart computer. After computer has been restarted, your existing docker instance will detect that your Hyper-V setting is turned off and will ask you if you want to allow docker to enable the Hyper-V feature.

Jun 26, 2020 how to enable hyper-v in windows 10 home edition for running windows phone 8.1 emulator 229 Docker for Windows error: 'Hardware assisted virtualization and data execution protection must be enabled in the BIOS'.


On the General tab of the Settings dialog, you can configure when to start and update Docker.

  • Automatically check for updates: By default, Docker Desktop is configured to check for newer versions automatically. If you have installed Docker Desktop as part of an organization, you may not be able to update Docker Desktop yourself. In that case, upgrade your existing organization to a Team plan and clear this checkbox to disable the automatic check for updates.

  • Start Docker when you log in: Select this option to automatically start Docker Desktop when you log into your Windows machine.

  • Expose daemon on tcp://localhost:2375 without TLS: Click this option to enable legacy clients to connect to the Docker daemon. You must use this option with caution as exposing the daemon without TLS can result in remote code execution attacks.

  • Use the WSL 2 based engine: WSL 2 provides better performance than the legacy Hyper-V backend. For more information, see Docker Desktop WSL 2 backend.

  • Send usage statistics: By default, Docker Desktop sends diagnostics,crash reports, and usage data. This information helps Docker improve andtroubleshoot the application. Clear the check box to opt out. Docker may periodically prompt you for more information.

  • Show weekly tips: Displays useful advice and suggestions about using Docker.

  • Open Docker Desktop dashboard at startup: Automatically opens the dashboard when starting Docker Desktop.

  • Use Docker Compose V2: Select this option to enable the docker-compose command to use Docker Compose V2. For more information, see Docker Compose V2.


The Resources tab allows you to configure CPU, memory, disk, proxies,network, and other resources. Different settings are available forconfiguration depending on whether you are using Linux containers in WSL 2mode, Linux containers in Hyper-V mode, or Windows containers.



The Advanced tab is only available in Hyper-V mode, because in WSL 2 mode and Windows container mode these resources are managed by Windows. In WSL 2 mode, you can configure limits on the memory, CPU, and swap size allocatedto the WSL 2 utility VM.

Use the Advanced tab to limit resources available to Docker.

  • CPUs: By default, Docker Desktop is set to use half the number of processorsavailable on the host machine. To increase processing power, set this to ahigher number; to decrease, lower the number.

  • Memory: By default, Docker Desktop is set to use 2 GB runtime memory,allocated from the total available memory on your machine. To increase the RAM, set this to a higher number. To decrease it, lower the number.

  • Swap: Configure swap file size as needed. The default is 1 GB.

  • Disk image size: Specify the size of the disk image.

  • Disk image location: Specify the location of the Linux volume where containers and images are stored.

You can also move the disk image to a different location. If you attempt to move a disk image to a location that already has one, you get a prompt asking if you want to use the existing image or replace it.

File sharing


The File sharing tab is only available in Hyper-V mode, because in WSL 2 mode and Windows container mode all files are automatically shared by Windows.

Use File sharing to allow local directories on Windows to be shared with Linux containers.This is especially useful forediting source code in an IDE on the host while running and testing the code in a container.Note that configuring file sharing is not necessary for Windows containers, only Linux containers. If a directory is not shared with a Linux container you may get file not found or cannot start service errors at runtime. See Volume mounting requires shared folders for Linux containers.

File share settings are:

  • Add a Directory: Click + and navigate to the directory you want to add.

  • Apply & Restart makes the directory available to containers using Docker’sbind mount (-v) feature.

Tips on shared folders, permissions, and volume mounts

  • Share only the directories that you need with the container. File sharing introduces overhead as any changes to the files on the host need to be notified to the Linux VM. Sharing too many files can lead to high CPU load and slow filesystem performance.

  • Shared folders are designed to allow application code to be edited on the host while being executed in containers. For non-code items such as cache directories or databases, the performance will be much better if they are stored in the Linux VM, using a data volume (named volume) or data container.

  • Docker Desktop sets permissions to read/write/execute for users, groups and others 0777 or a+rwx.This is not configurable. See Permissions errors on data directories for shared volumes.

  • Windows presents a case-insensitive view of the filesystem to applications while Linux is case-sensitive. On Linux it is possible to create 2 separate files: test and Test, while on Windows these filenames would actually refer to the same underlying file. This can lead to problems where an app works correctly on a developer Windows machine (where the file contents are shared) but fails when run in Linux in production (where the file contents are distinct). To avoid this, Docker Desktop insists that all shared files are accessed as their original case. Therefore if a file is created called test, it must be opened as test. Attempts to open Test will fail with “No such file or directory”. Similarly once a file called test is created, attempts to create a second file called Test will fail.

Shared folders on demand

You can share a folder “on demand” the first time a particular folder is used by a container.

If you run a Docker command from a shell with a volume mount (as shown in theexample below) or kick off a Compose file that includes volume mounts, you get apopup asking if you want to share the specified folder.

You can select to Share it, in which case it is added your Docker Desktop Shared Folders list and available tocontainers. Alternatively, you can opt not to share it by selecting Cancel.


Docker Desktop lets you configure HTTP/HTTPS Proxy Settings andautomatically propagates these to Docker. For example, if you set your proxysettings to, Docker uses this proxy when pulling containers.

Your proxy settings, however, will not be propagated into the containers you start.If you wish to set the proxy settings for your containers, you need to defineenvironment variables for them, just like you would do on Linux, for example:

For more information on setting environment variables for running containers,see Set environment variables.



The Network tab is not available in Windows container mode because networking is managed by Windows.

You can configure Docker Desktop networking to work on a virtual private network (VPN). Specify a network address translation (NAT) prefix and subnet mask to enable Internet connectivity.

DNS Server: You can configure the DNS server to use dynamic or static IP addressing.


Some users reported problems connecting to Docker Hub on Docker Desktop. This would manifest as an error when trying to rundocker commands that pull images from Docker Hub that are not alreadydownloaded, such as a first time run of docker run hello-world. If youencounter this, reset the DNS server to use the Google DNS fixed address: For more information, seeNetworking issues in Troubleshooting.

Updating these settings requires a reconfiguration and reboot of the Linux VM.

WSL Integration

In WSL 2 mode, you can configure which WSL 2 distributions will have the Docker WSL integration.

By default, the integration will be enabled on your default WSL distribution. To change your default WSL distro, run wsl --set-default <distro name>. (For example, to set Ubuntu as your default WSL distro, run wsl --set-default ubuntu).

You can also select any additional distributions you would like to enable the WSL 2 integration on.

For more details on configuring Docker Desktop to use WSL 2, see Docker Desktop WSL 2 backend.

Docker Engine

The Docker Engine page allows you to configure the Docker daemon to determine how your containers run.

Type a JSON configuration file in the box to configure the daemon settings. For a full list of options, see the Docker Enginedockerd commandline reference.

Click Apply & Restart to save your settings and restart Docker Desktop.

Command Line

On the Command Line page, you can specify whether or not to enable experimental features.

You can toggle the experimental features on and off in Docker Desktop. If you toggle the experimental features off, Docker Desktop uses the current generally available release of Docker Engine.

Experimental features

Experimental features provide early access to future product functionality.These features are intended for testing and feedback only as they may changebetween releases without warning or can be removed entirely from a futurerelease. Experimental features must not be used in production environments.Docker does not offer support for experimental features.

For a list of current experimental features in the Docker CLI, see Docker CLI Experimental features.

Run docker version to verify whether you have enabled experimental features. Experimental modeis listed under Server data. If Experimental is true, then Docker isrunning in experimental mode, as shown here:



The Kubernetes tab is not available in Windows container mode.

Docker Desktop includes a standalone Kubernetes server that runs on your Windows machine, sothat you can test deploying your Docker workloads on Kubernetes. To enable Kubernetes support and install a standalone instance of Kubernetes running as a Docker container, select Enable Kubernetes.

For more information about using the Kubernetes integration with Docker Desktop, see Deploy on Kubernetes.

Software Updates

The Software Updates section notifies you of any updates available to Docker Desktop. You can choose to download the update right away, or click the Release Notes option to learn what’s included in the updated version.

If you are on a Docker Team or a Business subscription, you can turn off the check for updates by clearing the Automatically Check for Updates checkbox in the General settings. This will also disable the notification badge that appears on the Docker Dashboard.


The Restart Docker Desktop and Reset to factory defaults options are now available on the Troubleshoot menu. For information, see Logs and Troubleshooting.


Visit our Logs and Troubleshooting guide for more details.

Log on to our Docker Desktop for Windows forum to get help from the community, review current user topics, or join a discussion.

Log on to Docker Desktop for Windows issues on GitHub to report bugs or problems and review community reported issues.

For information about providing feedback on the documentation or update it yourself, see Contribute to documentation.

Switch between Windows and Linux containers

From the Docker Desktop menu, you can toggle which daemon (Linux or Windows)the Docker CLI talks to. Select Switch to Windows containers to use Windowscontainers, or select Switch to Linux containers to use Linux containers(the default).

For more information on Windows containers, refer to the following documentation:

  • Microsoft documentation on Windows containers.

  • Build and Run Your First Windows Server Container (Blog Post)gives a quick tour of how to build and run native Docker Windows containers on Windows 10 and Windows Server 2016 evaluation releases.

  • Getting Started with Windows Containers (Lab)shows you how to use the MusicStoreapplication with Windows containers. The MusicStore is a standard .NET application and,forked here to use containers, is a good example of a multi-container application.

  • To understand how to connect to Windows containers from the local host, seeI want to connect to a container from Windows

Settings dialog changes with Windows containers

When you switch to Windows containers, the Settings dialog only shows those tabs that are active and apply to your Windows containers:

If you set proxies or daemon configuration in Windows containers mode, theseapply only on Windows containers. If you switch back to Linux containers,proxies and daemon configurations return to what you had set for Linuxcontainers. Your Windows container settings are retained and become availableagain when you switch back.


The Docker Desktop Dashboard enables you to interact with containers and applications and manage the lifecycle of your applications directly from your machine. The Dashboard UI shows all running, stopped, and started containers with their state. It provides an intuitive interface to perform common actions to inspect and manage containers and Docker Compose applications. For more information, see Docker Desktop Dashboard.

Docker Hub

Select Sign in /Create Docker ID from the Docker Desktop menu to access your Docker Hub account. Once logged in, you can access your Docker Hub repositories directly from the Docker Desktop menu.

For more information, refer to the following Docker Hub topics:

Two-factor authentication

Docker Desktop enables you to sign into Docker Hub using two-factor authentication. Two-factor authentication provides an extra layer of security when accessing your Docker Hub account.

You must enable two-factor authentication in Docker Hub before signing into your Docker Hub account through Docker Desktop. For instructions, see Enable two-factor authentication for Docker Hub.

After you have enabled two-factor authentication:

  1. Go to the Docker Desktop menu and then select Sign in / Create Docker ID.

  2. Enter your Docker ID and password and click Sign in.

  3. After you have successfully signed in, Docker Desktop prompts you to enter the authentication code. Enter the six-digit code from your phone and then click Verify.

After you have successfully authenticated, you can access your organizations and repositories directly from the Docker Desktop menu.

Adding TLS certificates

You can add trusted Certificate Authorities (CAs) to your Docker daemon to verify registry server certificates, and client certificates, to authenticate to registries.

How do I add custom CA certificates?

Docker Desktop supports all trusted Certificate Authorities (CAs) (root orintermediate). Docker recognizes certs stored under Trust RootCertification Authorities or Intermediate Certification Authorities.

Docker Desktop creates a certificate bundle of all user-trusted CAs based onthe Windows certificate store, and appends it to Moby trusted certificates. Therefore, if an enterprise SSL certificate is trusted by the user on the host, it is trusted by Docker Desktop.

To learn more about how to install a CA root certificate for the registry, seeVerify repository client with certificatesin the Docker Engine topics.

How do I add client certificates?

You can add your client certificatesin ~/.docker/certs.d/<MyRegistry>:<Port>/client.cert and~/.docker/certs.d/<MyRegistry>:<Port>/client.key. You do not need to push your certificates with git commands.

When the Docker Desktop application starts, it copies the~/.docker/certs.d folder on your Windows system to the /etc/docker/certs.ddirectory on Moby (the Docker Desktop virtual machine running on Hyper-V).

You need to restart Docker Desktop after making any changes to the keychainor to the ~/.docker/certs.d directory in order for the changes to take effect.

The registry cannot be listed as an insecure registry (seeDocker Daemon). Docker Desktop ignorescertificates listed under insecure registries, and does not send clientcertificates. Commands like docker run that attempt to pull from the registryproduce error messages on the command line, as well as on the registry.

To learn more about how to set the client TLS certificate for verification, seeVerify repository client with certificatesin the Docker Engine topics.

Where to go next

  • Try out the walkthrough at Get Started.

  • Dig in deeper with Docker Labs example walkthroughs and source code.

  • Refer to the Docker CLI Reference Guide.

windows, edge, tutorial, run, docker, local, machine

After updating to docker desktop v2.3.0.4 from prev version on windows 10 pro 64bit, i too faced the issue. After enabling kubernetes, it appeared stuck on starting. But it was not stuck and it came back after a considerable delay. It worked for me even though i am behind corporate proxy and using cisco anyconnect vpn too. Hypervisor enabled at Windows startup; Hyper-V. On Windows 10 Pro or Enterprise, you can also use Hyper-V with the following features enabled: Hyper-V installed and working; Virtualization enabled in the BIOS; Hypervisor enabled at Windows startup; Docker Desktop requires Hyper-V as well as the Hyper-V Module for Windows Powershell to be. Docker for Windows runs on 64-bit Windows 10 Pro, Enterprise, and Education; 1511 November update, Build 10586 or later. Docker plans to support more versions of Windows 10 in the future.

Estimated reading time: 16 minutes

Did you know that Docker Desktop now offers support for developers subscribed to a Pro or a Team plan? Click here to learn more.

This page contains information on how to diagnose and troubleshoot Docker Desktop issues, request Docker Desktop support (Pro and Team plan users only), send logs and communicate with the Docker Desktop team, use our forums and Success Center, browse and log issues on GitHub, and find workarounds for known problems.


Choose > Troubleshootfrom the menu bar to see the troubleshoot options.

The Troubleshoot page contains the following options:

  • Restart Docker Desktop: Select to restart Docker Desktop.

  • Support: Developers on Pro and Team plans can use this option to send a support request. Other users can use this option to diagnose any issues in Docker Desktop. For more information, see Diagnose and feedback and Support.

  • Reset Kubernetes cluster: Select this option to delete all stacks and Kubernetes resources. For more information, see Kubernetes.

  • Clean / Purge data: Select this option to delete container and image data. Choose whether you’d like to delete data from Hyper-V, WSL 2, or Windows Containers and then click Delete to confirm.

  • Reset to factory defaults: Choose this option to reset all options onDocker Desktop to their initial state, the same as when Docker Desktop was first installed.

Diagnose and feedback

In-app diagnostics

If you experience issues for which you do not find solutions in thisdocumentation, on Docker Desktop for Windows issues onGitHub, or the Docker Desktop for Windowsforum, we can help youtroubleshoot the log data. Before reporting an issue, we recommend that you read the information provided on this page to fix some common known issues.

  1. Choose > Troubleshootfrom the menu.
  2. Sign into Docker Desktop. In addition, ensure you are signed into your Docker account.
  3. Click Get support. This opens the in-app Support page and starts collecting the diagnostics.
  4. When the diagnostics collection process is complete, click Upload to get a Diagnostic ID.
  5. When the diagnostics have been uploaded, Docker Desktop prints a Diagnostic ID. Copy this ID.
  6. If you have subscribed to a Pro or a Team plan, click Contact Support. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied earlier to the Diagnostics ID field. Click Submit to request Docker Desktop support.


    You must be signed in to Docker Desktop using your Pro or Team plan credentials to access the support form. For information on what’s covered as part of Docker Desktop support, see Support.

  7. If you are not subscribed to a Pro or a team plan, you can click Upgrade to benefit from Docker Support to upgrade your existing account. Alternatively, click Report a Bug to open a new Docker Desktop issue on GitHub. This opens Docker Desktop for Windows on GitHub in your web browser in a ‘New issue’ template. Complete the information required and ensure you add the diagnostic ID you copied earlier. Click submit new issue to create a new issue.

Diagnosing from the terminal

On occasions it is useful to run the diagnostics yourself, for instance ifDocker Desktop for Windows cannot start.

First locate the com.docker.diagnose, that should be in C:ProgramFilesDockerDockerresourcescom.docker.diagnose.exe.

To create and upload diagnostics in Powershell, run:

After the diagnostics have finished, you should have the following output,containing your diagnostic ID:

Troubleshooting topics

Make sure certificates are set up correctly

Docker Desktop ignores certificates listed under insecure registries, anddoes not send client certificates to them. Commands like docker run thatattempt to pull from the registry produces error messages on the command line,like this:

As well as on the registry. For example:

For more about using client and server side certificates, seeHow do I add custom CA certificates?and How do I add client certificates? in theGetting Started topic.


Permissions errors on data directories for shared volumes

When sharing files from Windows, Docker Desktop sets permissions on shared volumesto a default value of 0777(read, write, execute permissions for user and for group).

The default permissions on shared volumes are not configurable. If you areworking with applications that require permissions different from the sharedvolume defaults at container runtime, you need to either use non-host-mountedvolumes or find a way to make the applications work with the default filepermissions.

See also,Can I change permissions on shared volumes for container-specific deployment requirements?in the FAQs.

Volume mounting requires shared folders for Linux containers

If you are using mounted volumes and get runtime errors indicating anapplication file is not found, access is denied to a volume mount, or a servicecannot start, such as when using Docker Compose,you might need to enable shared folders.

With the Hyper-V backend, mounting files from Windows requires shared folders for Linux containers. Click and then Settings > Shared Folders and share the folder that contains theDockerfile and volume.

Support for symlinks

Symlinks work within and across containers. To learn more, see How do symlinks work on Windows? in the FAQs.

Avoid unexpected syntax errors, use Unix style line endings for files in containers

Any file destined to run inside a container must use Unix style n lineendings. This includes files referenced at the command line for builds and inRUN commands in Docker files.

Docker containers and docker build run in a Unix environment, so files incontainers must use Unix style line endings: n, not Windows style: rn.Keep this in mind when authoring files such as shell scripts using Windowstools, where the default is likely to be Windows style line endings. Thesecommands ultimately get passed to Unix commands inside a Unix based container(for example, a shell script passed to /bin/sh). If Windows style line endingsare used, docker run fails with syntax errors.

For an example of this issue and the resolution, see this issue on GitHub:Docker RUN fails to execute shellscript.


Your machine must have the following features for Docker Desktop to function correctly.

WSL 2 and Windows Home

  1. Virtual Machine Platform
  2. Virtualization enabled in the BIOS
  3. Hypervisor enabled at Windows startup


On Windows 10 Pro or Enterprise, you can also use Hyper-V with the following features enabled:

  1. Hyper-Vinstalled and working
  2. Virtualization enabled in the BIOS
  3. Hypervisor enabled at Windows startup

Docker Desktop requires Hyper-V as well as the Hyper-V Module for WindowsPowershell to be installed and enabled. The Docker Desktop installer enablesit for you.

Docker Desktop also needs two CPU hardware features to use Hyper-V: Virtualization and Second Level Address Translation (SLAT), which is also called Rapid Virtualization Indexing (RVI). On some systems, Virtualization must be enabled in the BIOS. The steps required are vendor-specific, but typically the BIOS option is called Virtualization Technology (VTx) or something similar. Run the command systeminfo to check all required Hyper-V features. See Pre-requisites for Hyper-V on Windows 10 for more details.

To install Hyper-V manually, see Install Hyper-V on Windows 10. A reboot is required after installation. If you install Hyper-V without rebooting, Docker Desktop does not work correctly.

From the start menu, type Turn Windows features on or off and press enter.In the subsequent screen, verify that Hyper-V is enabled.

Virtualization must be enabled

In addition to Hyper-V or WSL 2, virtualization must be enabled. Check thePerformance tab on the Task Manager:

If you manually uninstall Hyper-V, WSL 2 or disable virtualization,Docker Desktop cannot start. See Unable to run Docker for Windows onWindows 10 Enterprise.

Docker Windows 10 Proxy

Hypervisor enabled at Windows startup

If you have completed the steps described above and are still experiencingDocker Desktop startup issues, this could be because the Hypervisor is installed,but not launched during Windows startup. Some tools (such as older versions of Virtual Box) and video game installers disable hypervisor on boot. To reenable it:

  1. Open an administrative console prompt.
  2. Run bcdedit /set hypervisorlaunchtype auto.
  3. Restart Windows.

You can also refer to the Microsoft TechNet article on Code flow guard (CFG) settings.

Windows containers and Windows Server

Docker Desktop is not supported on Windows Server. If you have questions about how to run Windows containers on Windows 10, seeSwitch between Windows and Linux containers.

A full tutorial is available in docker/labs onGetting Started with Windows Containers.

You can install a native Windows binary which allows you to develop and runWindows containers without Docker Desktop. However, if you install Docker this way, you cannot develop or run Linux containers. If you try to run a Linux container on the native Docker daemon, an error occurs:

Running Docker Desktop in nested virtualization scenarios

Docker Desktop can run inside a Windows 10 VM running on apps like Parallels or VMware Fusion on a Mac provided that the VM is properly configured. However, problems and intermittent failures may still occur due to the way these apps virtualize the hardware. For these reasons, Docker Desktop is not supported in nested virtualization scenarios. It might workin some cases, and not in others.

For best results, we recommend you run Docker Desktop natively on a Windows system (to work with Windows or Linux containers), or on Mac to work with Linux containers.

If you still want to use nested virtualization

  • Make sure nested virtualization support is enabled in VMWare or Parallels.Check the settings in Hardware > CPU & Memory > Advanced Options > Enablenested virtualization (the exact menu sequence might vary slightly).

  • Configure your VM with at least 2 CPUs and sufficient memory to run yourworkloads.

  • Make sure your system is more or less idle.

  • Make sure your Windows OS is up-to-date. There have been several issues withsome insider builds.

  • The processor you have may also be relevant. For example, Westmere based MacPros have some additional hardware virtualization features over Nehalem basedMac Pros and so do newer generations of Intel processors.

Typical failures we see with nested virtualization

  • Slow boot time of the Linux VM. If you look in the logs and find some entriesprefixed with Moby. On real hardware, it takes 5-10 seconds to boot theLinux VM; roughly the time between the Connected log entry and the *Starting Docker ... [ ok ] log entry. If you boot the Linux VM inside aWindows VM, this may take considerably longer. We have a timeout of 60s or so.If the VM hasn’t started by that time, we retry. If the retry fails we printan error. You can sometimes work around this by providing more resources tothe Windows VM.

  • Sometimes the VM fails to boot when Linux tries to calibrate the time stampcounter (TSC). This process is quite timing sensitive and may fail whenexecuted inside a VM which itself runs inside a VM. CPU utilization is alsolikely to be higher.

  • Ensure “PMU Virtualization” is turned off in Parallels on Macs. Check thesettings in Hardware > CPU & Memory > Advanced Settings > PMUVirtualization.

Networking issues

IPv6 is not (yet) supported on Docker Desktop.



Restart your PC to stop / discard any vestige of the daemon running from thepreviously installed version.


The DOCKER_HOST environmental variable does not need to be set. If you usebash, use the command unset ${!DOCKER_*} to unset it. For other shells,consult the shell’s documentation.

Make sure Docker is running for webserver examples

For the hello-world-nginx example and others, Docker Desktop must berunning to get to the webserver on http://localhost/. Make sure that theDocker whale is showing in the menu bar, and that you run the Docker commands ina shell that is connected to the Docker Desktop Engine. Otherwise, you might start the webserver container but get a “web pagenot available” error when you go to docker.

How to solve port already allocated errors

If you see errors like Bind for failed: port is already allocatedor listen tcp: bind: address is already in use ...

These errors are often caused by some other software on Windows using thoseports. To discover the identity of this software, either use the resmon.exeGUI and click “Network” and then “Listening Ports” or in a Powershell usenetstat -aon find /i 'listening ' to discover the PID of the processcurrently using the port (the PID is the number in the rightmost column). Decidewhether to shut the other process down, or to use a different port in yourdocker app.

Docker Desktop fails to start when anti-virus software is installed

Some anti-virus software may be incompatible with Hyper-V and MicrosoftWindows 10 builds. The conflicttypically occurs after a Windows update andmanifests as an error response from the Docker daemon and a Docker Desktop start failure.

For a temporary workaround, uninstall the anti-virus software, orexplore other workarounds suggested on Docker Desktop forums.

Docker On Windows 10 Pro


Docker Desktop offers support for developers subscribed to a Pro or a Team plan. Click here to upgrade your existing account.

Windows 10 Pro Docker Download

This section contains instructions on how to get support, and covers the scope of Docker Desktop support.

How do I get Docker Desktop support?

If you have subscribed to a Pro and Team account, please raise a ticket through Docker Desktop support.

Docker Community users can get support through our Github repos for-win and for-mac, where we respond on a best-effort basis.

What support can I get?

If you are a Pro or a Team user, you can request for support on the following types of issues:

  • Desktop upgrade issues
  • Desktop installation issues
    • Enabling virtualization in BIOS
    • Enabling Windows features
    • Installation crashes
    • Failure to launch Docker Desktop on first run
  • Usage issues
    • Crash closing software
    • Docker Desktop not behaving as expected
  • Configuration issues
  • Basic product ‘how to’ questions such as ‘how to work efficiently on WSL 2’

Docker Toolbox On Windows 10 Pro

What is not supported?

Docker Desktop excludes support for the following types of issues:

  • Use on or in conjunction with hardware or software other than that specified in the applicable documentation
  • Running on unsupported operating systems, including beta/preview versions of operating systems
  • Support for the Docker engine, Docker CLI, or other bundled Linux components
  • Support for Kubernetes
  • Features labeled as experimental
  • System/Server administration activities
  • Supporting Desktop as a production runtime
  • Scale deployment/multi-machine installation of Desktop
  • Routine product maintenance (data backup, cleaning disk space and configuring log rotation)
  • Third-party applications not provided by Docker
  • Altered or modified Docker software
  • Defects in the Docker software due to hardware malfunction, abuse, or improper use
  • Any version of the Docker software other than the latest version
  • Reimbursing and expenses spent for third-party services not provided by Docker
  • Docker Support excludes training, customization, and integration

What versions are supported?

Docker Requires Windows 10 Pro Or Enterprise

We currently only offer support for the latest version of Docker Desktop. If you are running an older version, you may be asked to upgrade before we investigate your support request.

How many machines can I get support for Docker Desktop on?

As a Pro user you can get support for Docker Desktop on a single machine.As a Team, you can get support for Docker Desktop for the number of machines equal to the number of seats as part of your plan.

What OS’s are supported?

Docker Desktop is available for Mac and Windows. The supported version information can be found on the following pages:

Can I run Docker Desktop on Virtualized hardware?

Windows 10 Pro Docker Software

No, currently this is unsupported and against the terms of use.

Docker Windows 10 Pro Error

Install Docker On Windows 10 Pro

windows, troubleshooting, logs, issues
Comments are closed.