docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #15130 from thaJeztah/sync_desktop_settings 

desktop: updates to "settings" section
This commit is contained in:
Usha Mandya 2022-07-15 22:16:13 +01:00 committed by GitHub
parent f02e3ea4b6 7b7a947b9d
commit b6034284ca
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
19 changed files with 429 additions and 349 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
_data/toc.yaml
View File

@ -1183,11 +1183,11 @@ manuals:
title: Dashboard
- sectiontitle: Change settings
section:
- path: /desktop/settings/mac-settings/
- path: /desktop/settings/mac/
title: On Mac
- path: /desktop/settings/windows-settings/
- path: /desktop/settings/windows/
title: On Windows
- path: /desktop/settings/linux-settings/
- path: /desktop/settings/linux/
title: On Linux
- path: /desktop/networking/
title: Explore networking features

2
compose/gettingstarted.md
View File

@ -273,7 +273,7 @@ mount is denied, or a service cannot start, try enabling file or drive sharing.
Volume mounting requires shared drives for projects that live outside of
`C:\Users` (Windows) or `/Users` (Mac), and is required for _any_ project on
Docker Desktop for Windows that uses [Linux containers](../desktop/windows/index.md#switch-between-windows-and-linux-containers).
For more information, see [File sharing](../desktop/settings/mac-settings.md#file-sharing) on Docker
For more information, see [File sharing](../desktop/settings/mac.md#file-sharing) on Docker
for Mac, and the general examples on how to
> [Manage data in containers](../storage/volumes.md).
>

2
desktop/faqs/windowsfaqs.md
View File

@ -42,7 +42,7 @@ Desktop. For more information, see [Docker Desktop fails to start when anti-viru
### Can I change permissions on shared volumes for container-specific deployment requirements?
Docker Desktop does not enable you to control (`chmod`)
the Unix-style permissions on [shared volumes](../settings/windows-settings.md#file-sharing) for
the Unix-style permissions on [shared volumes](../settings/windows.md#file-sharing) for
deployed containers, but rather sets permissions to a default value of
[0777](http://permissions-calculator.org/decode/0777/){: target="_blank" rel="noopener" class="_"}
(`read`, `write`, `execute` permissions for `user` and for

2
desktop/install/linux-install.md
View File

@ -143,7 +143,7 @@ Log out and log back in so that your group membership is re-evaluated.
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](linux-install.md#why-docker-desktop-for-linux-runs-a-vm) and offers
controls to restrict [its resources](../settings/linux-settings.md#resources). Using a dedicated storage
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.

4
desktop/linux/troubleshoot.md
View File

@ -24,7 +24,7 @@ The Troubleshoot page contains the following options:
* **Support**: Users with a paid Docker subscription can use this option to send a support request. Other users can use this option to diagnose any issues in Docker Desktop. For more information, see [Diagnose and feedback](#diagnose-and-feedback) and [Support](../../support/index.md).
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../settings/linux-settings.md#kubernetes).
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../settings/linux.md#kubernetes).
* **Clean / Purge data**: This option resets all Docker data _without_ a
reset to factory defaults. Selecting this option results in the loss of existing settings.
@ -146,7 +146,7 @@ to learn how to view the Docker Daemon logs.
If you are using mounted volumes and get runtime errors indicating an
application file is not found, access to a volume mount is denied, or a service
cannot start, such as when using [Docker Compose](../../compose/gettingstarted.md),
you might need to enable [file sharing](../settings/linux-settings.md#file-sharing).
you might need to enable [file sharing](../settings/linux.md#file-sharing).
Volume mounting requires shared drives for projects that live outside of the
`/home/<user>` directory. Go to ![whale menu](images/whale-x.png){: .inline} >

2
desktop/mac/apple-silicon.md
View File

@ -31,7 +31,7 @@ $ softwareupdate --install-rosetta
### Known issues
- Some command line tools do not work when Rosetta 2 is not installed.
- The old version 1.x of `docker-compose`. We recommend that you use Compose V2 instead. Either type `docker compose` or enable the **Use Docker Compose V2** option in the [General preferences tab](../settings/mac-settings.md#general).
- The old version 1.x of `docker-compose`. We recommend that you use Compose V2 instead. Either type `docker compose` or enable the **Use Docker Compose V2** option in the [General preferences tab](../settings/mac.md#general).
- The `docker scan` command and the underlying `snyk` binary.
- The `docker-credential-ecr-login` credential helper.
- Not all images are available for ARM64 architecture. You can add `--platform linux/amd64` to run an Intel image under emulation. In particular, the [mysql](https://hub.docker.com/_/mysql?tab=tags&page=1&ordering=last_updated) image is not available for ARM64. You can work around this issue by using a [mariadb](https://hub.docker.com/_/mariadb?tab=tags&page=1&ordering=last_updated) image.

4
desktop/mac/troubleshoot.md
View File

@ -27,7 +27,7 @@ The Troubleshoot page contains the following options:
* **Support**: Users with a paid Docker subscription can use this option to send a support request. Other users can use this option to diagnose any issues in Docker Desktop. For more information, see [Diagnose and feedback](#diagnose-and-feedback) and [Support](../../support/index.md).
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../settings/mac-settings.md#kubernetes).
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../settings/mac.md#kubernetes).
* **Clean / Purge data**: This option resets all Docker data _without_ a
reset to factory defaults. Selecting this option results in the loss of existing settings.
@ -205,7 +205,7 @@ For more about using client and server side certificates, see
If you are using mounted volumes and get runtime errors indicating an
application file is not found, access to a volume mount is denied, or a service
cannot start, such as when using [Docker Compose](../../compose/gettingstarted.md),
you might need to enable [file sharing](../settings/mac-settings.md#file-sharing).
you might need to enable [file sharing](../settings/mac.md#file-sharing).
Volume mounting requires shared drives for projects that live outside of the
`/Users` directory. Go to ![whale menu](images/whale-x.png){: .inline} >

6
desktop/networking.md
View File

@ -46,9 +46,9 @@ syntax for `-p` is `HOST_PORT:CLIENT_PORT`.
### HTTP/HTTPS Proxy Support
See:
- [Proxies on Linux](settings/linux-settings.md#proxies)
- [Proxies on Mac](settings/mac-settings.md#proxies)
- [Proxies on Windows](settings/windows-settings.md#proxies)
- [Proxies on Linux](settings/linux.md#proxies)
- [Proxies on Mac](settings/mac.md#proxies)
- [Proxies on Windows](settings/windows.md#proxies)
## Features for Mac and Linux

2
desktop/previous-versions/2.x-windows.md
View File

@ -377,7 +377,7 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
- Fixed a race condition when starting the WSL engine which caused Docker Desktop to incorrectly report that the containers have exited. Fixes [docker/for-win#5607](https://github.com/docker/for-win/issues/5607).
- Fixed an issue where editing code inside a container resulted in an error. Fixes [docker/for-win#5528](https://github.com/docker/for-win/issues/5528).
- Fixed a bug where running the command `DockerCli.exe -SharedDrives` failed to display a list of drives that are shared. Fixes [docker/for-win#5625](https://github.com/docker/for-win/issues/5625).
- Starting with Docker Desktop 2.2.0.3, you must access all shared files using their original case. For example, if you have created a file called `test`, you must open it as `test`. Attempts to open the file as `Test` will fail with the error `No such file or directory`. For more information, see _Tips on shared drives, permissions, and volume mounts_ in [File sharing](../settings/windows-settings.md#file-sharing).
- Starting with Docker Desktop 2.2.0.3, you must access all shared files using their original case. For example, if you have created a file called `test`, you must open it as `test`. Attempts to open the file as `Test` will fail with the error `No such file or directory`. For more information, see _Tips on shared drives, permissions, and volume mounts_ in [File sharing](../settings/windows.md#file-sharing).
### Known issues

4
desktop/previous-versions/edge-releases-mac.md
View File

@ -1868,9 +1868,9 @@ TCP connection is idle for more than five minutes (related to
**New**
- Dedicated preference pane for advanced configuration of the docker daemon (edit daemon.json). See [Daemon Advanced (JSON configuration file)](../settings/mac-settings.md#docker-engine).
- Dedicated preference pane for advanced configuration of the docker daemon (edit daemon.json). See [Daemon Advanced (JSON configuration file)](../settings/mac.md#docker-engine).
- Docker Experimental mode can be toggled. See [Daemon Basic (experimental mode and registries)](../settings/mac-settings.md#docker-engine).
- Docker Experimental mode can be toggled. See [Daemon Basic (experimental mode and registries)](../settings/mac.md#docker-engine).
**Upgrades**

2
desktop/release-notes.md
View File

@ -452,7 +452,7 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/ge
#### For Mac
- Docker Desktop 4.6.0 gives macOS users the option of enabling a new experimental file sharing technology called VirtioFS. During testing VirtioFS has been shown to drastically reduce the time taken to sync changes between the host and VM, leading to substantial performance improvements. For more information, see [VirtioFS](settings/mac-settings.md#experimental-features).
- Docker Desktop 4.6.0 gives macOS users the option of enabling a new experimental file sharing technology called VirtioFS. During testing VirtioFS has been shown to drastically reduce the time taken to sync changes between the host and VM, leading to substantial performance improvements. For more information, see [VirtioFS](settings/mac.md#experimental-features).
### Upgrades

108
desktop/settings/linux-settings.md → desktop/settings/linux.md
View File

@ -1,45 +1,55 @@
---
description: Docker Desktop settings
keywords: Settings, Docker Desktop, Linux
title: Change Docker Dektop settings on Linux
keywords: settings, preferences, proxy, file sharing, resources, kubernetes, Docker Desktop, Linux
title: Change Docker Desktop settings on Linux
---
This page provides information on how to configure and manage your Docker Desktop settings.
To navigate to **Settings** either:
- Select the Docker menu ![whale menu](../images/whale-x.png){: .inline} and then **Settings**
- Select the **Settings** icon from the Docker Dashboard.
- Select the Docker menu ![whale menu](../images/whale-x.png){: .inline} and then **Settings**
- Select the **Settings** icon from the Docker Dashboard.
## General
On the **General** tab, you can configure when to start Docker and specify other settings:
- **Start Docker Desktop when you log in**. This automatically starts Docker Desktop when you open your session.
- **Start Docker Desktop when you log in**. Select to automatically start Docker
Desktop when you log into your machine.
- **Send usage statistics**. Docker Desktop sends diagnostics, crash reports, and usage data. This information helps Docker improve and troubleshoot the application. Clear the check box to opt out.
- **Send usage statistics**. Select so Docker Desktop sends diagnostics,
crash reports, and usage data. This information helps Docker improve and
troubleshoot the application. Clear the check box to opt out. Docker may
periodically prompt you for more information.
- **Show weekly tips**. Select to display useful advice and suggestions about using Docker.
- **Show weekly tips**. Select to display useful advice and suggestions about
using Docker.
- **Open Docker Desktop dashboard at startup**. Select to automatically opens the dashboard when starting Docker Desktop.
- **Open Docker Desktop dashboard at startup**. Select to automatically open the
dashboard when starting Docker Desktop.
- **Use Docker Compose V2**. Select to enable the `docker-compose` command to use Docker Compose V2. For more information, see [Docker Compose V2](../../compose/index.md#compose-v2-and-the-new-docker-compose-command)
- **Use Docker Compose V2**. Select to enable the `docker-compose` command to
use Docker Compose V2. For more information, see [Docker Compose V2](../../compose/index.md#compose-v2-and-the-new-docker-compose-command).
## Resources
The **Resources** tab allows you to configure CPU, memory, disk, proxies, network, and other resources.
The **Resources** tab allows you to configure CPU, memory, disk, proxies,
network, and other resources.
#### Advanced
### Advanced
On the **Advanced** tab, you can limit resources available to Docker.
Advanced settings are:
- **CPUs**. By default, Docker Desktop is set to use half the number of processors
available on the host machine. To increase processing power, set this to a
higher number; to decrease, lower the number.
available on the host machine. To increase processing power, set this to a
higher number; to decrease, lower the number.
- **Memory**. By default, Docker Desktop is set to use 25% of your host's memory. To increase the RAM, set this to a higher number. To decrease it, lower the number.
- **Memory**. By default, Docker Desktop is set to use 25% of your host's
memory. To increase the RAM, set this to a higher number; to decrease it,
lower the number.
- **Swap**. Configure swap file size as needed. The default is 1 GB.
@ -51,33 +61,34 @@ You can also move the disk image to a different location. If you attempt to move
### File sharing
Use File sharing to allow local directories on the Linux host to be shared with Linux containers.
This is especially useful for
editing source code in an IDE on the host while running and testing the code in a container.
By default the `/home/<user>` directory is shared. If your project is outside this directory then it must be added
to the list. Otherwise you may get `Mounts denied` or `cannot start service` errors at runtime.
Use File sharing to allow local directories on your machine to be shared with
Linux containers. This is especially useful for editing source code in an IDE on
the host while running and testing the code in a container.
By default the `/home/<user>` directory is shared.
If your project is outside this directory then it must be added to the list,
otherwise you may get `Mounts denied` or `cannot start service` errors at runtime.
File share settings are:
- **Add a Directory**: Click `+` and navigate to the directory you want to add.
- **Add a Directory**. Click `+` and navigate to the directory you want to add.
- **Remove a Directory**: Click `-` next to the directory you want to remove
- **Remove a Directory**. Click `-` next to the directory you want to remove
- **Apply & Restart** makes the directory available to containers using Docker's
bind mount (`-v`) feature.
> Tips on shared folders, permissions, and volume mounts
>
* Share only the directories that you need with the container. File sharing
introduces overhead as any changes to the files on the host need to be notified
to the Linux VM. Sharing too many files can lead to high CPU load and slow
filesystem performance.
>
* Shared folders are designed to allow application code to be edited
on the host while being executed in containers. For non-code items
such as cache directories or databases, the performance will be much
better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md)
(named volume) or [data container](../../storage/volumes.md).
> * Share only the directories that you need with the container. File sharing
> introduces overhead as any changes to the files on the host need to be notified
> to the Linux VM. Sharing too many files can lead to high CPU load and slow
> filesystem performance.
> * Shared folders are designed to allow application code to be edited
> on the host while being executed in containers. For non-code items
> such as cache directories or databases, the performance will be much
> better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md)
> (named volume) or [data container](../../storage/volumes.md).
### Proxies
@ -98,7 +109,7 @@ HTTP_PROXY=http://proxy.example.com:3128
```
For more information on configuring the Docker CLI to automatically set proxy variables for both `docker run` and `docker build`
see [Configure the Docker client](/network/proxy#configure-the-docker-client).
see [Configure the Docker client](../../network/proxy.md#configure-the-docker-client).
### Network
@ -121,24 +132,35 @@ From the **Experimental features** tab, you can sign up to the [Developer Previe
## Kubernetes
Docker Desktop includes a standalone Kubernetes server, so
that you can test deploying your Docker workloads on Kubernetes. To enable Kubernetes support and install a standalone instance of Kubernetes running as a Docker container, select **Enable Kubernetes**.
Docker Desktop includes a standalone Kubernetes server, so that you can test
deploying your Docker workloads on Kubernetes. To enable Kubernetes support and
install a standalone instance of Kubernetes running as a Docker container,
select **Enable Kubernetes**.
Select **Show system containers (advanced)** to view internal containers when using Docker commands.
Select **Show system containers (advanced)** to view internal containers when
using Docker commands.
Select **Reset Kubernetes cluster** to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../kubernetes.md){:target="_blank" rel="noopener" class="_"}.
Select **Reset Kubernetes cluster** to delete all stacks and Kubernetes resources.
For more information about using the Kubernetes integration with Docker Desktop,
see [Deploy on Kubernetes](../kubernetes.md){:target="_blank" rel="noopener" class="_"}.
## Software Updates
The **Software Updates** tab notifies you of any updates available to Docker Desktop. When there's a new update, click the **Release Notes** option to learn what's included in the updated version.
The **Software Updates** tab notifies you of any updates available to Docker Desktop.
When there's a new update,
click the **Release Notes** option to learn what's included in the updated version.
> **Disable automatic check for updates**
>
> Turn off the check for updates by clearing the **Automatically check for updates** check box. This disables notifications in the Docker menu and also the notification badge that appears on the Docker Dashboard. To check for updates manually, select the **Check for updates** option in the Docker menu.
Turn off the check for updates by clearing the **Automatically check for updates**
check box. This disables notifications in the Docker menu and the notification
badge that appears on the Docker Dashboard. To check for updates manually, select
the **Check for updates** option in the Docker menu.
Turn off the check for updates by clearing the **Automatically check for updates** check box. This disables notifications in the Docker menu and also the notification badge that appears on the Docker Dashboard. To check for updates manually, select the **Check for updates** option in the Docker menu.
To allow Docker Desktop to automatically download new updates in the background, select **Always download updates**. This downloads newer versions of Docker Desktop when an update becomes available. After downloading the update, click **Apply and Restart** to install the update. You can do this either through the Docker menu or in the **Updates** section in the Docker Dashboard.
To allow Docker Desktop to automatically download new updates in the background,
select **Always download updates**. This downloads newer versions of Docker Desktop
when an update becomes available. After downloading the update, click
**Apply and Restart** to install the update. You can do this either through the
Docker menu or in the **Updates** section in the Docker Dashboard.
## Extensions

146
desktop/settings/mac-settings.md → desktop/settings/mac.md
View File

@ -1,37 +1,47 @@
---
description: Docker Desktop settings
keywords: Settings, Docker Desktop, Mac
title: Change Docker Dektop preferences on Mac
keywords: settings, preferences, proxy, file sharing, resources, kubernetes, Docker Desktop, Mac
title: Change Docker Desktop preferences on Mac
---
This page provides information on how to configure and manage your Docker Desktop settings.
To navigate to **Preferences** either:
- Select the Docker menu ![whale menu](../images/whale-x.png){: .inline} and then **Preferences**
- Select the **Preferences** icon from the Docker Dashboard.
- Select the Docker menu ![whale menu](../images/whale-x.png){: .inline} and then **Preferences**
- Select the **Preferences** icon from the Docker Dashboard.
### General
## General
On the **General** tab, you can configure when to start Docker and specify other settings:
- **Start Docker Desktop when you log in**. This automatically starts Docker Desktop when you open your session.
- **Start Docker Desktop when you log in**. Select to automatically start Docker
Desktop when you log into your machine.
- **Include VM in Time Machine backups**. Select to back up the Docker Desktop virtual machine. This option is disabled by default.
- **Include VM in Time Machine backups**. Select to back up the Docker Desktop
virtual machine. This option is disabled by default.
- **Use gRPC FUSE for file sharing**. Clear this check box to use the legacy osxfs file sharing instead.
- **Use gRPC FUSE for file sharing**. Clear this check box to use the legacy
osxfs file sharing instead.
- **Send usage statistics**. Select so Docker Desktop sends diagnostics, crash reports, and usage data. This information helps Docker improve and troubleshoot the application. Clear the check box to opt out.
- **Send usage statistics**. Select so Docker Desktop sends diagnostics,
crash reports, and usage data. This information helps Docker improve and
troubleshoot the application. Clear the check box to opt out. Docker may
periodically prompt you for more information.
- **Show weekly tips**. Select to display useful advice and suggestions about using Docker.
- **Show weekly tips**. Select to display useful advice and suggestions about
using Docker.
- **Open Docker Desktop dashboard at startup**. Select to automatically open Docker Dashboard when starting Docker Desktop.
- **Open Docker Desktop dashboard at startup**. Select to automatically open the
dashboard when starting Docker Desktop.
- **Use Docker Compose V2**. Select to enable the `docker-compose` command to use Docker Compose V2. For more information, see [Docker Compose V2](../../compose/index.md#compose-v2-and-the-new-docker-compose-command).
- **Use Docker Compose V2**. Select to enable the `docker-compose` command to
use Docker Compose V2. For more information, see [Docker Compose V2](../../compose/index.md#compose-v2-and-the-new-docker-compose-command).
## Resources
The **Resources** tab allows you to configure CPU, memory, disk, proxies, network, and other resources.
The **Resources** tab allows you to configure CPU, memory, disk, proxies,
network, and other resources.
### Advanced
@ -40,11 +50,12 @@ On the **Advanced** tab, you can limit resources available to Docker.
Advanced settings are:
- **CPUs**. By default, Docker Desktop is set to use half the number of processors
available on the host machine. To increase processing power, set this to a
higher number; to decrease, lower the number.
available on the host machine. To increase processing power, set this to a
higher number; to decrease, lower the number.
- **Memory**. By default, Docker Desktop is set to use `2` GB runtime memory,
allocated from the total available memory on your Mac. To increase the RAM, set this to a higher number. To decrease it, lower the number.
- **Memory**. By default, Docker Desktop is set to use `2` GB of your host's
memory. To increase the RAM, set this to a higher number; to decrease it,
lower the number.
- **Swap**. Configure swap file size as needed. The default is 1 GB.
@ -54,13 +65,15 @@ allocated from the total available memory on your Mac. To increase the RAM, set
You can also move the disk image to a different location. If you attempt to move a disk image to a location that already has one, you are asked if you want to use the existing image or replace it.
#### File sharing
### File sharing
Use File sharing to allow local directories on the Mac to be shared with Linux containers.
This is especially useful for
editing source code in an IDE on the host while running and testing the code in a container.
By default the `/Users`, `/Volume`, `/private`, `/tmp` and `/var/folders` directory are shared. If your project is outside this directory then it must be added
to the list. Otherwise you may get `Mounts denied` or `cannot start service` errors at runtime.
Use File sharing to allow local directories on your machine to be shared with
Linux containers. This is especially useful for editing source code in an IDE on
the host while running and testing the code in a container.
By default the `/Users`, `/Volume`, `/private`, `/tmp` and `/var/folders` directory are shared.
If your project is outside this directory then it must be added to the list,
otherwise you may get `Mounts denied` or `cannot start service` errors at runtime.
File share settings are:
@ -73,32 +86,31 @@ File share settings are:
> Tips on shared folders, permissions, and volume mounts
>
* Share only the directories that you need with the container. File sharing
introduces overhead as any changes to the files on the host need to be notified
to the Linux VM. Sharing too many files can lead to high CPU load and slow
filesystem performance.
> * Share only the directories that you need with the container. File sharing
> introduces overhead as any changes to the files on the host need to be notified
> to the Linux VM. Sharing too many files can lead to high CPU load and slow
> filesystem performance.
> * Shared folders are designed to allow application code to be edited
> on the host while being executed in containers. For non-code items
> such as cache directories or databases, the performance will be much
> better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md)
> (named volume) or [data container](../../storage/volumes.md).
> * If you share the whole of your home directory into a container, MacOS may
> prompt you to give Docker access to personal areas of your home directory such as
> your Reminders or Downloads.
> * By default, Mac file systems are case-insensitive while Linux is case-sensitive.
> On Linux, it is possible to create two separate files: `test` and `Test`,
> while on Mac these filenames would actually refer to the same underlying
> file. This can lead to problems where an app works correctly on a developer's
> machine (where the file contents are shared) but fails when run in Linux in
> production (where the file contents are distinct). To avoid this, Docker Desktop
> insists that all shared files are accessed as their original case. Therefore,
> if a file is created called `test`, it must be opened as `test`. Attempts to
> open `Test` will fail with the error "No such file or directory". Similarly,
> once a file called `test` is created, attempts to create a second file called
> `Test` will fail.
>
* Shared folders are designed to allow application code to be edited
on the host while being executed in containers. For non-code items
such as cache directories or databases, the performance will be much
better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md)
(named volume) or [data container](../../storage/volumes.md).
>
* If you share the whole of your home directory into a container, MacOS may
prompt you to give Docker access to personal areas of your home directory such as
your Reminders or Downloads.
>
* By default, Mac file systems are case-insensitive while Linux is case-sensitive.
On Linux, it is possible to create 2 separate files: `test` and `Test`,
while on Mac these filenames would actually refer to the same underlying file.
This can lead to problems where an app works correctly on a Mac
(where the file contents are shared) but fails when run in Linux in
production (where the file contents are distinct). To avoid this, Docker Desktop
insists that all shared files are accessed as their original case. Therefore, if a file
is created called `test`, it must be opened as `test`. Attempts to open `Test` will
fail with the error `No such file or directory`. Similarly, once a file called `test`
is created, attempts to create a second file called `Test` will fail. For more information,
see [Volume mounting requires file sharing for any project directories outside of `/Users`](../mac/troubleshoot.md#volume-mounting-requires-file-sharing-for-any-project-directories-outside-of-users).)
> For more information, see [Volume mounting requires file sharing for any project directories outside of `/Users`](../mac/troubleshoot.md#volume-mounting-requires-file-sharing-for-any-project-directories-outside-of-users).)
### Proxies
@ -121,7 +133,7 @@ of the form `http://username:password@proxy:port`.
HTTP/HTTPS traffic from image builds and running containers is forwarded transparently to the same
upstream proxy used for logging in and image pulls.
If you want to override this behaviour and use different HTTP/HTTPS proxies for image builds and
running containers, see [Configure the Docker client](/network/proxy#configure-the-docker-client).
running containers, see [Configure the Docker client](../../network/proxy.md#configure-the-docker-client).
The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY` environment variable.
@ -138,7 +150,7 @@ Type a JSON configuration file in the box to configure the daemon settings. For
Click **Apply & Restart** to save your settings and restart Docker Desktop.
## Experimental features
## Experimental Features
{% include experimental.md %}
@ -162,25 +174,35 @@ To enable virtioFS:
## Kubernetes
Docker Desktop includes a standalone Kubernetes server that runs on your Mac, so
that you can test deploying your Docker workloads on Kubernetes. To enable Kubernetes support and install a standalone instance of Kubernetes running as a Docker container, select **Enable Kubernetes**.
Docker Desktop includes a standalone Kubernetes server, so that you can test
deploying your Docker workloads on Kubernetes. To enable Kubernetes support and
install a standalone instance of Kubernetes running as a Docker container,
select **Enable Kubernetes**.
Select **Show system containers (advanced)** to view internal containers when using Docker commands.
Select **Show system containers (advanced)** to view internal containers when
using Docker commands.
Select **Reset Kubernetes cluster** to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../kubernetes.md){:target="_blank" rel="noopener" class="_"}.
Select **Reset Kubernetes cluster** to delete all stacks and Kubernetes resources.
For more information about using the Kubernetes integration with Docker Desktop,
see [Deploy on Kubernetes](../kubernetes.md){:target="_blank" rel="noopener" class="_"}.
## Software Updates
The **Software Updates** tab notifies you of any updates available to Docker Desktop. When there's a new update, you can choose to download the update right away, or click the **Release Notes** option to learn what's included in the updated version.
The **Software Updates** tab notifies you of any updates available to Docker Desktop.
When there's a new update, you can choose to download the update right away, or
click the **Release Notes** option to learn what's included in the updated version.
> **Disable automatic check for updates**
>
> Starting with Docker Desktop 4.2.0, the option to turn off the automatic check for updates is available for users on all Docker subscriptions, including Docker Personal and Docker Pro. Update to [Docker Desktop 4.2.0](../release-notes.md) to start using this feature.
{: .important}
Turn off the check for updates by clearing the **Automatically check for updates**
check box. This disables notifications in the Docker menu and the notification
badge that appears on the Docker Dashboard. To check for updates manually, select
the **Check for updates** option in the Docker menu.
Turn off the check for updates by clearing the **Automatically check for updates** check box. This disables notifications in the Docker menu and also the notification badge that appears on the Docker Dashboard. To check for updates manually, select the **Check for updates** option in the Docker menu.
To allow Docker Desktop to automatically download new updates in the background, select **Always download updates**. This downloads newer versions of Docker Desktop when an update becomes available. After downloading the update, click **Apply and Restart** to install the update. You can do this either through the Docker menu or in the **Updates** section in the Docker Dashboard.
To allow Docker Desktop to automatically download new updates in the background,
select **Always download updates**. This downloads newer versions of Docker Desktop
when an update becomes available. After downloading the update, click
**Apply and Restart** to install the update. You can do this either through the
Docker menu or in the **Updates** section in the Docker Dashboard.
## Extensions

214
desktop/settings/windows-settings.md
View File

@ -1,214 +0,0 @@
---
description: Docker Desktop settings
keywords: Settings, Docker Desktop, Windows
title: Change Docker Dektop settings on Windows
---
This page provides information on how to configure and manage your Docker Desktop settings.
To navigate to **Settings** either:
- Select the Docker menu ![whale menu](../images/whale-x.png){: .inline} and then **Settings**
- Select the **Settings** icon from the Docker Dashboard.
## General
On the **General** tab, you can configure when to start Docker and specify other settings.
- **Start Docker when you log in**: Select to automatically start Docker Desktop when you log into your Windows machine.
- **Expose daemon on tcp://localhost:2375 without TLS**: Check this option to enable legacy clients to connect to the Docker daemon. You must use this option with caution as exposing the daemon without TLS can result in remote code execution attacks.
- **Use the WSL 2 based engine**. WSL 2 provides better performance than the legacy Hyper-V backend. For more information, see [Docker Desktop WSL 2 backend](../windows/wsl.md).
- **Send usage statistics**: By default, Docker Desktop sends diagnostics,
crash reports, and usage data. This information helps Docker improve and
troubleshoot the application. Clear the check box to opt out. Docker may periodically prompt you for more information.
- **Show weekly tips**. Select to display useful advice and suggestions about using Docker.
- **Open Docker Desktop dashboard at startup**. Select to automatically opens the dashboard when starting Docker Desktop.
- **Use Docker Compose V2**. Select to enable the `docker-compose` command to use Docker Compose V2. For more information, see [Docker Compose V2](../../compose/index.md#compose-v2-and-the-new-docker-compose-command).
## Resources
The **Resources** tab allows you to configure CPU, memory, disk, proxies,
network, and other resources. Different settings are available for
configuration depending on whether you are using Linux containers in WSL 2
mode, Linux containers in Hyper-V mode, or Windows containers.
### Advanced
> **Note**
>
> The Advanced tab is only available in Hyper-V mode, because Windows manages
> the resources in WSL 2 mode and Windows container mode. In WSL 2
> mode, you can configure limits on the memory, CPU, and swap size allocated
> to the [WSL 2 utility VM](https://docs.microsoft.com/en-us/windows/wsl/wsl-config#configure-global-options-with-wslconfig){:target="_blank"
class="_"}.
Use the **Advanced** tab to limit resources available to Docker.
- **CPUs**. By default, Docker Desktop is set to use half the number of processors
available on the host machine. To increase the processing power, set this to a
higher number. To decrease the processing power, set this to a lower number.
- **Memory**. By default, Docker Desktop is set to use `2` GB runtime memory,
allocated from the total available memory on your machine. To increase the RAM, set this to a higher number. To decrease the RAM, lower the number.
- **Swap**. Configure swap file size as needed. The default is 1 GB.
- **Disk image size**. Specify the size of the disk image.
- **Disk image location**. Specify the location of the Linux volume where containers and images are stored.
You can also move the disk image to a different location. If you attempt to move a disk image to a location that already has one, you are asked if you want to use the existing image or replace it.
### File sharing
> **Note**
>
> The File sharing tab is only available in Hyper-V mode because the files
> are automatically shared in WSL 2 mode and Windows container mode.
Use File sharing to allow local directories on Windows to be shared with Linux containers.
This is especially useful for
editing source code in an IDE on the host while running and testing the code in a container.
Note that configuring file sharing is not necessary for Windows containers, only [Linux containers](../windows/index.md#switch-between-windows-and-linux-containers).
If a directory is not shared with a Linux container you may get `file not found` or `cannot start service` errors at runtime. See [Volume mounting requires shared folders for Linux containers](../windows/troubleshoot.md#volume-mounting-requires-shared-folders-for-linux-containers).
File share settings are:
- **Add a Directory**. Click `+` and navigate to the directory you want to add.
- **Remove a Directory**. Click `-` next to the directory you want to remove
- **Apply & Restart** makes the directory available to containers using Docker's
bind mount (`-v`) feature.
> Tips on shared folders, permissions, and volume mounts
>
* Share only the directories that you need with the container. File sharing
introduces overhead as any changes to the files on the host need to be notified
to the Linux VM. Sharing too many files can lead to high CPU load and slow
filesystem performance.
>
* Shared folders are designed to allow application code to be edited on the host while being executed in containers. For non-code items
such as cache directories or databases, the performance will be much better if they are stored in
the Linux VM, using a [data volume](../../storage/volumes.md)
(named volume) or [data container](../../storage/volumes.md).
>
* Docker Desktop sets permissions to read/write/execute for users, groups and others [0777 or a+rwx](http://permissions-calculator.org/decode/0777/).
This is not configurable. See [Permissions errors on data directories for shared volumes](../windows/troubleshoot.md#permissions-errors-on-data-directories-for-shared-volumes).
>
* Windows presents a case-insensitive view of the filesystem to applications while Linux is case-sensitive. On Linux, it is possible to create two separate files: `test` and `Test`, while on Windows these filenames would actually refer to the same underlying file. This can lead to problems where an app works correctly on a developer Windows machine (where the file contents are shared) but fails when run in Linux in production (where the file contents are distinct). To avoid this, Docker Desktop insists that all shared files are accessed as their original case. Therefore if a file is created called `test`, it must be opened as `test`. Attempts to open `Test` will fail with "No such file or directory". Similarly once a file called `test` is created, attempts to create a second file called `Test` will fail.
#### Shared folders on demand
You can share a folder "on demand" the first time a particular folder is used by a container.
If you run a Docker command from a shell with a volume mount (as shown in the
example below) or kick off a Compose file that includes volume mounts, you get a
popup asking if you want to share the specified folder.
You can select to **Share it**, in which case it is added to your Docker Desktop Shared Folders list and available to
containers. Alternatively, you can opt not to share it by selecting **Cancel**.
![Shared folder on demand](../images/shared-folder-on-demand.png){:width="600px"}
### Proxies
HTTP/HTTPS proxies can be used when
- Logging in to Docker
- Pulling or pushing images
- Fetching artifacts during image builds
- Containers interact with the external network
- Scanning images.
These are configured slightly differently.
If the host uses a static HTTP/HTTPS proxy configuration, Docker Desktop reads this configuration
and automatically uses these settings for logging into Docker and for pulling and pushing images.
If the host uses a more sophisticated HTTP/HTTPS configuration, enable **Manual proxy configuration** and enter a single upstream proxy URL
of the form `http://username:password@proxy:port`.
The HTTP/HTTPS proxy settings used for fetching artifacts during builds and for running containers
are set via the `.docker/config.json` file, see [Configure the Docker client](/network/proxy#configure-the-docker-client).
The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY` environment variable.
### Network
> **Note**
>
> The Network tab is not available in the Windows container mode because
> Windows manages networking.
You can configure Docker Desktop networking to work on a virtual private network (VPN). Specify a network address translation (NAT) prefix and subnet mask to enable Internet connectivity.
### WSL Integration
In WSL 2 mode, you can configure which WSL 2 distributions will have the Docker
WSL integration.
By default, the integration is enabled on your default WSL distribution.
To change your default WSL distro, run `wsl --set-default <distro name>`. (For example,
to set Ubuntu as your default WSL distro, run `wsl --set-default ubuntu`).
You can also select any additional distributions you would like to enable the WSL 2 integration on.
For more details on configuring Docker Desktop to use WSL 2, see
[Docker Desktop WSL 2 backend](../windows/wsl.md).
## Docker Engine
The **Docker Engine** tab allows you to configure the Docker daemon to determine how your containers run.
Type a JSON configuration file in the box to configure the daemon settings. For a full list of options, see the Docker Engine
[dockerd commandline reference](/engine/reference/commandline/dockerd/){:target="_blank"
class="_"}.
Click **Apply & Restart** to save your settings and restart Docker Desktop.
## Experimental features
{% include experimental.md %}
From the **Experimental features** tab, you can sign up to the [Developer Preview program](https://www.docker.com/community/get-involved/developer-preview/).
## Kubernetes
> **Note**
>
> The **Kubernetes** tab is not available in Windows container mode.
Docker Desktop includes a standalone Kubernetes server that runs on your Windows machine, so
that you can test deploying your Docker workloads on Kubernetes. To enable Kubernetes support and install a standalone instance of Kubernetes running as a Docker container, select **Enable Kubernetes**.
For more information about using the Kubernetes integration with Docker Desktop, see [Deploy on Kubernetes](../kubernetes.md){:target="_blank" rel="noopener" class="_"}.
## Software Updates
The **Software Updates** tab notifies you of any updates available to Docker Desktop. When there's a new update, you can choose to download the update right away, or click the **Release Notes** option to learn what's included in the updated version.
> **Disable automatic check for updates**
>
> Starting with Docker Desktop 4.2.0, the option to turn off the automatic check for updates is available for users on all Docker subscriptions, including Docker Personal and Docker Pro. Update to [Docker Desktop 4.2.0](../release-notes.md) to start using this feature.
{: .important}
Turn off the check for updates by clearing the **Automatically Check for Updates** check box. This disables notifications in the Docker menu and also the notification badge that appears on the Docker Dashboard. To check for updates manually, select the **Check for updates** option in the Docker menu.
To allow Docker Desktop to automatically download new updates in the background, select **Always download updates**. This downloads newer versions of Docker Desktop when an update becomes available. After downloading the update, click **Apply and Restart** to install the update. You can do this either through the Docker menu or in the **Updates** section in the Docker Dashboard.
## Extensions
Use the **Extensions** tab to:
- **Enable Docker Extensions**
- **Allow only extensions distributed through the Docker Marketplace**
- **Show Docker Extensions system containers**
For more information about Docker extensions, see [Extensions](../extensions.md).

250
desktop/settings/windows.md Normal file
View File

@ -0,0 +1,250 @@
---
description: Docker Desktop settings
keywords: settings, preferences, proxy, file sharing, resources, kubernetes, Docker Desktop, Windows
title: Change Docker Desktop settings on Windows
---
This page provides information on how to configure and manage your Docker Desktop settings.
To navigate to **Settings** either:
- Select the Docker menu ![whale menu](../images/whale-x.png){: .inline} and then **Settings**
- Select the **Settings** icon from the Docker Dashboard.
## General
On the **General** tab, you can configure when to start Docker and specify other settings:
- **Start Docker Desktop when you log in**. Select to automatically start Docker
Desktop when you log into your machine.
- **Expose daemon on tcp://localhost:2375 without TLS**. Check this option to
enable legacy clients to connect to the Docker daemon. You must use this option
with caution as exposing the daemon without TLS can result in remote code
execution attacks.
- **Use the WSL 2 based engine**. WSL 2 provides better performance than the
legacy Hyper-V backend. For more information, see [Docker Desktop WSL 2 backend](../windows/wsl.md).
- **Send usage statistics**. Select so Docker Desktop sends diagnostics,
crash reports, and usage data. This information helps Docker improve and
troubleshoot the application. Clear the check box to opt out. Docker may
periodically prompt you for more information.
- **Show weekly tips**. Select to display useful advice and suggestions about
using Docker.
- **Open Docker Desktop dashboard at startup**. Select to automatically open the
dashboard when starting Docker Desktop.
- **Use Docker Compose V2**. Select to enable the `docker-compose` command to
use Docker Compose V2. For more information, see [Docker Compose V2](../../compose/index.md#compose-v2-and-the-new-docker-compose-command).
## Resources
The **Resources** tab allows you to configure CPU, memory, disk, proxies,
network, and other resources.
Different settings are available for configuration depending on whether you are
using Linux containers in WSL 2 mode, Linux containers in Hyper-V mode, or Windows
containers.
### Advanced
> **Note**
>
> The Advanced tab is only available in Hyper-V mode, because Windows manages
> the resources in WSL 2 mode and Windows container mode. In WSL 2
> mode, you can configure limits on the memory, CPU, and swap size allocated
> to the [WSL 2 utility VM](https://docs.microsoft.com/en-us/windows/wsl/wsl-config#configure-global-options-with-wslconfig){:target="_blank"
class="_"}.
On the **Advanced** tab, you can limit resources available to Docker.
Advanced settings are:
- **CPUs**. By default, Docker Desktop is set to use half the number of processors
available on the host machine. To increase processing power, set this to a
higher number; to decrease, lower the number.
- **Memory**. By default, Docker Desktop is set to use `2` GB of your host's
memory. To increase the RAM, set this to a higher number; to decrease it,
lower the number.
- **Swap**. Configure swap file size as needed. The default is 1 GB.
- **Disk image size**. Specify the size of the disk image.
- **Disk image location**. Specify the location of the Linux volume where containers and images are stored.
You can also move the disk image to a different location. If you attempt to move a disk image to a location that already has one, you are asked if you want to use the existing image or replace it.
### File sharing
> **Note**
>
> The File sharing tab is only available in Hyper-V mode because the files
> are automatically shared in WSL 2 mode and Windows container mode.
Use File sharing to allow local directories on your machine to be shared with
Linux containers. This is especially useful for editing source code in an IDE on
the host while running and testing the code in a container.
Note that configuring file sharing is not necessary for Windows containers,
only [Linux containers](../windows/index.md#switch-between-windows-and-linux-containers).
If a directory is not shared with a Linux container you may get `file not found`
or `cannot start service` errors at runtime. See [Volume mounting requires shared folders for Linux containers](../windows/troubleshoot.md#volume-mounting-requires-shared-folders-for-linux-containers).
File share settings are:
- **Add a Directory**. Click `+` and navigate to the directory you want to add.
- **Remove a Directory**. Click `-` next to the directory you want to remove
- **Apply & Restart** makes the directory available to containers using Docker's
bind mount (`-v`) feature.
> Tips on shared folders, permissions, and volume mounts
>
> * Share only the directories that you need with the container. File sharing
> introduces overhead as any changes to the files on the host need to be notified
> to the Linux VM. Sharing too many files can lead to high CPU load and slow
> filesystem performance.
> * Shared folders are designed to allow application code to be edited
> on the host while being executed in containers. For non-code items
> such as cache directories or databases, the performance will be much
> better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md)
> (named volume) or [data container](../../storage/volumes.md).
> * Docker Desktop sets permissions to read/write/execute for users, groups and
> others [0777 or a+rwx](http://permissions-calculator.org/decode/0777/).
> This is not configurable. See [Permissions errors on data directories for shared volumes](../windows/troubleshoot.md#permissions-errors-on-data-directories-for-shared-volumes).
> * Windows presents a case-insensitive view of the filesystem to applications while Linux is case-sensitive.
> On Linux, it is possible to create two separate files: `test` and `Test`,
> while on Windows these filenames would actually refer to the same underlying
> file. This can lead to problems where an app works correctly on a developer's
> machine (where the file contents are shared) but fails when run in Linux in
> production (where the file contents are distinct). To avoid this, Docker Desktop
> insists that all shared files are accessed as their original case. Therefore,
> if a file is created called `test`, it must be opened as `test`. Attempts to
> open `Test` will fail with the error "No such file or directory". Similarly,
> once a file called `test` is created, attempts to create a second file called
> `Test` will fail.
#### Shared folders on demand
You can share a folder "on demand" the first time a particular folder is used by a container.
If you run a Docker command from a shell with a volume mount (as shown in the
example below) or kick off a Compose file that includes volume mounts, you get a
popup asking if you want to share the specified folder.
You can select to **Share it**, in which case it is added to your Docker Desktop Shared Folders list and available to
containers. Alternatively, you can opt not to share it by selecting **Cancel**.
![Shared folder on demand](../images/shared-folder-on-demand.png){:width="600px"}
### Proxies
HTTP/HTTPS proxies can be used when:
- Logging in to Docker
- Pulling or pushing images
- Fetching artifacts during image builds
- Containers interact with the external network
- Scanning images
Each use case above is configured slightly differently.
If the host uses a static HTTP/HTTPS proxy configuration, Docker Desktop reads this configuration
and automatically uses these settings for logging into Docker and for pulling and pushing images.
If the host uses a more sophisticated HTTP/HTTPS configuration, enable **Manual proxy configuration** and enter a single upstream proxy URL
of the form `http://username:password@proxy:port`.
The HTTP/HTTPS proxy settings used for fetching artifacts during builds and for running containers
are set via the `.docker/config.json` file, see [Configure the Docker client](../../network/proxy.md#configure-the-docker-client).
The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY` environment variable.
### Network
> **Note**
>
> The Network tab is not available in the Windows container mode because
> Windows manages networking.
You can configure Docker Desktop networking to work on a virtual private network (VPN). Specify a network address translation (NAT) prefix and subnet mask to enable Internet connectivity.
### WSL Integration
In WSL 2 mode, you can configure which WSL 2 distributions will have the Docker
WSL integration.
By default, the integration is enabled on your default WSL distribution.
To change your default WSL distro, run `wsl --set-default <distro name>`. (For example,
to set Ubuntu as your default WSL distro, run `wsl --set-default ubuntu`).
You can also select any additional distributions you would like to enable the WSL 2 integration on.
For more details on configuring Docker Desktop to use WSL 2, see
[Docker Desktop WSL 2 backend](../windows/wsl.md).
## Docker Engine
The **Docker Engine** tab allows you to configure the Docker daemon to determine how your containers run.
Type a JSON configuration file in the box to configure the daemon settings. For a full list of options, see the Docker Engine
[dockerd commandline reference](/engine/reference/commandline/dockerd/){:target="_blank" rel="noopener" class="_"}.
Click **Apply & Restart** to save your settings and restart Docker Desktop.
## Experimental features
{% include experimental.md %}
From the **Experimental features** tab, you can sign up to the [Developer Preview program](https://www.docker.com/community/get-involved/developer-preview/).
## Kubernetes
> **Note**
>
> The **Kubernetes** tab is not available in Windows container mode.
Docker Desktop includes a standalone Kubernetes server, so that you can test
deploying your Docker workloads on Kubernetes. To enable Kubernetes support and
install a standalone instance of Kubernetes running as a Docker container,
select **Enable Kubernetes**.
Select **Show system containers (advanced)** to view internal containers when
using Docker commands.
Select **Reset Kubernetes cluster** to delete all stacks and Kubernetes resources.
For more information about using the Kubernetes integration with Docker Desktop,
see [Deploy on Kubernetes](../kubernetes.md){:target="_blank" rel="noopener" class="_"}.
## Software Updates
The **Software Updates** tab notifies you of any updates available to Docker Desktop.
When there's a new update, you can choose to download the update right away, or
click the **Release Notes** option to learn what's included in the updated version.
Turn off the check for updates by clearing the **Automatically check for updates**
check box. This disables notifications in the Docker menu and the notification
badge that appears on the Docker Dashboard. To check for updates manually, select
the **Check for updates** option in the Docker menu.
To allow Docker Desktop to automatically download new updates in the background,
select **Always download updates**. This downloads newer versions of Docker Desktop
when an update becomes available. After downloading the update, click
**Apply and Restart** to install the update. You can do this either through the
Docker menu or in the **Updates** section in the Docker Dashboard.
## Extensions
Use the **Extensions** tab to:
- **Enable Docker Extensions**
- **Allow only extensions distributed through the Docker Marketplace**
- **Show Docker Extensions system containers**
For more information about Docker extensions, see [Extensions](../extensions.md).

8
desktop/windows/index.md
View File

@ -53,9 +53,9 @@ For more information on Windows containers, refer to the following documentation
> When you switch to Windows containers, the Settings dialog only shows those tabs that are active and apply to your Windows containers:
>
* [General](../settings/windows-settings.md#general)
* [Proxies](../settings/windows-settings.md#proxies)
* [Daemon](../settings/windows-settings.md#docker-engine)
* [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,
@ -145,7 +145,7 @@ You need to restart Docker Desktop after making any changes to the keychain
or to the `~/.docker/certs.d` directory in order for the changes to take effect.
The registry cannot be listed as an _insecure registry_ (see
[Docker Daemon](../settings/windows-settings.md#docker-engine)). Docker Desktop ignores
[Docker Daemon](../settings/windows.md#docker-engine)). Docker Desktop ignores
certificates listed under insecure registries, and does not send client
certificates. Commands like `docker run` that attempt to pull from the registry
produce error messages on the command line, as well as on the registry.

6
desktop/windows/troubleshoot.md
View File

@ -28,7 +28,7 @@ The Troubleshoot page contains the following options:
* **Support**: Users with a paid Docker subscription can use this option to send a support request. Other users can use this option to diagnose any issues in Docker Desktop. For more information, see [Diagnose and feedback](#diagnose-and-feedback) and [Support](../../support/index.md).
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../settings/windows-settings.md#kubernetes).
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../settings/windows.md#kubernetes).
* **Clean / Purge data**: Select this option to delete container and image data. Choose whether you'd like to delete data from Hyper-V, WSL 2, or Windows Containers and then click **Delete** to confirm.
@ -131,7 +131,7 @@ Getting Started topic.
#### Permissions errors on data directories for shared volumes
When sharing files from Windows, Docker Desktop sets permissions on [shared volumes](../settings/windows-settings.md#file-sharing)
When sharing files from Windows, Docker Desktop sets permissions on [shared volumes](../settings/windows.md#file-sharing)
to a default value of [0777](http://permissions-calculator.org/decode/0777/)
(`read`, `write`, `execute` permissions for `user` and for `group`).
@ -150,7 +150,7 @@ in the FAQs.
If you are using mounted volumes and get runtime errors indicating an
application file is not found, access is denied to a volume mount, or a service
cannot start, such as when using [Docker Compose](../../compose/gettingstarted.md),
you might need to enable [shared folders](../settings/windows-settings.md#file-sharing).
you might need to enable [shared folders](../settings/windows.md#file-sharing).
With the Hyper-V backend, mounting files from Windows requires shared folders for Linux containers. Click ![whale menu](images/whale-x.png){: .inline}
and then **Settings** > **Shared Folders** and share the folder that contains the

2
network/proxy.md
View File

@ -7,7 +7,7 @@ keywords: network, networking, proxy, client
> **Note**
>
> This page describes how to configure the Docker CLI to configure proxies via environment variables in containers.
> For information on configuring Docker Desktop to use HTTP/HTTPS proxies, see [proxies on Mac](../desktop/settings/mac-settings.md#proxies), [proxies on Windows](../desktop/settings/windows-settings.md#proxies), and [proxies on Linux](../desktop/settings/linux-settings.md#proxies).
> For information on configuring Docker Desktop to use HTTP/HTTPS proxies, see [proxies on Mac](../desktop/settings/mac.md#proxies), [proxies on Windows](../desktop/settings/windows.md#proxies), and [proxies on Linux](../desktop/settings/linux.md#proxies).
> If you are not running Docker Desktop, and have installed the Docker Engine in
> other ways, refer to the "HTTP/HTTPS proxy" section in

8
samples/aspnet-mssql-compose.md
View File

@ -27,8 +27,8 @@ configure this app to use our SQL Server database, and then create a
1. Create a new directory for your application.
This directory is the context of your docker-compose project. For
[Docker Desktop for Windows](../desktop/settings/windows-settings.md#file-sharing) and
[Docker Desktop for Mac](../desktop/settings/mac-settings.md#file-sharing), you
[Docker Desktop for Windows](../desktop/settings/windows.md#file-sharing) and
[Docker Desktop for Mac](../desktop/settings/mac.md#file-sharing), you
need to set up file sharing for the volume that you need to map.
1. Within your directory, use the `dotnet:2.1-sdk` Docker image to generate a
@ -176,8 +176,8 @@ configure this app to use our SQL Server database, and then create a
1. Make sure you allocate at least 2GB of memory to Docker Engine. Here is how
to do it on
[Docker Desktop for Mac](../desktop/settings/mac-settings.md#advanced) and
[Docker Desktop for Windows](../desktop/settings/windows-settings.md#advanced).
[Docker Desktop for Mac](../desktop/settings/mac.md#advanced) and
[Docker Desktop for Windows](../desktop/settings/windows.md#advanced).
This is necessary to run the SQL Server on Linux container.
1. Run the `docker-compose up` command. After a few seconds, you should be able