Frequently asked questions
What are the system requirements for Docker Desktop?
For information about Docker Desktop system requirements, see:
Where does Docker Desktop get installed on my machine?
By default, Docker Desktop is installed at the following location:
- On Mac:
- On Windows:
- On Linux:
Where can I find the checksums for the download files?
You can find the checksums on the release notes page.
Do I need to pay to use Docker Desktop?
Docker Desktop is free for small businesses (fewer than 250 employees AND less than $10 million in annual revenue), personal use, education, and non-commercial open-source projects. Otherwise, it requires a paid subscription for professional use. Paid subscriptions are also required for government entities. When downloading and installing Docker Desktop, you are asked to agree to the Docker Subscription Service Agreement.
Do I need to pay to create or share Docker Extensions?
No, the Docker Extension SDK is licensed under the Apache 2.0 License and is free to use. Anyone can create new Docker Extensions and share them without constraints.
Do I need to use a specific license when I create a Docker Extension?
No, there is no constraint on how each extension should be licensed, this is up to the extension authors to decide when creating a new extension.
Can I use Docker Desktop offline?
Yes, you can use Docker Desktop offline. However, you cannot access features that require an active internet connection. Additionally, any functionality that requires you to sign won’t work while using Docker Desktop offline or in air-gapped environments. This includes:
- The in-app Quick Start Guide
- Pulling or pushing an image to Docker Hub
- Image Access Management
- Vulnerability scanning
- Viewing remote images in the Docker Dashboard
- Settting up Dev Environments
- Docker build when using BuildKit.
You can work around this by disabling BuildKit. Run
DOCKER_BUILDKIT=0 docker build .to disable BuildKit.
- Deploying an app to the cloud through Compose ACI and ECS integrations
- Kubernetes (Images are download when you enable Kubernetes for the first time)
- Check for updates
- In-app diagnostics (including the Self-diagnose tool)
- Tip of the week
- Sending usage statistics
Where can I find information about diagnosing and troubleshooting Docker Desktop issues?
You can find information about diagnosing and troubleshooting common issues in the Troubleshooting topic.
If you do not find a solution in troubleshooting, browse the Github repositories or create a new issue:
How do I connect to the remote Docker Engine API?
To connect to the remote Engine API, you might need to provide the location of the Engine API for Docker clients and development tools.
Mac and Windows WSL 2 users can connect to the Docker Engine through a Unix socket:
If you are working with applications like Apache Maven
that expect settings for
variables, specify these to connect to Docker instances through Unix sockets.
$ export DOCKER_HOST=unix:///var/run/docker.sock
Docker Desktop Windows users can connect to the Docker Engine through a named pipe:
npipe:////./pipe/docker_engine, or TCP socket at this URL:
For details, see Docker Engine API.
How do I connect from a container to a service on the host?
Mac, Linux, and Windows have a changing IP address (or none if you have no network access). On both Mac and Windows, 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 does not work in a production environment outside of Docker Desktop.
For more information and examples, see how to connect from a container to a service on the host.
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?
In general, Docker recommends running Docker Desktop natively on either Mac, Linux, or Windows. However, Docker Desktop for Windows can run inside a virtual desktop provided the virtual desktop is properly configured. For more information, see Run Docker Desktop in a VM or VDI environment
Docker Desktop’s UI appears green, distorted, or has visual artifacts. How do I fix this?
Docker Desktop uses hardware-accelerated graphics by default, which may cause problems for some GPUs. In such cases, Docker Desktop will launch successfully, but some screens may appear green, distorted, or have some visual artifacts.
To work around this issue, disable hardware acceleration by creating a
"disableHardwareAcceleration": true entry in Docker Desktop’s
settings.json file. You can find this file at:
After updating the
settings.json file, close and restart Docker Desktop to apply the changes.
Can I run Docker Desktop on Virtualized hardware?
How do new users install Docker Desktop?
Each Docker Desktop release is also delivered as a full installer for new users. The same applies if you have skipped a version, although this doesn’t normally happen as updates are applied automatically.
How frequent will new releases be?
New releases are available roughly monthly, 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 happens 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.