| description | keywords | title |
|---|---|---|
Frequently asked questions |
windows faqs |
Frequently asked questions (FAQ) |
A. You can download the Stable version of Docker Desktop from Docker Hub. To download the Edge version, see the Edge release notes.
For installation instructions, see Install Docker Desktop on Windows{: target="blank" class=""}.
Two different download channels are available in the Community version of Docker Desktop:
The Stable channel provides a general availability release-ready installer for a fully baked and tested, more reliable app. The Stable version of Docker Desktop includes the latest released version of Docker Engine. The release schedule is synced with Docker Engine releases and patch releases. On the Stable channel, you can select whether to send usage statistics and other data.
The Edge channel provides an installer with new features we are working on, but is not necessarily fully tested. It includes the experimental version of Docker Engine. Bugs, crashes, and issues can occur when using the Edge version, but you get a chance to preview new functionality, experiment, and provide feedback as Docker Desktop evolves. Edge releases are typically more frequent than for Stable, often one or more per month. Usage statistics and crash reports are sent by default. You do not have the option to disable this on the Edge channel.
Yes, you can switch between Stable and Edge versions. You can try out the Edge releases to see what's new, then go back to Stable for other work. However, you can only have one version of Docker Desktop installed at a time. For more information, see Switch between Stable and Edge versions.
For information about system requirements, see Docker Desktop Windows system requirements.
{% include experimental.md %}
You might need to provide the location of the Engine API for Docker clients and development tools.
On Docker Desktop, clients can connect to the Docker Engine through a
named pipe: npipe:////./pipe/docker_engine, or TCP socket at this URL:
tcp://localhost:2375.
This sets DOCKER_HOST and DOCKER_CERT_PATH environment variables to the
given values (for the named pipe or TCP socket, whichever you use).
See also Docker Engine API and the Docker Desktop for Windows forums topic How to find the remote API{: target="blank" class=""}.
Windows has a changing IP address (or none if you have no network access). We recommend that you connect to the special DNS name host.docker.internal, which resolves to the internal IP address used by the host. This is for development purposes and will not work in a production environment outside of Docker Desktop for Windows.
The gateway is also reachable as gateway.docker.internal.
For more information about the networking features in Docker Desktop for Windows, see Networking.
We recommend that you publish a port, or connect from another container. You can use the same method on Linux if the container is on an overlay network and not a bridge network, as these are not routed.
For more information and examples, see I want to connect to a container from Windows in the Networking topic.
No, at this point, Docker Desktop does not enable you to control (chmod)
the Unix-style permissions on shared volumes for
deployed containers, but rather sets permissions to a default value of
0777{: target="blank" class=""}
(read, write, execute permissions for user and for
group) which is not configurable.
For workarounds and to learn more, see Permissions errors on data directories for shared volumes.
Docker Desktop supports symbolic links (symlinks) created within containers. Symlinks resolve within and across containers. Symlinks created outside of Docker do not work.
To learn more about the reasons for this limitation, see the following discussions:
-
GitHub issue: Symlinks don't work as expected{: target="blank" class=""}
-
Docker Desktop for Windows forums topic: Symlinks on shared volumes not supported{: target="blank" class=""}
Docker Desktop supports all trusted Certificate Authorities (CAs) (root or intermediate). Docker recognizes certs stored under Trust Root Certification Authorities or Intermediate Certification Authorities.
For more information on adding server and client side certs, see Add TLS certificates in the Getting Started topic.
For information on adding client certificates, see Add TLS certificates in the Getting Started topic.
Unfortunately, it is not possible to pass through a USB device (or a serial port) to a container as it requires support at the hypervisor level.
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 work in some cases, and not in others. For more information, see Running Docker Desktop in nested virtualization scenarios.
Unfortunately, VirtualBox (and other hypervisors like VMWare) cannot run when Hyper-V is enabled on Windows.
You can find a tutorial about running Windows containers on Windows Server in Getting Started with Windows Containers{: target="blank" class=""}.
Docker Desktop requires the Hyper-V feature which is not available in the Windows Home edition.
Docker Desktop uses the Windows Hyper-V features. While older Windows versions have Hyper-V, their Hyper-V implementations lack features critical for Docker Desktop to work.
Some anti-virus software may be incompatible with Hyper-V and Windows 10 builds which impact Docker Desktop. For more information, see Docker Desktop fails to start when anti-virus software is installed in Troubleshooting.
Everything is fair game. We'd like your impressions on the download and install process, startup, functionality available, the GUI, usefulness of the app, command line integration, and so on. Tell us about problems, what you like, or functionality you'd like to see added.
You can find information about diagnosing and troubleshooting common issues in the Logs and Troubleshooting topic.
If you do not find a solution in Troubleshooting, browse issues on Docker Desktop for Windows issues on GitHub{: target="blank" class=""} or create a new one. You can also create new issues based on diagnostics. To learn more, see Diagnose problems, send feedback, and create GitHub issues.
The Docker Desktop for Windows forum{: target="blank" class=""} contains discussion threads. You can also create discussion topics there, but we recommend using the GitHub issues over the forums for better tracking and response.
If you do not want to send usage data, use the Stable channel. For more information, see What is the difference between the Stable and Edge versions of Docker Desktop.
When uploading diagnostics to help Docker with investigating issues, the uploaded diagnostics bundle may contain personal data such as usernames and IP addresses. The diagnostics bundles are only accessible to Docker, Inc. employees who are directly involved in diagnosing Docker Desktop issues.
By default, Docker, Inc. will delete uploaded diagnostics bundles after 30 days unless they are referenced in an open issue on the docker/for-mac or docker/for-win issue trackers. If an issue is closed, Docker, Inc. will remove the referenced diagnostics bundles within 30 days. You may also request the removal of a diagnostics bundle by either specifying the diagnostics ID or through your GitHub ID (if the diagnostics ID is mentioned in a GitHub issue). Docker, Inc. will only use the data in the diagnostics bundle to investigate specific user issues, but may derive high-level (non-personal) metrics such as the rate of issues from it.