Frequently asked questions (FAQ)

Estimated reading time: 9 minutes

Docker Desktop releases

When will Docker Desktop move to a cumulative release stream?

Starting with version 3.0.0, Docker Desktop will be available as a single, cumulative release stream. This is the same version for both Stable and Edge users. The next release after Docker Desktop 3.0.0 will be the first to be applied as a delta update. For more information, see Automatic updates.

How do new users install Docker Desktop?

Each Docker Desktop release will also be delivered as a full installer for new users. The same will apply if you have skipped a version, although this will not normally happen as updates will be applied automatically.

How frequent will new releases be?

New releases will be available roughly monthly, similar to Edge today, unless there are critical fixes that need to be released sooner.

How do I ensure that all users on my team are using the same version?

Previously you had to manage this yourself: now it will happen automatically as a side effect of all users being on the latest version.

My colleague has got a new version but I haven’t got it yet.

Sometimes we may roll out a new version gradually over a few days. Therefore, if you wait, it will turn up soon. Alternatively, you can select Check for Updates from the Docker menu to jump the queue and get the latest version immediately.

Where can I find information about Stable and Edge releases?

Starting with Docker Desktop 3.0.0, Stable and Edge releases are combined into a single, cumulative release stream for all users.

What are the system requirements for Docker Desktop?

For information about system requirements, see Docker Desktop Windows system requirements.

What is an experimental feature?

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

To enable experimental features in the Docker CLI, edit the config.json file and set experimental to enabled.

To enable experimental features from the Docker Desktop menu, click Settings (Preferences on macOS) > Command Line and then turn on the Enable experimental features toggle. Click Apply & Restart.

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

How do I?

How do I connect to the remote Docker Engine API?

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.

How do I connect from a container to a service on the host?

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.

How do I connect to a container from Windows?

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.

Volumes

Can I change permissions on shared volumes for container-specific deployment requirements?

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 (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.

How do symlinks work on Windows?

Docker Desktop supports 2 kinds of symlink:

1. Windows native symlinks: these are visible inside containers as symlinks.
2. Symlinks created inside a container: these are represented as mfsymlinks i.e. regular Windows files with special metadata. These appear as symlinks inside containers but not as symlinks on the host.

Certificates

How do I add custom CA certificates?

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 Adding TLS certificates in the Getting Started topic.

How do I add client certificates?

For information on adding client certificates, see Adding TLS certificates in the Getting Started topic.

Can I pass through a USB device to a container?

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.

Can I run 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 work in some cases, and not in others. For more information, see Running Docker Desktop in nested virtualization scenarios.

Can I use VirtualBox alongside Docker Desktop?

Yes, you can run VirtualBox along with Docker Desktop if you have enabled the Windows Hypervisor Platform feature on your machine.

Windows requirements

Can I run Docker Desktop on Windows Server?

No, running Docker Desktop on Windows Server is not supported.

How do I run Windows containers on Windows Server?

You can install a native Windows binary which allows you to develop and run Windows containers without Docker Desktop. For more information, see the tutorial about running Windows containers on Windows Server in Getting Started with Windows Containers.

Can I install Docker Desktop on Windows 10 Home?

Windows 10 Home, version 2004 users can now install Docker Desktop Stable 2.3.0.2 or a later release with the WSL 2 backend.

Docker Desktop Stable releases require the Hyper-V feature which is not available in the Windows 10 Home edition.

Why is Windows 10 required?

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.

Why does Docker Desktop fail to start when anti-virus software is installed?

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.

Feedback

What kind of feedback are we looking for?

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.

What if I have problems or questions?

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 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 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.

How can I opt out of sending my usage data?

If you do not want to send the usage data, from the Docker menu, go to Settings > General and then clear the Send usage statistics box.

How is personal data handled in 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.