| description | keywords | redirect_from | title | |
|---|---|---|---|---|
Frequently asked questions |
mac faqs |
|
Frequently asked questions (FAQ) |
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.
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.
New releases will be available roughly monthly, similar to Edge today, unless there are critical fixes that need to be released sooner.
Previously you had to manage this yourself: now it will happen automatically as a side effect of all users being on the latest version.
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.
Starting with Docker Desktop 3.0.0, Stable and Edge releases are combined into a single, cumulative release stream for all users.
Docker.app is Docker Desktop on Mac. It bundles the Docker client and Docker Engine. Docker.app uses the macOS Hypervisor.framework to run containers, which means that a separate VirtualBox is not required to run Docker Desktop.
You need a Mac that supports hardware virtualization. For more information, see Docker Desktop Mac system requirements.
At the moment, Docker Desktop is compatible with Intel processors only. You can follow the status of Apple Silicon support in our roadmap{:target="blank" rel="noopener" class=""}.
{% 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 Unix
socket: unix:///var/run/docker.sock.
See also Docker Engine API and Docker Desktop for Mac forums topic Using pycharm Docker plugin{: target="blank" rel="noopener" class=""}.
If you are working with applications like Apache Maven{: target="blank" rel="noopener" class=""}
that expect settings for DOCKER_HOST and DOCKER_CERT_PATH environment
variables, specify these to connect to Docker instances through Unix sockets.
For example:
export DOCKER_HOST=unix:///var/run/docker.sockMac has a changing IP address (or none if you have no network access). We recommend that you attach an unused IP to the lo0 interface on the
Mac so that containers can connect to this address.
For more information and examples, see I want to connect from a container to a service on the host in the Networking topic.
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 the Mac in the Networking topic.
Docker Desktop supports all trusted certificate authorities (CAs) (root or intermediate). 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 client 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.
HyperKit is a hypervisor built on top of the Hypervisor.framework in macOS. It runs entirely in userspace and has no other dependencies.
We use HyperKit to eliminate the need for other VM products, such as Oracle VirtualBox or VMWare Fusion.
HyperKit is thinner than VirtualBox and VMWare fusion, and the version we include is customized for Docker workloads on Mac.
The privileged helper process com.docker.vmnetd is started by launchd and
runs in the background. The process does not consume any resources unless
Docker.app connects to it, so it's safe to ignore.
Everything is fair game. We'd like your impressions on the download-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 Mac issues on GitHub{: target="blank" rel="noopener" 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 Mac forum{: target="blank" rel="noopener" class=""} provides discussion threads as well, and you can 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 the usage data, go to Preferences > General and then clear the Send usage statistics box.
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 via 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.