mirror of
https://github.com/docker/docs.git
synced 2026-10-28 07:15:09 +03:00
@@ -6,23 +6,6 @@ title: Compose FAQs
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
### How do I get help?
|
||||
|
||||
Docker Compose is under active development. If you need help, would like to
|
||||
contribute, or simply want to talk about the project with like-minded
|
||||
individuals, we have a number of open channels for communication.
|
||||
|
||||
- To report bugs or file feature requests, use the [issue tracker on Github](https://github.com/docker/compose/issues).
|
||||
|
||||
- To talk about the project with people in real time, join the
|
||||
`#docker-compose` channel on the [Docker Community Slack](https://dockr.ly/slack).
|
||||
|
||||
- To contribute code submit a [pull request on Github](https://github.com/docker/compose/pulls).
|
||||
|
||||
### Where can I find example Compose files?
|
||||
|
||||
There are [many examples of Compose files on GitHub](https://github.com/docker/awesome-compose).
|
||||
|
||||
### What is the difference between `docker compose` and `docker-compose`
|
||||
|
||||
Version one of the Docker Compose command-line binary was first released in 2014. It was written in Python, and is invoked with `docker-compose`. Typically, Compose V1 projects include a top-level version element in the compose.yml file, with values ranging from 2.0 to 3.8, which refer to the specific file formats.
|
||||
@@ -91,10 +74,6 @@ system (like [s6](https://skarnet.org/software/s6/)) or a signal proxy (like
|
||||
[tini](https://github.com/krallin/tini)). Either of these wrappers takes care of
|
||||
handling `SIGTERM` properly.
|
||||
|
||||
### Can I control service startup order?
|
||||
|
||||
Yes, see [Controlling startup order](startup-order.md).
|
||||
|
||||
### How do I run multiple copies of a Compose file on the same host?
|
||||
|
||||
Compose uses the project name to create unique identifiers for all of a
|
||||
|
||||
21
content/compose/feedback.md
Normal file
21
content/compose/feedback.md
Normal file
@@ -0,0 +1,21 @@
|
||||
---
|
||||
description: Find a way to provide feedback on Docker Compose that's right for you
|
||||
keywords: Feedback, Docker Compose, Community forum, bugs, problems, issues
|
||||
title: Give feedback
|
||||
---
|
||||
|
||||
There are many ways you can provide feedback on Docker Compose.
|
||||
|
||||
### In-product feedback
|
||||
|
||||
If you have obtained Docker Compose through Docker Desktop, you can use the `docker feedback` command to submit feedback directly from the command line.
|
||||
|
||||
<script async id="asciicast-KkC0fFrhV8nAzvXUGqay06UXx" src="https://asciinema.org/a/KkC0fFrhV8nAzvXUGqay06UXx.js"></script>
|
||||
|
||||
### Report bugs or problems on GitHub
|
||||
|
||||
To report bugs or problems, visit [Docker Compose on GitHub](https://github.com/docker/compose/issues)
|
||||
|
||||
### Feedback via Community Slack channels
|
||||
|
||||
You can also provide feedback through the #docker-compse [Docker Community Slack](https://dockr.ly/comm-slack) channel.
|
||||
@@ -11,6 +11,12 @@ There are two main parts to creating a Docker Extension:
|
||||
1. Build the foundations
|
||||
2. Publish the extension
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> You do not need to pay to create a Docker Extension. The [Docker Extension SDK](https://www.npmjs.com/package/@docker/extension-api-client) is licensed under the Apache 2.0 License and is free to use. Anyone can create new Docker Extensions and share them without constraints.
|
||||
>
|
||||
> There is also no constraint on how each extension should be licensed, this is up to you to decide when creating a new extension.
|
||||
|
||||
## Part one: Build the foundations
|
||||
|
||||
The build process consists of:
|
||||
|
||||
@@ -9,36 +9,6 @@ aliases:
|
||||
- /desktop/faqs/
|
||||
---
|
||||
|
||||
### What are the system requirements for Docker Desktop?
|
||||
|
||||
For information about Docker Desktop system requirements, see:
|
||||
|
||||
- [Mac system requirements](../install/mac-install.md#system-requirements)
|
||||
- [Windows system requirements](../install/windows-install.md#system-requirements)
|
||||
- [Linux system requirements](../install/linux-install.md#system-requirements)
|
||||
|
||||
### Where does Docker Desktop get installed on my machine?
|
||||
|
||||
By default, Docker Desktop is installed at the following location:
|
||||
|
||||
- On Mac: `/Applications/Docker.app`
|
||||
- On Windows: `C:\Program Files\Docker\Docker`
|
||||
- On Linux: `/opt/docker-desktop`
|
||||
|
||||
### 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](https://www.docker.com/legal/docker-subscription-service-agreement).
|
||||
|
||||
Read the [Blog](https://www.docker.com/blog/updating-product-subscriptions/) and [FAQs](https://www.docker.com/pricing/faq) to learn more.
|
||||
|
||||
### Do I need to pay to create or share Docker Extensions?
|
||||
|
||||
No, the [Docker Extension SDK](https://www.npmjs.com/package/@docker/extension-api-client) 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
|
||||
@@ -59,16 +29,6 @@ This includes:
|
||||
- [In-app diagnostics](../troubleshoot/overview.md#diagnose-from-the-app) (including the [Self-diagnose tool](../troubleshoot/overview.md#diagnose-from-the-app))
|
||||
- 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](../troubleshoot/overview.md).
|
||||
|
||||
If you do not find a solution in troubleshooting, browse the GitHub repositories or create a new issue:
|
||||
|
||||
- [docker/for-mac](https://github.com/docker/for-mac/issues)
|
||||
- [docker/for-win](https://github.com/docker/for-win/issues)
|
||||
- [docker/for-linux](https://github.com/docker/for-linux/issues)
|
||||
|
||||
### 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.
|
||||
@@ -102,25 +62,3 @@ For more information and examples, see [how to connect from a container to a ser
|
||||
|
||||
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](../vm-vdi.md)
|
||||
|
||||
### 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:
|
||||
|
||||
- Mac: `~/Library/Group Containers/group.com.docker/settings.json`
|
||||
- Windows: `C:\Users\[USERNAME]\AppData\Roaming\Docker\settings.json`
|
||||
- Linux: `~/.docker/desktop/settings.json.`
|
||||
|
||||
After updating the `settings.json` file, close and restart Docker Desktop to apply the changes.
|
||||
|
||||
### Can I run Docker Desktop on Virtualized hardware?
|
||||
|
||||
Yes, see section [Run Docker Desktop for Windows in a VM or VDI environment](../vm-vdi.md) for more information on how to do this.
|
||||
|
||||
@@ -6,88 +6,6 @@ aliases:
|
||||
- /desktop/linux/space/
|
||||
---
|
||||
|
||||
### What is the difference between Docker Desktop for Linux and Docker Engine?
|
||||
|
||||
Docker Desktop for Linux provides a user-friendly graphical interface that simplifies the management of containers and services. It includes Docker Engine as this is the core technology that powers Docker containers. Docker Desktop for Linux also comes with additional features like Docker Scout and Docker Extensions.
|
||||
|
||||
### Can I have both Docker Desktop for Linux and Docker Engine installed on my machine?
|
||||
|
||||
Docker Desktop for Linux and Docker Engine can be installed side-by-side on the
|
||||
same machine. Docker Desktop for Linux stores containers and images in an isolated
|
||||
storage location within a VM and offers
|
||||
controls to restrict [its resources](../settings/linux.md#resources). Using a dedicated storage
|
||||
location for Docker Desktop prevents it from interfering with a Docker Engine
|
||||
installation on the same machine.
|
||||
|
||||
While it's possible to run both Docker Desktop and Docker Engine simultaneously,
|
||||
there may be situations where running both at the same time can cause issues.
|
||||
For example, when mapping network ports (`-p` / `--publish`) for containers, both
|
||||
Docker Desktop and Docker Engine may attempt to reserve the same port on your
|
||||
machine, which can lead to conflicts ("port already in use").
|
||||
|
||||
We generally recommend stopping the Docker Engine while you're using Docker Desktop
|
||||
to prevent the Docker Engine from consuming resources and to prevent conflicts
|
||||
as described above.
|
||||
|
||||
Use the following command to stop the Docker Engine service:
|
||||
|
||||
```console
|
||||
$ sudo systemctl stop docker docker.socket containerd
|
||||
```
|
||||
|
||||
Depending on your installation, the Docker Engine may be configured to automatically
|
||||
start as a system service when your machine starts. Use the following command to
|
||||
disable the Docker Engine service, and to prevent it from starting automatically:
|
||||
|
||||
```console
|
||||
$ sudo systemctl disable docker docker.socket containerd
|
||||
```
|
||||
|
||||
#### How do I switch between Docker Desktop and Docker Engine?
|
||||
|
||||
|
||||
The Docker CLI can be used to interact with multiple Docker Engines. For example,
|
||||
you can use the same Docker CLI to control a local Docker Engine and to control
|
||||
a remote Docker Engine instance running in the cloud. [Docker Contexts](../../engine/context/working-with-contexts.md)
|
||||
allow you to switch between Docker Engines instances.
|
||||
|
||||
When installing Docker Desktop, a dedicated "desktop-linux" context is created to
|
||||
interact with Docker Desktop. On startup, Docker Desktop automatically sets its
|
||||
own context (`desktop-linux`) as the current context. This means that subsequent
|
||||
Docker CLI commands target Docker Desktop. On shutdown, Docker Desktop resets
|
||||
the current context to the `default` context.
|
||||
|
||||
Use the `docker context ls` command to view what contexts are available on your
|
||||
machine. The current context is indicated with an asterisk (`*`);
|
||||
|
||||
```console
|
||||
$ docker context ls
|
||||
NAME DESCRIPTION DOCKER ENDPOINT ...
|
||||
default * Current DOCKER_HOST based configuration unix:///var/run/docker.sock ...
|
||||
desktop-linux unix:///home/<user>/.docker/desktop/docker.sock ...
|
||||
```
|
||||
|
||||
If you have both Docker Desktop and Docker Engine installed on the same machine,
|
||||
you can run the `docker context use` command to switch between the Docker Desktop
|
||||
and Docker Engine contexts. For example, use the "default" context to interact
|
||||
with the Docker Engine;
|
||||
|
||||
```console
|
||||
$ docker context use default
|
||||
default
|
||||
Current context is now "default"
|
||||
```
|
||||
|
||||
And use the `desktop-linux` context to interact with Docker Desktop:
|
||||
|
||||
```console
|
||||
$ docker context use desktop-linux
|
||||
desktop-linux
|
||||
Current context is now "desktop-linux"
|
||||
```
|
||||
|
||||
Refer to the [Docker Context documentation](../../engine/context/working-with-contexts.md) for more details.
|
||||
|
||||
### Why does Docker Desktop for Linux run a VM?
|
||||
|
||||
Docker Desktop for Linux runs a Virtual Machine (VM) for the following reasons:
|
||||
|
||||
@@ -7,10 +7,6 @@ aliases:
|
||||
- /docker-for-mac/space/
|
||||
---
|
||||
|
||||
### What is Docker.app?
|
||||
|
||||
`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.
|
||||
|
||||
### What is HyperKit?
|
||||
|
||||
HyperKit is a hypervisor built on top of the Hypervisor.framework in macOS. It runs entirely in userspace and has no other dependencies.
|
||||
|
||||
@@ -4,14 +4,6 @@ keywords: desktop, mac, windows, faqs
|
||||
title: FAQs on Docker Desktop releases
|
||||
---
|
||||
|
||||
### Where can I find the checksums for the download files?
|
||||
|
||||
You can find the checksums on the [release notes](../release-notes.md) page.
|
||||
|
||||
### 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 every month, unless there are critical fixes that need to be released sooner.
|
||||
@@ -23,7 +15,3 @@ Previously you had to manage this yourself. Now, it happens automatically as a s
|
||||
### 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.
|
||||
@@ -12,27 +12,10 @@ Yes, you can run VirtualBox along with Docker Desktop if you have enabled the [W
|
||||
|
||||
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.
|
||||
|
||||
### Can I install Docker Desktop on Windows 10 Home?
|
||||
|
||||
If you are running Windows 10 Home (starting with build 19045), you can install [Docker Desktop for Windows](https://hub.docker.com/editions/community/docker-ce-desktop-windows/) with the [WSL 2 backend](../wsl/index.md).
|
||||
|
||||
### Can I run Docker Desktop on Windows Server?
|
||||
|
||||
No, running Docker Desktop on Windows Server is not supported.
|
||||
|
||||
### Why do I see the `Docker Desktop Access Denied` error message when I try to start Docker Desktop?
|
||||
|
||||
Docker Desktop displays the **Docker Desktop - Access Denied** error if a Windows user is not part of the **docker-users** group.
|
||||
|
||||
If your admin account is different to your user account, add the **docker-users** group. Run **Computer Management** as an administrator and navigate to **Local Users* and Groups** > **Groups** > **docker-users**.
|
||||
|
||||
Right-click to add the user to the group. Sign out and sign back in for the changes to take effect.
|
||||
|
||||
### 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](../troubleshoot/workarounds.md#docker-desktop-fails-to-start-when-anti-virus-software-is-installed).
|
||||
|
||||
### Can I change permissions on shared volumes for container-specific deployment requirements?
|
||||
|
||||
Docker Desktop does not enable you to control (`chmod`)
|
||||
@@ -94,38 +77,3 @@ To learn more about how to set the client TLS certificate for verification, see
|
||||
[Verify repository client with certificates](../../engine/security/certificates.md)
|
||||
in the Docker Engine topics.
|
||||
|
||||
### How do I 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 Windows
|
||||
containers, 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](https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/index).
|
||||
|
||||
- [Build and Run Your First Windows Server Container (Blog Post)](https://blog.docker.com/2016/09/build-your-first-docker-windows-server-container/)
|
||||
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)](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md)
|
||||
shows you how to use the [MusicStore](https://github.com/aspnet/MusicStore/)
|
||||
application with Windows containers. The MusicStore is a standard .NET application and,
|
||||
[forked here to use containers](https://github.com/friism/MusicStore), is a good example of a multi-container application.
|
||||
|
||||
- To understand how to connect to Windows containers from the local host, see
|
||||
[I want to connect to a container from Windows](../networking.md#i-want-to-connect-to-a-container-from-the-host)
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> When you switch to Windows containers, **Settings** only shows those tabs that are active and apply to your Windows containers. These are:
|
||||
>
|
||||
> * [General](../settings/windows.md#general)
|
||||
> * [Proxies](../settings/windows.md#proxies)
|
||||
> * [Daemon](../settings/windows.md#docker-engine)
|
||||
|
||||
If you set proxies or daemon configuration in Windows containers mode, these
|
||||
apply only on Windows containers. If you switch back to Linux containers,
|
||||
proxies and daemon configurations return to what you had set for Linux
|
||||
containers. Your Windows container settings are retained and become available
|
||||
again when you switch back.
|
||||
@@ -3,7 +3,7 @@ description: Install Docker on Linux with ease using our step-by-step installati
|
||||
guide covering system requirements, supported platforms, and where to go next.
|
||||
keywords: linux, docker linux install, docker linux, linux docker installation, docker
|
||||
for linux, docker desktop for linux, installing docker on linux, docker download
|
||||
linux, how to install docker on linux
|
||||
linux, how to install docker on linux, linux vs docker engine, switch docker contexts
|
||||
title: Install Docker Desktop on Linux
|
||||
aliases:
|
||||
- /desktop/linux/install/
|
||||
@@ -22,6 +22,89 @@ This page contains information about general system requirements, supported plat
|
||||
>For more information see [What is the difference between Docker Desktop for Linux and Docker Engine](../faqs/linuxfaqs.md#what-is-the-difference-between-docker-desktop-for-linux-and-docker-engine).
|
||||
{ .important }
|
||||
|
||||
{{< accordion title=" What is the difference between Docker Desktop for Linux and Docker Engine?" >}}
|
||||
|
||||
Docker Desktop for Linux provides a user-friendly graphical interface that simplifies the management of containers and services. It includes Docker Engine as this is the core technology that powers Docker containers. Docker Desktop for Linux also comes with additional features like Docker Scout and Docker Extensions.
|
||||
|
||||
#### Installing Docker Desktop and Docker Engine
|
||||
|
||||
Docker Desktop for Linux and Docker Engine can be installed side-by-side on the
|
||||
same machine. Docker Desktop for Linux stores containers and images in an isolated
|
||||
storage location within a VM and offers
|
||||
controls to restrict [its resources](../settings/linux.md#resources). Using a dedicated storage
|
||||
location for Docker Desktop prevents it from interfering with a Docker Engine
|
||||
installation on the same machine.
|
||||
|
||||
While it's possible to run both Docker Desktop and Docker Engine simultaneously,
|
||||
there may be situations where running both at the same time can cause issues.
|
||||
For example, when mapping network ports (`-p` / `--publish`) for containers, both
|
||||
Docker Desktop and Docker Engine may attempt to reserve the same port on your
|
||||
machine, which can lead to conflicts ("port already in use").
|
||||
|
||||
We generally recommend stopping the Docker Engine while you're using Docker Desktop
|
||||
to prevent the Docker Engine from consuming resources and to prevent conflicts
|
||||
as described above.
|
||||
|
||||
Use the following command to stop the Docker Engine service:
|
||||
|
||||
```console
|
||||
$ sudo systemctl stop docker docker.socket containerd
|
||||
```
|
||||
|
||||
Depending on your installation, the Docker Engine may be configured to automatically
|
||||
start as a system service when your machine starts. Use the following command to
|
||||
disable the Docker Engine service, and to prevent it from starting automatically:
|
||||
|
||||
```console
|
||||
$ sudo systemctl disable docker docker.socket containerd
|
||||
```
|
||||
|
||||
### Switching between Docker Desktop and Docker Engine
|
||||
|
||||
The Docker CLI can be used to interact with multiple Docker Engines. For example,
|
||||
you can use the same Docker CLI to control a local Docker Engine and to control
|
||||
a remote Docker Engine instance running in the cloud. [Docker Contexts](../../engine/context/working-with-contexts.md)
|
||||
allow you to switch between Docker Engines instances.
|
||||
|
||||
When installing Docker Desktop, a dedicated "desktop-linux" context is created to
|
||||
interact with Docker Desktop. On startup, Docker Desktop automatically sets its
|
||||
own context (`desktop-linux`) as the current context. This means that subsequent
|
||||
Docker CLI commands target Docker Desktop. On shutdown, Docker Desktop resets
|
||||
the current context to the `default` context.
|
||||
|
||||
Use the `docker context ls` command to view what contexts are available on your
|
||||
machine. The current context is indicated with an asterisk (`*`);
|
||||
|
||||
```console
|
||||
$ docker context ls
|
||||
NAME DESCRIPTION DOCKER ENDPOINT ...
|
||||
default * Current DOCKER_HOST based configuration unix:///var/run/docker.sock ...
|
||||
desktop-linux unix:///home/<user>/.docker/desktop/docker.sock ...
|
||||
```
|
||||
|
||||
If you have both Docker Desktop and Docker Engine installed on the same machine,
|
||||
you can run the `docker context use` command to switch between the Docker Desktop
|
||||
and Docker Engine contexts. For example, use the "default" context to interact
|
||||
with the Docker Engine:
|
||||
|
||||
```console
|
||||
$ docker context use default
|
||||
default
|
||||
Current context is now "default"
|
||||
```
|
||||
|
||||
And use the `desktop-linux` context to interact with Docker Desktop:
|
||||
|
||||
```console
|
||||
$ docker context use desktop-linux
|
||||
desktop-linux
|
||||
Current context is now "desktop-linux"
|
||||
```
|
||||
|
||||
Refer to the [Docker Context documentation](../../engine/context/working-with-contexts.md) for more details.
|
||||
|
||||
{{< /accordion >}}
|
||||
|
||||
## Supported platforms
|
||||
|
||||
Docker provides `.deb` and `.rpm` packages from the following Linux distributions
|
||||
@@ -132,6 +215,7 @@ Sign out and sign back in so that your group membership is re-evaluated.
|
||||
- [Install on Fedora](fedora.md)
|
||||
- [Install on Ubuntu](ubuntu.md)
|
||||
- [Install on Arch](archlinux.md)
|
||||
By default, Docker Desktop is installed at `/opt/docker-desktop`.
|
||||
|
||||
2. Open your **Applications** menu in Gnome/KDE Desktop and search for **Docker Desktop**.
|
||||
|
||||
|
||||
@@ -69,7 +69,7 @@ Beginning with Docker Desktop 4.3.0, we have removed the hard requirement to ins
|
||||
|
||||
1. Download the installer using the download buttons at the top of the page, or from the [release notes](../release-notes.md).
|
||||
|
||||
2. Double-click `Docker.dmg` to open the installer, then drag the Docker icon to the **Applications** folder.
|
||||
2. Double-click `Docker.dmg` to open the installer, then drag the Docker icon to the **Applications** folder. By default, Docker Desktop is installed at `/Applications/Docker.app`.
|
||||
|
||||
3. Double-click `Docker.app` in the **Applications** folder to start Docker.
|
||||
|
||||
@@ -102,7 +102,7 @@ $ sudo /Volumes/Docker/Docker.app/Contents/MacOS/install
|
||||
$ sudo hdiutil detach /Volumes/Docker
|
||||
```
|
||||
|
||||
As macOS typically performs security checks the first time an application is used, the `install` command can take several minutes to run.
|
||||
By default, Docker Desktop is installed at `/Applications/Docker.app`. As macOS typically performs security checks the first time an application is used, the `install` command can take several minutes to run.
|
||||
|
||||
The `install` command accepts the following flags:
|
||||
- `--accept-license`: Accepts the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement) now, rather than requiring it to be accepted when the application is first run.
|
||||
|
||||
@@ -3,7 +3,7 @@ description: Get started with Docker for Windows. This guide covers system requi
|
||||
where to download, and instructions on how to install and update.
|
||||
keywords: docker for windows, docker windows, docker desktop for windows, docker on
|
||||
windows, install docker windows, install docker on windows, docker windows 10, docker
|
||||
run on windows, installing docker for windows
|
||||
run on windows, installing docker for windows, windows containers, wsl, hyper-v
|
||||
title: Install Docker Desktop on Windows
|
||||
aliases:
|
||||
- /desktop/windows/install/
|
||||
@@ -107,15 +107,41 @@ Running Docker Desktop inside a VMware ESXi or Azure VM is supported for Docker
|
||||
It requires enabling nested virtualization on the hypervisor first.
|
||||
For more information, see [Running Docker Desktop in a VM or VDI environment](../vm-vdi.md).
|
||||
|
||||
{{< accordion title="About Windows containers" >}}
|
||||
{{< accordion title="How do I switch between Windows and Linux containers?" >}}
|
||||
|
||||
Looking for information on using Windows 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 Windows
|
||||
containers, or select **Switch to Linux containers** to use Linux containers
|
||||
(the default).
|
||||
|
||||
* [Switch between Windows and Linux containers](../faqs/windowsfaqs.md#how-do-i-switch-between-windows-and-linux-containers)
|
||||
describes how you can toggle between Linux and Windows containers in Docker Desktop and points you to the tutorial mentioned below.
|
||||
- [Getting Started with Windows Containers](https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce)
|
||||
- Docker Container Platform for Windows [articles and blog
|
||||
posts](https://www.docker.com/microsoft/) on the Docker website.
|
||||
For more information on Windows containers, refer to the following documentation:
|
||||
|
||||
- Microsoft documentation on [Windows containers](https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/index).
|
||||
|
||||
- [Build and Run Your First Windows Server Container (Blog Post)](https://www.docker.com/blog/build-your-first-docker-windows-server-container/)
|
||||
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)](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md)
|
||||
shows you how to use the [MusicStore](https://github.com/aspnet/MusicStore/)
|
||||
application with Windows containers. The MusicStore is a standard .NET application and,
|
||||
[forked here to use containers](https://github.com/friism/MusicStore), is a good example of a multi-container application.
|
||||
|
||||
- To understand how to connect to Windows containers from the local host, see
|
||||
[I want to connect to a container from Windows](../networking.md#i-want-to-connect-to-a-container-from-the-host)
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> When you switch to Windows containers, **Settings** only shows those tabs that are active and apply to your Windows containers. These are:
|
||||
>
|
||||
> * [General](../settings/windows.md#general)
|
||||
> * [Proxies](../settings/windows.md#proxies)
|
||||
> * [Daemon](../settings/windows.md#docker-engine)
|
||||
|
||||
If you set proxies or daemon configuration in Windows containers mode, these
|
||||
apply only on Windows containers. If you switch back to Linux containers,
|
||||
proxies and daemon configurations return to what you had set for Linux
|
||||
containers. Your Windows container settings are retained and become available
|
||||
again when you switch back.
|
||||
|
||||
{{< /accordion >}}
|
||||
|
||||
@@ -126,7 +152,7 @@ Looking for information on using Windows containers?
|
||||
|
||||
1. Download the installer using the download button at the top of the page, or from the [release notes](../release-notes.md).
|
||||
|
||||
2. Double-click `Docker Desktop Installer.exe` to run the installer.
|
||||
2. Double-click `Docker Desktop Installer.exe` to run the installer. By default, Docker Desktop is installed at `C:\Program Files\Docker\Docker`.
|
||||
|
||||
3. When prompted, ensure the **Use WSL 2 instead of Hyper-V** option on the Configuration page is selected or not depending on your choice of backend.
|
||||
|
||||
@@ -163,6 +189,8 @@ If using the Windows Command Prompt:
|
||||
start /w "" "Docker Desktop Installer.exe" install
|
||||
```
|
||||
|
||||
By default, Docker Desktop is installed at `C:\Program Files\Docker\Docker`.
|
||||
|
||||
The `install` command accepts the following flags:
|
||||
- `--quiet`: Suppresses information output when running the installer
|
||||
- `--accept-license`: Accepts the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement) now, rather than requiring it to be accepted when the application is first run
|
||||
|
||||
@@ -43,6 +43,15 @@ Docker Desktop to their initial state, the same as when Docker Desktop was first
|
||||
If you are a Mac or Linux user, you also have the option to **Uninstall** Docker Desktop from your system.
|
||||
|
||||
## Diagnose
|
||||
|
||||
> **Tip**
|
||||
>
|
||||
> If you do not find a solution in troubleshooting, browse the GitHub repositories or create a new issue:
|
||||
>
|
||||
> - [docker/for-mac](https://github.com/docker/for-mac/issues)
|
||||
> - [docker/for-win](https://github.com/docker/for-win/issues)
|
||||
> - [docker/for-linux](https://github.com/docker/for-linux/issues)
|
||||
{ .tip }
|
||||
|
||||
### Diagnose from the app
|
||||
|
||||
|
||||
@@ -5,6 +5,15 @@ title: Troubleshoot topics for Docker Desktop
|
||||
toc_max: 4
|
||||
---
|
||||
|
||||
> **Tip**
|
||||
>
|
||||
> If you do not find a solution in troubleshooting, browse the GitHub repositories or create a new issue:
|
||||
>
|
||||
> - [docker/for-mac](https://github.com/docker/for-mac/issues)
|
||||
> - [docker/for-win](https://github.com/docker/for-win/issues)
|
||||
> - [docker/for-linux](https://github.com/docker/for-linux/issues)
|
||||
{ .tip }
|
||||
|
||||
## Topics for all platforms
|
||||
|
||||
### Make sure certificates are set up correctly
|
||||
@@ -25,6 +34,20 @@ As well as on the registry. For example:
|
||||
2017/06/20 18:15:30 http: TLS handshake error from 192.168.203.139:52883: tls: first record does not look like a TLS handshake
|
||||
```
|
||||
|
||||
### Docker Desktop's UI appears green, distorted, or has visual artifacts
|
||||
|
||||
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:
|
||||
|
||||
- Mac: `~/Library/Group Containers/group.com.docker/settings.json`
|
||||
- Windows: `C:\Users\[USERNAME]\AppData\Roaming\Docker\settings.json`
|
||||
- Linux: `~/.docker/desktop/settings.json.`
|
||||
|
||||
After updating the `settings.json` file, close and restart Docker Desktop to apply the changes.
|
||||
|
||||
## Topics for Linux and Mac
|
||||
|
||||
### Volume mounting requires file sharing for any project directories outside of `$HOME`
|
||||
@@ -313,3 +336,12 @@ C:\Program Files\Docker\docker.exe:
|
||||
image operating system "linux" cannot be used on this platform.
|
||||
See 'C:\Program Files\Docker\docker.exe run --help'.
|
||||
```
|
||||
|
||||
### `Docker Desktop Access Denied` error message when starting Docker Desktop
|
||||
|
||||
Docker Desktop displays the **Docker Desktop - Access Denied** error if a Windows user is not part of the **docker-users** group.
|
||||
|
||||
If your admin account is different to your user account, add the **docker-users** group. Run **Computer Management** as an administrator and navigate to **Local Users and Groups** > **Groups** > **docker-users**.
|
||||
|
||||
Right-click to add the user to the group. Sign out and sign back in for the changes to take effect.
|
||||
|
||||
|
||||
@@ -1945,6 +1945,8 @@ Manuals:
|
||||
title: Control startup order
|
||||
- path: /compose/samples-for-compose/
|
||||
title: Sample apps with Compose
|
||||
- path: /compose/feedback/
|
||||
title: Give feedback
|
||||
- path: /compose/migrate/
|
||||
title: Migrate to Compose V2
|
||||
- path: /compose/release-notes/
|
||||
|
||||
@@ -128,11 +128,6 @@
|
||||
<div class="w-full">
|
||||
<h2 class="text-lg mb-2">Common FAQs</h6>
|
||||
<ul class="space-y-3">
|
||||
<li>
|
||||
<a class="link"
|
||||
href="/desktop/faqs/general/#what-are-the-system-requirements-for-docker-desktop">What are the
|
||||
system requirements for Docker Desktop?</a>
|
||||
</li>
|
||||
<li>
|
||||
<a class="link" href="https://github.com/docker/awesome-compose" target="_blank"
|
||||
rel="noopener">Where can I find example Compose files?</a>
|
||||
|
||||
Reference in New Issue
Block a user