From 5d4eeb58de18568682774d1abd8c0a9daeb60549 Mon Sep 17 00:00:00 2001 From: aevesdocker Date: Mon, 9 Sep 2024 13:38:25 +0100 Subject: [PATCH] consolidate settings --- .../get-started/workshop/06_bind_mounts.md | 5 +- content/includes/beta.md | 5 - content/includes/desktop-builders-setting.md | 63 --- content/includes/desktop-experimental.md | 3 - content/includes/desktop-network-setting.md | 1 - .../desktop-notifications-settings.md | 9 - content/manuals/build/builders/manage.md | 6 +- content/manuals/desktop/faqs/windowsfaqs.md | 4 +- .../manuals/desktop/install/linux-install.md | 2 +- .../manuals/desktop/install/mac-install.md | 2 +- .../desktop/mac/permission-requirements.md | 2 +- content/manuals/desktop/networking.md | 5 +- .../desktop/previous-versions/2.x-windows.md | 2 +- .../previous-versions/edge-releases-mac.md | 4 +- content/manuals/desktop/release-notes.md | 14 +- .../desktop/{settings/mac.md => settings.md} | 248 ++++++++++-- content/manuals/desktop/settings/_index.md | 5 - content/manuals/desktop/settings/linux.md | 276 ------------- content/manuals/desktop/settings/windows.md | 375 ------------------ .../manuals/desktop/troubleshoot/overview.md | 2 +- .../manuals/desktop/troubleshoot/topics.md | 6 +- content/manuals/desktop/use-desktop/builds.md | 6 +- content/manuals/desktop/wsl/_index.md | 2 +- content/manuals/engine/cli/proxy.md | 5 +- content/manuals/engine/daemon/_index.md | 6 +- .../registry-access-management.md | 2 +- data/redirects.yml | 2 +- 27 files changed, 233 insertions(+), 829 deletions(-) delete mode 100644 content/includes/beta.md delete mode 100644 content/includes/desktop-builders-setting.md delete mode 100644 content/includes/desktop-experimental.md delete mode 100644 content/includes/desktop-network-setting.md delete mode 100644 content/includes/desktop-notifications-settings.md rename content/manuals/desktop/{settings/mac.md => settings.md} (55%) delete mode 100644 content/manuals/desktop/settings/_index.md delete mode 100644 content/manuals/desktop/settings/linux.md delete mode 100644 content/manuals/desktop/settings/windows.md diff --git a/content/get-started/workshop/06_bind_mounts.md b/content/get-started/workshop/06_bind_mounts.md index 8c4ca7e1845d..1b89b210207c 100644 --- a/content/get-started/workshop/06_bind_mounts.md +++ b/content/get-started/workshop/06_bind_mounts.md @@ -50,10 +50,7 @@ work. 1. Verify that your `getting-started-app` directory is in a directory defined in Docker Desktop's file sharing setting. This setting defines which parts of your -filesystem you can share with containers. For details about accessing the -setting, see the topic for [Mac](/manuals/desktop/settings/mac.md#file-sharing), -[Windows](/manuals/desktop/settings/windows.md#file-sharing), or -[Linux](/manuals/desktop/settings/linux.md#file-sharing). +filesystem you can share with containers. For details about accessing the setting, see [File sharing](/manuals/desktop/settings.md#file-sharing). 2. Open a terminal and change directory to the `getting-started-app` directory. diff --git a/content/includes/beta.md b/content/includes/beta.md deleted file mode 100644 index b3d94642f2ea..000000000000 --- a/content/includes/beta.md +++ /dev/null @@ -1,5 +0,0 @@ -Beta features provide access to future product functionality. -These features are intended for testing and feedback only as they may change -between releases without warning or remove them entirely from a future -release. Beta features must not be used in production environments. -Docker doesn't offer support for beta features. diff --git a/content/includes/desktop-builders-setting.md b/content/includes/desktop-builders-setting.md deleted file mode 100644 index 45e135be255f..000000000000 --- a/content/includes/desktop-builders-setting.md +++ /dev/null @@ -1,63 +0,0 @@ -If you have turned on the -[Docker Desktop Builds view](/desktop/use-desktop/builds/), you can use the -**Builders** tab to inspect and manage builders in the Docker Desktop settings. - -### Inspect - -To inspect builders, find the builder that you want to inspect and select the -expand icon. You can only inspect active builders. - -Inspecting an active builder shows: - -- BuildKit version -- Status -- Driver type -- Supported capabilities and platforms -- Disk usage -- Endpoint address - -### Select a different builder - -The **Selected builder** section displays the selected builder. -To select a different builder: - -1. Find the builder that you want to use under **Available builders** -2. Open the drop-down menu next to the builder's name. -3. Select **Use** to switch to this builder. - -Your build commands now use the selected builder by default. - -### Create a builder - -To create a builder, use the Docker CLI. See -[Create a new builder](/build/builders/manage/#create-a-new-builder) - -### Remove a builder - -You can remove a builder if: - -- The builder isn't your [selected builder](/build/builders/#selected-builder) -- The builder isn't [associated with a Docker context](/build/builders/#default-builder). - - To remove builders associated with a Docker context, remove the context using - the `docker context rm` command. - -To remove a builder: - -1. Find the builder that you want to remove under **Available builders** -2. Open the drop-down menu. -3. Select **Remove** to remove this builder. - -If the builder uses the `docker-container` or `kubernetes` driver, -the build cache is also removed, along with the builder. - -### Stop and start a builder - -Builders that use the -[`docker-container` driver](/build/builders/drivers/docker-container/) -run the BuildKit daemon in a container. -You can start and stop the BuildKit container using the drop-down menu. - -Running a build automatically starts the container if it's stopped. - -You can only start and stop builders using the `docker-container` driver. diff --git a/content/includes/desktop-experimental.md b/content/includes/desktop-experimental.md deleted file mode 100644 index f2f772bfe636..000000000000 --- a/content/includes/desktop-experimental.md +++ /dev/null @@ -1,3 +0,0 @@ -On the **Experimental features** tab, you have the option to allow feature flags. These are features that Docker is currently experimenting with. This is switched on by default. - -These features are intended for testing and feedback only as they may change between releases without warning or remove them entirely from a future release. Docker doesn't offer support for experimental features. diff --git a/content/includes/desktop-network-setting.md b/content/includes/desktop-network-setting.md deleted file mode 100644 index 6b325622be62..000000000000 --- a/content/includes/desktop-network-setting.md +++ /dev/null @@ -1 +0,0 @@ -Docker Desktop uses a private IPv4 network for internal services such as a DNS server and an HTTP proxy. In case Docker Desktop's choice of subnet clashes with IPs in your environment, you can specify a custom subnet using the **Network** setting. diff --git a/content/includes/desktop-notifications-settings.md b/content/includes/desktop-notifications-settings.md deleted file mode 100644 index 0881c26b08fc..000000000000 --- a/content/includes/desktop-notifications-settings.md +++ /dev/null @@ -1,9 +0,0 @@ -Use the **Notifications** tab to turn on or turn off notifications for the following events: - -- **Status updates on tasks and processes** -- **Docker announcements** -- **Docker surveys** - -By default, all notifications are turned on. You'll always receive error notifications and notifications about new Docker Desktop releases and updates. - -Notifications momentarily appear in the lower-right of the Docker Dashboard and then move to the **Notifications** drawer. To open the **Notifications** drawer, select {{< inline-image src="../images/notifications.svg" alt="notifications" >}}. diff --git a/content/manuals/build/builders/manage.md b/content/manuals/build/builders/manage.md index e73c1a092471..306ed098df49 100644 --- a/content/manuals/build/builders/manage.md +++ b/content/manuals/build/builders/manage.md @@ -123,8 +123,4 @@ It only removes your connection to the builder. If you have turned on the [Docker Desktop Builds view](/manuals/desktop/use-desktop/builds.md), -you can inspect builders in Docker Desktop settings. See: - -- [Change settings, Windows](/manuals/desktop/settings/windows.md#builders) -- [Change settings, Mac](/manuals/desktop/settings/mac.md#builders) -- [Change settings, Linux](/manuals/desktop/settings/linux.md#builders) +you can inspect builders in [Docker Desktop settings](/manuals/desktop/settings.md#builders). diff --git a/content/manuals/desktop/faqs/windowsfaqs.md b/content/manuals/desktop/faqs/windowsfaqs.md index d781a27f0eb3..0a048b8d9796 100644 --- a/content/manuals/desktop/faqs/windowsfaqs.md +++ b/content/manuals/desktop/faqs/windowsfaqs.md @@ -20,7 +20,7 @@ No, running Docker Desktop on Windows Server is not supported. ### 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.md#file-sharing) for +the Unix-style permissions on [shared volumes](/manuals/desktop/settings.md#file-sharing) for deployed containers, but rather sets permissions to a default value of [0777](https://chmodcommand.com/chmod-0777/) (`read`, `write`, `execute` permissions for `user` and for @@ -69,7 +69,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.md#docker-engine)). Docker Desktop ignores +[Docker Daemon](/manuals/desktop/settings.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. diff --git a/content/manuals/desktop/install/linux-install.md b/content/manuals/desktop/install/linux-install.md index 4f093f811c40..9a17f357b34d 100644 --- a/content/manuals/desktop/install/linux-install.md +++ b/content/manuals/desktop/install/linux-install.md @@ -38,7 +38,7 @@ Docker Desktop for Linux provides a user-friendly graphical interface that simpl 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 +controls to restrict [its resources](/manuals/desktop/settings.md#resources). Using a dedicated storage location for Docker Desktop prevents it from interfering with a Docker Engine installation on the same machine. diff --git a/content/manuals/desktop/install/mac-install.md b/content/manuals/desktop/install/mac-install.md index 76b0a421cec9..0a3bb4412bb9 100644 --- a/content/manuals/desktop/install/mac-install.md +++ b/content/manuals/desktop/install/mac-install.md @@ -87,7 +87,7 @@ This page contains download URLs, information about system requirements, and ins 6. From the installation window, select either: - **Use recommended settings (Requires password)**. This lets Docker Desktop automatically set the necessary configuration settings. - - **Use advanced settings**. You can then set the location of the Docker CLI tools either in the system or user directory, enable the default Docker socket, and enable privileged port mapping. See [Settings](../settings/mac.md#advanced), for more information and how to set the location of the Docker CLI tools. + - **Use advanced settings**. You can then set the location of the Docker CLI tools either in the system or user directory, enable the default Docker socket, and enable privileged port mapping. See [Settings](/manuals/desktop/settings.md#advanced), for more information and how to set the location of the Docker CLI tools. 7. Select **Finish**. If you have applied any of the previous configurations that require a password in step 6, enter your password to confirm your choice. ### Install from the command line diff --git a/content/manuals/desktop/mac/permission-requirements.md b/content/manuals/desktop/mac/permission-requirements.md index 5614552ed19f..8c412b0518e4 100644 --- a/content/manuals/desktop/mac/permission-requirements.md +++ b/content/manuals/desktop/mac/permission-requirements.md @@ -62,7 +62,7 @@ The Docker binaries are installed by default in `/Applications/Docker.app/Conten With version 4.18 and later, you can choose whether to install symlinks either in `/usr/local/bin` or `$HOME/.docker/bin` during installation of Docker Desktop. -If `/usr/local/bin` is chosen, and this location is not writable by unprivileged users, Docker Desktop requires authorization to confirm this choice before the symlinks to Docker binaries are created in `/usr/local/bin`. If `$HOME/.docker/bin` is chosen, authorization is not required, but then you must [manually add `$HOME/.docker/bin`](../settings/mac.md#advanced) to their PATH. +If `/usr/local/bin` is chosen, and this location is not writable by unprivileged users, Docker Desktop requires authorization to confirm this choice before the symlinks to Docker binaries are created in `/usr/local/bin`. If `$HOME/.docker/bin` is chosen, authorization is not required, but then you must [manually add `$HOME/.docker/bin`](/manuals/desktop/settings.md#advanced) to their PATH. You are also given the option to enable the installation of the `/var/run/docker.sock` symlink. Creating this symlink ensures various Docker clients relying on the default Docker socket path work without additional changes. diff --git a/content/manuals/desktop/networking.md b/content/manuals/desktop/networking.md index caa85cc2b3e6..b4c2a0ad9d98 100644 --- a/content/manuals/desktop/networking.md +++ b/content/manuals/desktop/networking.md @@ -45,10 +45,7 @@ syntax for `-p` is `HOST_PORT:CLIENT_PORT`. ### HTTP/HTTPS Proxy support -See: -- [Proxies on Linux](settings/linux.md#proxies) -- [Proxies on Mac](settings/mac.md#proxies) -- [Proxies on Windows](settings/windows.md#proxies) +See [Proxies](/manuals/desktop/settings.md#proxies) ### SOCKS5 proxy support diff --git a/content/manuals/desktop/previous-versions/2.x-windows.md b/content/manuals/desktop/previous-versions/2.x-windows.md index 7fd5cef90169..7a116e5764c4 100644 --- a/content/manuals/desktop/previous-versions/2.x-windows.md +++ b/content/manuals/desktop/previous-versions/2.x-windows.md @@ -318,7 +318,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.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](/manuals/desktop/settings.md#file-sharing). ### Known issues diff --git a/content/manuals/desktop/previous-versions/edge-releases-mac.md b/content/manuals/desktop/previous-versions/edge-releases-mac.md index fb1e85f8fcaf..f48efeecb081 100644 --- a/content/manuals/desktop/previous-versions/edge-releases-mac.md +++ b/content/manuals/desktop/previous-versions/edge-releases-mac.md @@ -1560,9 +1560,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.md#docker-engine). +- Dedicated preference pane for advanced configuration of the docker daemon (edit daemon.json). See [Daemon Advanced (JSON configuration file)](/manuals/desktop/settings.md#docker-engine). -- Docker Experimental mode can be toggled. See [Daemon Basic (experimental mode and registries)](../settings/mac.md#docker-engine). +- Docker Experimental mode can be toggled. See [Daemon Basic (experimental mode and registries)](/manuals/desktop/settings.md#docker-engine). **Upgrades** diff --git a/content/manuals/desktop/release-notes.md b/content/manuals/desktop/release-notes.md index 3d1d2288e18c..592f40304dc2 100644 --- a/content/manuals/desktop/release-notes.md +++ b/content/manuals/desktop/release-notes.md @@ -363,7 +363,7 @@ For more information, see [microsoft/WSL#11794](https://github.com/microsoft/WSL #### For Windows -- Added support for [Kerberos and NTLM proxy authentication](settings/windows.md#proxy-authentication) on Windows. Requires a Business subscription. +- Added support for [Kerberos and NTLM proxy authentication](/manuals/desktop/settings.md#proxy-authentication) on Windows. Requires a Business subscription. ### Upgrades @@ -861,7 +861,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st ### New -- Rosetta is now Generally Available for all users on macOS 13 or later. It provides faster emulation of Intel-based images on Apple Silicon. To use Rosetta, see [Settings](settings/mac.md). Rosetta is enabled by default on macOS 14.1 and later. +- Rosetta is now Generally Available for all users on macOS 13 or later. It provides faster emulation of Intel-based images on Apple Silicon. To use Rosetta, see [Settings](/manuals/desktop/settings.md). Rosetta is enabled by default on macOS 14.1 and later. - Docker Desktop now detects if a WSL version is out of date. If an out dated version of WSL is detected, you can allow Docker Desktop to automatically update the installation or you can manually update WSL outside of Docker Desktop. - New installations of Docker Desktop for Windows now require a Windows version of 19044 or later. - Administrators now have the ability to control Docker Scout image analysis in [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/configure.md). @@ -922,7 +922,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st #### For Windows -- **Switch to Windows containers** option in the tray menu may not show up on Windows. As a workaround, edit the [`settings.json` file](https://docs.docker.com/desktop/settings/windows/) and set `"displaySwitchWinLinContainers": true`. +- **Switch to Windows containers** option in the tray menu may not show up on Windows. As a workaround, edit the [`settings.json` file](/manuals/desktop/settings.md) and set `"displaySwitchWinLinContainers": true`. #### For all platforms @@ -1150,13 +1150,13 @@ This can be resolved by adding the user to the **docker-users** group. Before st #### For Mac - Fixed a bug that prevented Docker Desktop from starting. [docker/for-mac#6890](https://github.com/docker/for-mac/issues/6890) -- Resource Saver is now available on Mac. It optimises Docker Desktop's usage of your system resources when no containers are running. To access this feature, make sure you have [turned on access to experimental features](settings/mac.md) in settings. +- Resource Saver is now available on Mac. It optimises Docker Desktop's usage of your system resources when no containers are running. To access this feature, make sure you have [turned on access to experimental features](/manuals/desktop/settings.md) in settings. #### For Windows - Fixed a bug where the self-diagnose tool showed a false-positive failure when vpnkit is expected to be not running. Fixes [docker/for-win#13479](https://github.com/docker/for-win/issues/13479). - Fixed a bug where an invalid regular expression in the search bar caused an error. Fixes [docker/for-win#13592](https://github.com/docker/for-win/issues/13592). -- Resource Saver is now available on Windows Hyper-V. It optimises Docker Desktop's usage of your system resources when no containers are running. To access this feature, make sure you have [turned on access to experimental features](settings/windows.md) in settings. +- Resource Saver is now available on Windows Hyper-V. It optimises Docker Desktop's usage of your system resources when no containers are running. To access this feature, make sure you have [turned on access to experimental features](/manuals/desktop/settings.md) in settings. ## 4.21.1 @@ -1268,7 +1268,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st - Fixed a bug that meant WSL data could not be moved to a different disk. Fixes [docker/for-win#13269](https://github.com/docker/for-win/issues/13269). - Fixed a bug where Docker Desktop was not stopping its WSL distros (docker-desktop and docker-desktop-data) when it was shutdown, consuming host memory unnecessarily. -- Added a new setting that allows the Windows Docker daemon to use Docker Desktop's internal proxy when running Windows containers. See [Windows proxy settings](settings/windows.md#proxies). +- Added a new setting that allows the Windows Docker daemon to use Docker Desktop's internal proxy when running Windows containers. See [Windows proxy settings](/manuals/desktop/settings.md#proxies). #### For Linux @@ -2297,7 +2297,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st #### 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.md#beta-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](/manuals/desktop/settings.md#beta-features). ### Updates diff --git a/content/manuals/desktop/settings/mac.md b/content/manuals/desktop/settings.md similarity index 55% rename from content/manuals/desktop/settings/mac.md rename to content/manuals/desktop/settings.md index 3162df9c26ea..4fe6d71776c5 100644 --- a/content/manuals/desktop/settings/mac.md +++ b/content/manuals/desktop/settings.md @@ -1,23 +1,23 @@ --- -description: Change your Docker Desktop settings on Mac +description: Learn about and change Docker Desktop's settings keywords: settings, preferences, proxy, file sharing, resources, kubernetes, Docker - Desktop, Mac -title: Change Docker Desktop settings on Mac + Desktop, Linux, Mac, Windows +title: Change your Docker Desktop settings aliases: -- /docker-for-mac/mutagen-caching/ -- /docker-for-mac/mutagen/ -- /docker-for-mac/osxfs-caching/ -- /docker-for-mac/osxfs/ + - /desktop/settings/mac/ + - /desktop/settings/windows/ + - /desktop/settings/linux/ --- -This page provides information on how to configure and manage your Docker Desktop for Mac settings. - To navigate to **Settings** either: -- Select the Docker menu {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}} and then **Settings** +- Select the Docker menu {{< inline-image src="images/whale-x.svg" alt="whale menu" >}} and then **Settings** - Select the **Settings** icon from the Docker Dashboard. -You can also locate the `settings.json` file at `~/Library/Group Containers/group.com.docker/settings.json`. +You can also locate the `settings.json` 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` ## General @@ -32,30 +32,42 @@ On the **General** tab, you can configure when to start Docker and specify other - **Choose theme for Docker Desktop**. Choose whether you want to apply a **Light** or **Dark** theme to Docker Desktop. Alternatively you can set Docker Desktop to **Use system settings**. - **Choose container terminal**. Determines which terminal is launched when opening the terminal from a container. -If you choose the integrated terminal, you can run commands in a running container straight from the Docker Dashboard. For more information, see [Explore containers](../use-desktop/container.md). +If you choose the integrated terminal, you can run commands in a running container straight from the Docker Dashboard. For more information, see [Explore containers](/manuals/desktop/use-desktop/container.md). + +- **Enable Docker terminal**. Interact with your host machine and execute commands directly from Docker Desktop. -- **Enable Docker Debug by default**. Check this option to use Docker Debug by default when accessing the integrated terminal. For more information, see [Explore containers](../use-desktop/container.md#integrated-terminal). +- **Enable Docker Debug by default**. Check this option to use Docker Debug by default when accessing the integrated terminal. For more information, see [Explore containers](/manuals/desktop/use-desktop/container.md#integrated-terminal). -- **Include VM in Time Machine backups**. Select to back up the Docker Desktop +- {{< badge color=blue text="Mac only" >}}**Include VM in Time Machine backups**. Select to back up the Docker Desktop virtual machine. This option is turned off by default. +- {{< badge color=blue text="Windows only" >}}**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. + +- {{< badge color=blue text="Windows only" >}}**Use the WSL 2 based engine**. WSL 2 provides better performance than the + Hyper-V backend. For more information, see [Docker Desktop WSL 2 backend](/manuals/desktop/wsl/index.md). + +- {{< badge color=blue text="Windows only" >}}**Add the `*.docker.internal` names to the host's `/etc/hosts` file (Password required)**. Lets you resolve `*.docker.internal` DNS names from both the host and your containers. + - **Use containerd for pulling and storing images**. Turns on the containerd image store. This brings new features like faster container startup performance by lazy-pulling images, and the ability to run Wasm applications with Docker. - For more information, see [containerd image store](../containerd.md). + For more information, see [containerd image store](containerd.md). -- **Use Virtualization framework**. Select to allow Docker Desktop to use the `virtualization.framework` instead of the `hypervisor.framework`. +- {{< badge color=blue text="Mac only" >}} **Use Virtualization framework**. Select to allow Docker Desktop to use the `virtualization.framework` instead of the `hypervisor.framework`. > [!TIP] > > Turn this setting on to make Docker Desktop run faster. -- **Choose file sharing implementation for your containers**. Choose whether you want to share files using **VirtioFS**, **gRPC FUSE**, or **osxfs**. VirtioFS is only available for macOS versions 12.5 and above, and is turned on by default. +- {{< badge color=blue text="Mac only" >}}**Choose file sharing implementation for your containers**. Choose whether you want to share files using **VirtioFS**, **gRPC FUSE**, or **osxfs (Legacy)**. VirtioFS is only available for macOS versions 12.5 and above, and is turned on by default. >**Tip** > > Use VirtioFS for speedy file sharing. VirtioFS has reduced the time taken to complete filesystem operations by [up to 98%](https://github.com/docker/roadmap/issues/7#issuecomment-1044452206) -- **Use Rosetta for x86_64/amd64 emulation on Apple Silicon**. Turns on Rosetta to accelerate x86/AMD64 binary emulation on Apple Silicon. This option is only available if you have turned on **Virtualization framework** in the **General** settings tab. You must also be on macOS Ventura or later. +- {{< badge color=blue text="Mac only" >}}**Use Rosetta for x86_64/amd64 emulation on Apple Silicon**. Turns on Rosetta to accelerate x86/AMD64 binary emulation on Apple Silicon. This option is only available if you have turned on **Virtualization framework** in the **General** settings tab. You must also be on macOS Ventura or later. - **Send usage statistics**. Select so Docker Desktop sends diagnostics, crash reports, and usage data. This information helps Docker improve and @@ -63,7 +75,7 @@ If you choose the integrated terminal, you can run commands in a running contain periodically prompt you for more information. - **Use Enhanced Container Isolation**. Select to enhance security by preventing containers from breaching the Linux VM. For more information, see [Enhanced Container Isolation](/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/index.md). - >**Note** + > [!NOTE] > > This setting is only available if you are signed in to Docker Desktop and have a Docker Business subscription. @@ -73,14 +85,14 @@ If you choose the integrated terminal, you can run commands in a running contain - **Enable background SBOM indexing**. When this option is enabled, Docker Scout automatically analyzes images that you build or pull. -- **Automatically check configuration**. Regularly checks your configuration to ensure no unexpected changes have been made by another application. +- {{< badge color=blue text="Mac only" >}}**Automatically check configuration**. Regularly checks your configuration to ensure no unexpected changes have been made by another application. Docker Desktop checks if your setup, configured during installation, has been altered by external apps like Orbstack. Docker Desktop checks: - The symlinks of Docker binaries to `/usr/local/bin`. - The symlink of the default Docker socket. Additionally, Docker Desktop ensures that the context is switched to `desktop-linux` on startup. - You are notified if changes are found and are able to restore the configuration directly from the notification. For more information, see the [FAQs](../faqs/macfaqs.md#why-do-i-keep-getting-a-notification-telling-me-an-application-has-changed-my-desktop-configurations). + You are notified if changes are found and are able to restore the configuration directly from the notification. For more information, see the [FAQs](/manuals/desktop/faqs/macfaqs.md#why-do-i-keep-getting-a-notification-telling-me-an-application-has-changed-my-desktop-configurations). ## Resources @@ -89,6 +101,13 @@ network, and other resources. ### Advanced +> [!NOTE] +> +> On Windows, the **Resource allocation** options in the **Advanced** tab are 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). + On the **Advanced** tab, you can limit resources available to the Docker Linux VM. Advanced settings are: @@ -110,12 +129,12 @@ Advanced settings are: 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. ->**Tip** +>[!TIP] > > If you feel Docker Desktop starting to get slow or you're running > multi-container workloads, increase the memory and disk image space allocation -- **Resource Saver**. Enable or disable [Resource Saver mode](../use-desktop/resource-saver.md), +- **Resource Saver**. Enable or disable [Resource Saver mode](/manuals/desktop/use-desktop/resource-saver.md), which significantly reduces CPU and memory utilization on the host by automatically turning off the Linux VM when Docker Desktop is idle (i.e., no containers are running). @@ -124,7 +143,7 @@ Advanced settings are: should Docker Desktop be idle before Resource Saver mode kicks in. Default is 5 minutes. - >**Note** + > [!NOTE] > > Exit from Resource Saver mode occurs automatically when containers run. Exit > may take a few seconds (~3 to 10 secs) as Docker Desktop restarts the Linux VM. @@ -132,6 +151,11 @@ Advanced settings are: ### File sharing +> [!NOTE] +> +> On Windows, 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. @@ -140,7 +164,7 @@ the host while running and testing the code in a container. Synchronized file shares is an alternative file sharing mechanism that provides fast and flexible host-to-VM file sharing, enhancing bind mount performance through the use of synchronized filesystem caches. Available with Pro, Team, and Business subscriptions. -To learn more, see [Synchronized file share](../synchronized-file-sharing.md). +To learn more, see [Synchronized file share](/manuals/desktop/synchronized-file-sharing.md). #### Virtual file shares @@ -157,7 +181,7 @@ File share settings are: - **Apply & Restart** makes the directory available to containers using Docker's bind mount (`-v`) feature. -> Tips on shared folders, permissions, and volume mounts +> [!TIP] > > * 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 @@ -183,11 +207,24 @@ File share settings are: > 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`](../troubleshoot/topics.md) +> For more information, see [Volume mounting requires file sharing for any project directories outside of `/Users`](/manuals/desktop/troubleshoot/topics.md) + +#### Shared folders on demand + +On Windows, 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) ### Proxies -Docker Desktop on Mac supports the use of HTTP/HTTPS and [SOCKS5 proxies](../networking.md#socks5-proxy-support). +Docker Desktop supports the use of HTTP/HTTPS and [SOCKS5 proxies](/manuals/desktop/networking.md#socks5-proxy-support). HTTP/HTTPS proxies can be used when: @@ -218,11 +255,56 @@ The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY > > If you are using a PAC file hosted on a web server, make sure to add the MIME type `application/x-ns-proxy-autoconfig` for the `.pac` file extension on the server or website. Without this configuration, the PAC file may not be parsed correctly. +#### Proxy authentication + +##### Basic authentication + +If your proxy uses Basic authentication, Docker Desktop prompts developers for a username and password and caches the credentials. All passwords are stored securely in the OS credential store. It will request re-authentication if that cache is removed. + +It's recommended that you use an `https://` URL for HTTP/HTTPS proxies to protect passwords during network transit. Docker Desktop also supports TLS 1.3 for communication with proxies. + +##### Kerberos and NTLM authentication + +> [!NOTE] +> +> Available for Docker Business subscribers with Docker Desktop for Windows version 4.30 and later. + +Developers are no longer interrupted by prompts for proxy credentials as authentication is centralized. This also reduces the risk of account lockouts due to incorrect sign in attempts. + +If your proxy offers multiple authentication schemes in 407 (Proxy Authentication Required) response, Docker Desktop by default selects the Basic authentication scheme. + +For Docker Desktop version 4.30 to 4.31: + +To enable Kerberos or NTLM proxy authentication, no additional configuration is needed beyond specifying the proxy IP address and port. + +For Docker Desktop version 4.32 and later: + +To enable Kerberos or NTLM proxy authentication you must pass the `--proxy-enable-kerberosntlm` installer flag during installation via the command line, and ensure your proxy server is properly configured for Kerberos or NTLM authentication. + ### Network -{{< include "desktop-network-setting.md" >}} +> [!NOTE] +> +> On Windows, the **Network** tab isn't available in the Windows container mode because +> Windows manages networking. + +Docker Desktop uses a private IPv4 network for internal services such as a DNS server and an HTTP proxy. In case Docker Desktop's choice of subnet clashes with IPs in your environment, you can specify a custom subnet using the **Network** setting. + +On Mac, you can also select the **Use kernel networking for UDP** setting. This lets you use a more efficient kernel networking path for UDP. This may not be compatible with your VPN software. + +### WSL Integration -You can also select the **Use kernel networking for UDP** setting. This lets you use a more efficient kernel networking path for UDP. This may not be compatible with your VPN software. +On Windows 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 `. (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](/manuals/desktop/wsl/index.md). ## Docker Engine @@ -253,10 +335,76 @@ Select **Apply & Restart** to save your settings and restart Docker Desktop. ## Builders -{{< include "desktop-builders-setting.md" >}} +If you have turned on the +[Docker Desktop Builds view](/manuals/desktop/use-desktop/builds.md), you can use the +**Builders** tab to inspect and manage builders in the Docker Desktop settings. + +### Inspect + +To inspect builders, find the builder that you want to inspect and select the +expand icon. You can only inspect active builders. + +Inspecting an active builder shows: + +- BuildKit version +- Status +- Driver type +- Supported capabilities and platforms +- Disk usage +- Endpoint address + +### Select a different builder + +The **Selected builder** section displays the selected builder. +To select a different builder: + +1. Find the builder that you want to use under **Available builders** +2. Open the drop-down menu next to the builder's name. +3. Select **Use** to switch to this builder. + +Your build commands now use the selected builder by default. + +### Create a builder + +To create a builder, use the Docker CLI. See +[Create a new builder](/build/builders/manage/#create-a-new-builder) + +### Remove a builder + +You can remove a builder if: + +- The builder isn't your [selected builder](/build/builders/#selected-builder) +- The builder isn't [associated with a Docker context](/build/builders/#default-builder). + + To remove builders associated with a Docker context, remove the context using + the `docker context rm` command. + +To remove a builder: + +1. Find the builder that you want to remove under **Available builders** +2. Open the drop-down menu. +3. Select **Remove** to remove this builder. + +If the builder uses the `docker-container` or `kubernetes` driver, +the build cache is also removed, along with the builder. + +### Stop and start a builder + +Builders that use the +[`docker-container` driver](/build/builders/drivers/docker-container/) +run the BuildKit daemon in a container. +You can start and stop the BuildKit container using the drop-down menu. + +Running a build automatically starts the container if it's stopped. + +You can only start and stop builders using the `docker-container` driver. ## Kubernetes +> [!NOTE] +> +> On Windows 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 turn on Kubernetes support and install a standalone instance of Kubernetes running as a Docker container, @@ -268,7 +416,7 @@ 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). +see [Deploy on Kubernetes](/manuals/desktop/kubernetes.md). ## Software Updates @@ -305,19 +453,37 @@ You can also sign up to the [Developer Preview program](https://www.docker.com/c ### Beta features -{{< include "beta.md" >}} +Beta features provide access to future product functionality. +These features are intended for testing and feedback only as they may change +between releases without warning or remove them entirely from a future +release. Beta features must not be used in production environments. +Docker doesn't offer support for beta features. ### Experimental features -{{< include "desktop-experimental.md" >}} +Experimental features provide early access to future product functionality. +These features are intended for testing and feedback only as they may change +between releases without warning or can be removed entirely from a future +release. Experimental features must not be used in production environments. +Docker does not offer support for experimental features. + +For a list of current experimental features in the Docker CLI, see [Docker CLI Experimental features](https://github.com/docker/cli/blob/master/experimental/README.md). ## Notifications -{{< include "desktop-notifications-settings.md" >}} +Use the **Notifications** tab to turn on or turn off notifications for the following events: + +- **Status updates on tasks and processes** +- **Docker announcements** +- **Docker surveys** + +By default, all notifications are turned on. You'll always receive error notifications and notifications about new Docker Desktop releases and updates. + +Notifications momentarily appear in the lower-right of the Docker Dashboard and then move to the **Notifications** drawer. To open the **Notifications** drawer, select {{< inline-image src="images/notifications.svg" alt="notifications" >}}. ## Advanced -On the **Advanced** tab, you can reconfigure your initial installation settings: +On Mac, you can reconfigure your initial installation settings on the **Advanced** tab: - **Choose how to configure the installation of Docker's CLI tools**. - **System**: Docker CLI tools are installed in the system directory under `/usr/local/bin` @@ -329,12 +495,8 @@ On the **Advanced** tab, you can reconfigure your initial installation settings: ``` 3. Save and the close the file. Restart your shell to apply the changes to the PATH variable. -- **Enable default Docker socket (Requires password)**. Creates `/var/run/docker.sock` which some third party clients may use to communicate with Docker Desktop. For more information, see [permission requirements for macOS](../mac/permission-requirements.md#installing-symlinks). - -- **Enable privileged port mapping (Requires password)**. Starts the privileged helper process which binds the ports that are between 1 and 1024. For more information, see [permission requirements for macOS](../mac/permission-requirements.md#binding-privileged-ports). - - For more information on each configuration and use case, see [Permission requirements](../mac/permission-requirements.md). - - +- **Enable default Docker socket (Requires password)**. Creates `/var/run/docker.sock` which some third party clients may use to communicate with Docker Desktop. For more information, see [permission requirements for macOS](/manuals/desktop/mac/permission-requirements.md#installing-symlinks). +- **Enable privileged port mapping (Requires password)**. Starts the privileged helper process which binds the ports that are between 1 and 1024. For more information, see [permission requirements for macOS](/manuals/desktop/mac/permission-requirements.md#binding-privileged-ports). + For more information on each configuration and use case, see [Permission requirements](/manuals/desktop/mac/permission-requirements.md). \ No newline at end of file diff --git a/content/manuals/desktop/settings/_index.md b/content/manuals/desktop/settings/_index.md deleted file mode 100644 index e50de9485282..000000000000 --- a/content/manuals/desktop/settings/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -build: - render: never -title: Change settings ---- diff --git a/content/manuals/desktop/settings/linux.md b/content/manuals/desktop/settings/linux.md deleted file mode 100644 index 944d1e37b962..000000000000 --- a/content/manuals/desktop/settings/linux.md +++ /dev/null @@ -1,276 +0,0 @@ ---- -description: Change your Docker Desktop 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 {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}} and then **Settings** -- Select the **Settings** icon from the Docker Dashboard. - -You can also locate the `settings.json` file at `~/.docker/desktop/settings.json`. - -## General - -On the **General** tab, you can configure when to start Docker and specify other settings: - -- **Start Docker Desktop when you sign in to your computer**. Select to automatically start Docker - Desktop when you sign in to your machine. - -- **Open Docker Dashboard when Docker Desktop starts**. Select to automatically open the - dashboard when starting Docker Desktop. - -- **Choose theme for Docker Desktop**. Choose whether you want to apply a **Light** or **Dark** theme to Docker Desktop. Alternatively you can set Docker Desktop to **Use system settings**. - -- **Choose container terminal**. Determines which terminal is launched when opening the terminal from a container. -If you choose the integrated terminal, you can run commands in a running container straight from the Docker Dashboard. For more information, see [Explore containers](../use-desktop/container.md). - -- **Enable Docker Debug by default**. Check this option to use Docker Debug by default when accessing the integrated terminal. For more information, see [Explore containers](../use-desktop/container.md#integrated-terminal). - -- **Use containerd for pulling and storing images**. - Turns on the containerd image store. - This brings new features like faster container startup performance by lazy-pulling images, - and the ability to run Wasm applications with Docker. - For more information, see [containerd image store](../containerd.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. - -- **Use Enhanced Container Isolation**. Select to enhance security by preventing containers from breaching the Linux VM. For more information, see [Enhanced Container Isolation](/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/index.md) - >**Note** - > - > This setting is only available if you are signed in to Docker Desktop and have a Docker Business subscription. - -- **Show CLI hints**. Displays CLI hints and tips when running Docker commands in the CLI. This is turned on by default. To turn CLI hints on or off from the CLI, set `DOCKER_CLI_HINTS` to `true` or `false` respectively. - -- **SBOM Indexing**. When this option is enabled, inspecting an image in Docker Desktop shows a **Start analysis** button that, when selected, analyzes the image with Docker Scout. - -- **Enable background SBOM indexing**. When this option is enabled, Docker Scout automatically analyzes images that you build or pull. - -## Resources - -The **Resources** tab allows you to configure CPU, memory, disk, proxies, -network, and other resources. - -### Advanced - -On the **Advanced** tab, you can limit resources available to the Docker Linux VM. - -Advanced settings are: - -- **CPU limit**. Specify the maximum number of CPUs to be used by Docker Desktop. - By default, Docker Desktop is set to use all the processors available on the host machine. - -- **Memory limit**. By default, Docker Desktop is set to use up to 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. - -- **Virtual disk limit**. Specify the maximum 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. - ->**Tip** -> -> If you feel Docker Desktop starting to get slow or you're running -> multi-container workloads, increase the memory and disk image space allocation - -- **Resource Saver**. Enable or disable [Resource Saver mode](../use-desktop/resource-saver.md), - which significantly reduces CPU and memory utilization on the host by - automatically turning off the Linux VM when Docker Desktop is idle (i.e., no - containers are running). - - You can also configure the Resource Saver timeout which indicates how long - should Docker Desktop be idle before Resource Saver mode kicks in. Default is - 5 minutes. - - >**Note** - > - > Exit from Resource Saver mode occurs automatically when containers run. Exit - > may take a few seconds (~3 to 10 secs) as Docker Desktop restarts the Linux VM. - -### File sharing - -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. - -#### Synchronized file shares - -Synchronized file shares is an alternative file sharing mechanism that provides fast and flexible host-to-VM file sharing, enhancing bind mount performance through the use of synchronized filesystem caches. Available with Pro, Team, and Business subscriptions. - -To learn more, see [Synchronized file share](../synchronized-file-sharing.md). - -#### Virtual file shares - -By default the `/home/` 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**. Select `+` and navigate to the directory you want to add. - -- **Remove a Directory**. Select `-` 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](/manuals/engine/storage/volumes.md) -> (named volume) or [data container](/manuals/engine/storage/volumes.md). - -### Proxies - -Docker Desktop on Linux supports the use of HTTP/HTTPS and [SOCKS5 proxies](../networking.md#socks5-proxy-support). - -HTTP/HTTPS proxies can be used when: - -- Signing in to Docker -- Pulling or pushing images -- Fetching artifacts during image builds -- Containers interact with the external network -- Scanning images - -If the host uses a HTTP/HTTPS proxy configuration (static or via Proxy Auto-Configuration (PAC)), Docker Desktop reads -this configuration -and automatically uses these settings for signing in to Docker, for pulling and pushing images, and for -container Internet access. If the proxy requires authorization then Docker Desktop dynamically asks -the developer for a username and password. All passwords are stored securely in the OS credential store. -Note that only the `Basic` proxy authentication method is supported so we recommend using an `https://` -URL for your HTTP/HTTPS proxies to protect passwords while in transit on the network. Docker Desktop -supports TLS 1.3 when communicating with proxies. - -To set a different proxy for Docker Desktop, turn on **Manual proxy configuration** and enter a single -upstream proxy URL of the form `http://proxy:port` or `https://proxy:port`. - -To prevent developers from accidentally changing the proxy settings, see -[Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/index.md#what-features-can-i-configure-with-settings-management). - -The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY` environment variable. - -> [!NOTE] -> -> If you are using a PAC file hosted on a web server, make sure to add the MIME type `application/x-ns-proxy-autoconfig` for the `.pac` file extension on the server or website. Without this configuration, the PAC file may not be parsed correctly. - -### Network - -{{< include "desktop-network-setting.md" >}} - -## Docker Engine - -The **Docker Engine** tab allows you to configure the Docker daemon used to run containers with Docker Desktop. - -You configure the daemon using a JSON configuration file. Here's what the file might look like: - -```json -{ - "builder": { - "gc": { - "defaultKeepStorage": "20GB", - "enabled": true - } - }, - "experimental": false -} -``` - -You can find this file at `$HOME/.docker/daemon.json`. To change the configuration, either -edit the JSON configuration directly from the dashboard in Docker Desktop, or open and -edit the file using your favorite text editor. - -> [!NOTE] -> -> Only the **Docker Desktop** daemon uses the configuration file under `$HOME/.docker`. -> If you manually install Docker Engine alongside Docker Desktop, the manually -> installed instance uses a `daemon.json` configuration file in a different location. -> Refer to [Configure the daemon](/manuals/engine/daemon/_index.md) for more information -> about how to configure the Docker daemon on a manually installed Docker Engine. - -To see the full list of possible configuration options, see the -[dockerd command reference](/reference/cli/dockerd/). - -Select **Apply & Restart** to save your settings and restart Docker Desktop. - -## Builders - -{{< include "desktop-builders-setting.md" >}} - -## Kubernetes - -Docker Desktop includes a standalone Kubernetes server, so that you can test -deploying your Docker workloads on Kubernetes. To turn on 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). - -## Software Updates - -The **Software Updates** tab notifies you of any updates available to Docker Desktop. -When there's a new update, -select 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, select -**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](/manuals/extensions/index.md). - -## Features in development - -On the **Feature control** tab you can control your settings for **Beta features** and **Experimental features**. - -You can also sign up to the [Developer Preview program](https://www.docker.com/community/get-involved/developer-preview/) from the **Features in development** tab. - -### Beta features - -{{< include "beta.md" >}} - -### Experimental features - -{{< include "desktop-experimental.md" >}} - -## Notifications - -{{< include "desktop-notifications-settings.md" >}} diff --git a/content/manuals/desktop/settings/windows.md b/content/manuals/desktop/settings/windows.md deleted file mode 100644 index 9faab506df9d..000000000000 --- a/content/manuals/desktop/settings/windows.md +++ /dev/null @@ -1,375 +0,0 @@ ---- -description: Change your Docker Desktop settings on Windows -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 {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}} and then **Settings** -- Select the **Settings** icon from the Docker Dashboard. - -You can also locate the `settings.json` file at `C:\Users\[USERNAME]\AppData\Roaming\Docker\settings.json`. - -## General - -On the **General** tab, you can configure when to start Docker and specify other settings: - -- **Start Docker Desktop when you sign in to your computer**. Select to automatically start Docker - Desktop when you sign in to your machine. - -- **Open Docker Dashboard when Docker Desktop starts**. Select to automatically open the - dashboard when starting Docker Desktop. - -- **Choose theme for Docker Desktop**. Choose whether you want to apply a **Light** or **Dark** theme to Docker Desktop. Alternatively you can set Docker Desktop to **Use system settings**. - -- **Choose container terminal**. Determines which terminal is launched when opening the terminal from a container. -If you choose the integrated terminal, you can run commands in a running container straight from the Docker Dashboard. For more information, see [Explore containers](../use-desktop/container.md). - -- **Enable Docker Debug by default**. Check this option to use Docker Debug by default when accessing the integrated terminal. For more information, see [Explore containers](../use-desktop/container.md#integrated-terminal). - -- **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 - Hyper-V backend. For more information, see [Docker Desktop WSL 2 backend](../wsl/index.md). - -- **Add the `*.docker.internal` names to the host's `/etc/hosts` file (Password required)**. Lets you resolve `*.docker.internal` DNS names from both the host and your containers. - -- **Use containerd for pulling and storing images**. - Turns on the containerd image store. - This brings new features like faster container startup performance by lazy-pulling images, - and the ability to run Wasm applications with Docker. - For more information, see [containerd image store](../containerd.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. - -- **Use Enhanced Container Isolation**. Select to enhance security by preventing containers from breaching the Linux VM. For more information, see [Enhanced Container Isolation](/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/index.md) - >**Note** - > - > This setting is only available if you are signed in to Docker Desktop and have a Docker Business subscription. - -- **Show CLI hints**. Displays CLI hints and tips when running Docker commands in the CLI. This is turned on by default. To turn CLI hints on or off from the CLI, set `DOCKER_CLI_HINTS` to `true` or `false` respectively. - -- **SBOM Indexing**. When this option is enabled, inspecting an image in Docker Desktop shows a **Start analysis** button that, when selected, analyzes the image with Docker Scout. - -- **Enable background SBOM indexing**. When this option is enabled, Docker Scout automatically analyzes images that you build or pull. - -## 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 **Resource allocation** options in the **Advanced** tab are 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). - -On the **Advanced** tab, you can limit resources available to the Docker Linux VM. - -Advanced settings are: - -- **CPU limit**. Specify the maximum number of CPUs to be used by Docker Desktop. - By default, Docker Desktop is set to use all the processors available on the host machine. - -- **Memory limit**. By default, Docker Desktop is set to use up to `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. - -- **Virtual disk limit**. Specify the maximum 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. - ->**Tip** -> -> If you feel Docker Desktop starting to get slow or you're running -> multi-container workloads, increase the memory and disk image space allocation - -- **Resource Saver**. Enable or disable [Resource Saver mode](../use-desktop/resource-saver.md), - which significantly reduces CPU and memory utilization on the host by - automatically turning off the Linux VM when Docker Desktop is idle (i.e., no - containers are running). - - You can also configure the Resource Saver timeout which indicates how long - should Docker Desktop be idle before Resource Saver mode kicks in. Default is - 5 minutes. - - >**Note** - > - > Exit from Resource Saver mode occurs automatically when containers run. Exit - > may take a few seconds (~3 to 10 secs) as Docker Desktop restarts the Linux VM. - -### 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. - -#### Synchronized file shares - -Synchronized file shares is an alternative file sharing mechanism that provides fast and flexible host-to-VM file sharing, enhancing bind mount performance through the use of synchronized filesystem caches. Available with Pro, Team, and Business subscriptions. - -To learn more, see [Synchronized file share](../synchronized-file-sharing.md). - -#### Virtual file shares - -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](../faqs/windowsfaqs.md#how-do-i-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](../troubleshoot/topics.md). - -File share settings are: - -- **Add a Directory**. select `+` and navigate to the directory you want to add. - -- **Remove a Directory**. select `-` 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](/manuals/engine/storage/volumes.md) -> (named volume) or [data container](/manuals/engine/storage/volumes.md). -> * Docker Desktop sets permissions to read/write/execute for users, groups and -> others [0777 or a+rwx](https://chmodcommand.com/chmod-0777/). -> This is not configurable. See [Permissions errors on data directories for shared volumes](../troubleshoot/topics.md). -> * 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) - -### Proxies - -Docker Desktop on Windows supports the use of HTTP/HTTPS and [SOCKS5 proxies](../networking.md#socks5-proxy-support). - -HTTP/HTTPS proxies can be used when: - -- Signing in to Docker -- Pulling or pushing images -- Fetching artifacts during image builds -- Containers interact with the external network -- Scanning images - -If the host uses a HTTP/HTTPS proxy configuration (static or via Proxy Auto-Configuration (PAC)), Docker Desktop reads -this configuration -and automatically uses these settings for signing into Docker, for pulling and pushing images, and for -container Internet access. - -To set a different proxy for Docker Desktop, turn on **Manual proxy configuration** and enter a single -upstream proxy URL of the form `http://proxy:port` or `https://proxy:port`. - -To prevent developers from accidentally changing the proxy settings, see -[Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/index.md#what-features-can-i-configure-with-settings-management). - -The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY` environment variable. - -If you are running Windows containers in Docker, you can allow the Windows Docker daemon to use Docker Desktop's internal proxy, with the **Use proxy for Windows Docker daemon** setting. -This is useful when a corporate proxy that requires authentication is manually configured or set at the system level. If you are an admin for your organization and have a Docker Business subscription, you can control this setting with [Settings management](/manuals/security/for-admins/hardened-desktop/settings-management/configure.md) using the `windowsDockerdPort` parameter. - -> [!NOTE] -> -> If you are using a PAC file hosted on a web server, make sure to add the MIME type `application/x-ns-proxy-autoconfig` for the `.pac` file extension on the server or website. Without this configuration, the PAC file may not be parsed correctly. - -#### Proxy authentication - -Docker Desktop supports Basic, Kerberos and NTLM proxy authentication methods. - -##### Basic authentication - -If your proxy uses Basic authentication, Docker Desktop prompts developers for a username and password and caches the credentials. All passwords are stored securely in the OS credential store. It will request re-authentication if that cache is removed. - -It's recommended that you use an `https://` URL for HTTP/HTTPS proxies to protect passwords during network transit. Docker Desktop also supports TLS 1.3 for communication with proxies. - -##### Kerberos and NTLM authentication - -> [!NOTE] -> -> Available for Docker Business subscribers with Docker Desktop version 4.30 and later. - -Developers are no longer interrupted by prompts for proxy credentials as authentication is centralized. This also reduces the risk of account lockouts due to incorrect sign in attempts. - -If your proxy offers multiple authentication schemes in 407 (Proxy Authentication Required) response, Docker Desktop by default selects the Basic authentication scheme. - -For Docker Desktop version 4.30 to 4.31: - -To enable Kerberos or NTLM proxy authentication, no additional configuration is needed beyond specifying the proxy IP address and port. - -For Docker Desktop version 4.32 and later: - -To enable Kerberos or NTLM proxy authentication you must pass the `--proxy-enable-kerberosntlm` installer flag during installation via the command line, and ensure your proxy server is properly configured for Kerberos or NTLM authentication. - -> [!TIP] -> -> Docker Desktop also supports the use of [SOCKS5 proxies](../networking.md#socks5-proxy-support). - -### Network - -> [!NOTE] -> -> The **Network** tab isn't available in the Windows container mode because -> Windows manages networking. - -{{< include "desktop-network-setting.md" >}} - -### 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 `. (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](../wsl/index.md). - -## Docker Engine - -The **Docker Engine** tab allows you to configure the Docker daemon used to run containers with Docker Desktop. - -You configure the daemon using a JSON configuration file. Here's what the file might look like: - -```json -{ - "builder": { - "gc": { - "defaultKeepStorage": "20GB", - "enabled": true - } - }, - "experimental": false -} -``` - -You can find this file at `$HOME/.docker/daemon.json`. To change the configuration, either -edit the JSON configuration directly from the dashboard in Docker Desktop, or open and -edit the file using your favorite text editor. - -To see the full list of possible configuration options, see the -[dockerd command reference](/reference/cli/dockerd/). - -Select **Apply & Restart** to save your settings and restart Docker Desktop. - -## Builders - -{{< include "desktop-builders-setting.md" >}} - -## 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 turn on 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). - -## 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 -select 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, select -**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](/manuals/extensions/index.md). - -## Features in development - -On the **Features in development** tab you can control your settings for **Beta features** and **Experimental features**. - -You can also sign up to the [Developer Preview Program](https://www.docker.com/community/get-involved/developer-preview/) from the **Features in development** tab. - -### Beta features - -{{< include "beta.md" >}} - -### Experimental features - -{{< include "desktop-experimental.md" >}} - -## Notifications - -{{< include "desktop-notifications-settings.md" >}} diff --git a/content/manuals/desktop/troubleshoot/overview.md b/content/manuals/desktop/troubleshoot/overview.md index c0516dd8c11f..a2fd9b1a3c0b 100644 --- a/content/manuals/desktop/troubleshoot/overview.md +++ b/content/manuals/desktop/troubleshoot/overview.md @@ -33,7 +33,7 @@ The **Troubleshoot** page contains the following options: - **Get 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 [Support](../../support/index.md). -- **Reset Kubernetes cluster**. Select to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../settings/linux.md#kubernetes). +- **Reset Kubernetes cluster**. Select to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](/manuals/desktop/settings.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. diff --git a/content/manuals/desktop/troubleshoot/topics.md b/content/manuals/desktop/troubleshoot/topics.md index 1da0dfc16a17..04b5a76eaf2f 100644 --- a/content/manuals/desktop/troubleshoot/topics.md +++ b/content/manuals/desktop/troubleshoot/topics.md @@ -55,7 +55,7 @@ After updating the `settings.json` file, close and restart Docker Desktop to app 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](/manuals/compose/gettingstarted.md), -you might need to turn on [file sharing](../settings/linux.md#file-sharing). +you might need to turn on [file sharing](/manuals/desktop/settings.md#file-sharing). Volume mounting requires shared drives for projects that live outside of the `/home/` directory. From **Settings**, select **Resources** and then **File sharing**. Share the drive that contains the Dockerfile and volume. @@ -115,7 +115,7 @@ To continue using VPNKit, add `"networkType":"vpnkit"` to your `settings.json` f #### Permissions errors on data directories for shared volumes -When sharing files from Windows, Docker Desktop sets permissions on [shared volumes](../settings/windows.md#file-sharing) +When sharing files from Windows, Docker Desktop sets permissions on [shared volumes](/manuals/desktop/settings.md#file-sharing) to a default value of [0777](https://chmodcommand.com/chmod-0777/) (`read`, `write`, `execute` permissions for `user` and for `group`). @@ -134,7 +134,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](/manuals/compose/gettingstarted.md), -you might need to turn on [shared folders](../settings/windows.md#file-sharing). +you might need to turn on [shared folders](/manuals/desktop/settings.md#file-sharing). With the Hyper-V backend, mounting files from Windows requires shared folders for Linux containers. From **Settings**, select **Shared Folders** and share the folder that contains the Dockerfile and volume. diff --git a/content/manuals/desktop/use-desktop/builds.md b/content/manuals/desktop/use-desktop/builds.md index cde114c30d2f..8f144001ddf2 100644 --- a/content/manuals/desktop/use-desktop/builds.md +++ b/content/manuals/desktop/use-desktop/builds.md @@ -209,8 +209,4 @@ The **Builder settings** view in the Docker Desktop settings lets you: ![Builder settings drop-down](../images/build-ui-manage-builders.webp) -For more information about managing builders, see: - -- [Change settings, Windows](../settings/windows.md#builders) -- [Change settings, Mac](../settings/mac.md#builders) -- [Change settings, Linux](../settings/linux.md#builders) +For more information about managing builders, see [Change settings](/manuals/desktop/settings.md#builders) diff --git a/content/manuals/desktop/wsl/_index.md b/content/manuals/desktop/wsl/_index.md index 5d2a2424da97..ae77817a00ce 100644 --- a/content/manuals/desktop/wsl/_index.md +++ b/content/manuals/desktop/wsl/_index.md @@ -55,7 +55,7 @@ Now `docker` commands work from Windows using the new WSL 2 engine. > > By default, Docker Desktop stores the data for the WSL 2 engine at `C:\Users\[USERNAME]\AppData\Local\Docker\wsl`. > If you want to change the location, for example, to another drive you can do so via the `Settings -> Resources -> Advanced` page from the Docker Dashboard. -> Read more about this and other Windows settings at [Changing Docker Desktop settings on Windows](../settings/windows.md) +> Read more about this and other Windows settings at [Changing settings](/manuals/desktop/settings.md) ## Enabling Docker support in WSL 2 distros diff --git a/content/manuals/engine/cli/proxy.md b/content/manuals/engine/cli/proxy.md index 54a1e1972bc8..e87bc4f006fe 100644 --- a/content/manuals/engine/cli/proxy.md +++ b/content/manuals/engine/cli/proxy.md @@ -12,10 +12,7 @@ This page describes how to configure the Docker CLI to use proxies via environment variables in containers. This page doesn't describe how to configure proxies for the Docker daemon. -For instructions on configuring Docker Desktop to use HTTP/HTTPS proxies, see -[proxies on Mac](/manuals/desktop/settings/mac.md#proxies), -[proxies on Windows](/manuals/desktop/settings/windows.md#proxies), and -[proxies on Linux](/manuals/desktop/settings/linux.md#proxies). +For instructions, see [configuring Docker Desktop to use HTTP/HTTPS proxies](/manuals/desktop/settings.md#proxies). If you're running Docker Engine without Docker Desktop, refer to [Configure the Docker daemon to use a proxy](/manuals/engine/daemon/proxy.md) diff --git a/content/manuals/engine/daemon/_index.md b/content/manuals/engine/daemon/_index.md index d1536cfb2b3b..fd93053b0fd1 100644 --- a/content/manuals/engine/daemon/_index.md +++ b/content/manuals/engine/daemon/_index.md @@ -33,11 +33,7 @@ This page shows you how to customize the Docker daemon, `dockerd`. > [!NOTE] > > This page is for users who've installed Docker Engine manually. If you're -> using Docker Desktop, refer to the following pages instead: -> -> - [Change preferences on Mac](/desktop/settings/mac#docker-engine) -> - [Change preferences on Windows](/desktop/settings/windows#docker-engine) -> - [Change preferences on Linux](/desktop/settings/linux#docker-engine) +> using Docker Desktop, refer to the [settings page](/manuals/desktop/settings.md#docker-engine). ## Configure the Docker daemon diff --git a/content/manuals/security/for-admins/hardened-desktop/registry-access-management.md b/content/manuals/security/for-admins/hardened-desktop/registry-access-management.md index 77fa0677baa1..091b695ea8bc 100644 --- a/content/manuals/security/for-admins/hardened-desktop/registry-access-management.md +++ b/content/manuals/security/for-admins/hardened-desktop/registry-access-management.md @@ -61,7 +61,7 @@ The new Registry Access Management policy takes effect after the developer succe There are certain limitations when using Registry Access Management: -- Windows image pulls and image builds are not restricted by default. For Registry Access Management to take effect on Windows Container mode, you must allow the Windows Docker daemon to use Docker Desktop's internal proxy by selecting the [Use proxy for Windows Docker daemon](/manuals/desktop/settings/windows.md#proxies) setting. +- Windows image pulls and image builds are not restricted by default. For Registry Access Management to take effect on Windows Container mode, you must allow the Windows Docker daemon to use Docker Desktop's internal proxy by selecting the [Use proxy for Windows Docker daemon](/manuals/desktop/settings.md#proxies) setting. - Builds such as `docker buildx` using a Kubernetes driver are not restricted - Builds such as `docker buildx` using a custom docker-container driver are not restricted - Blocking is DNS-based; you must use a registry's access control mechanisms to distinguish between “push” and “pull” diff --git a/data/redirects.yml b/data/redirects.yml index 5fa1f5be2f16..2c7e4a4b5d2d 100644 --- a/data/redirects.yml +++ b/data/redirects.yml @@ -88,7 +88,7 @@ "/desktop/use-desktop/pause/": - /go/mac-desktop-pause/ - /go/win-desktop-pause/ -"/desktop/settings/mac/#file-sharing": +"/desktop/settings/#file-sharing": - /go/mac-file-sharing/ "/engine/security/rootless/": # Instructions on running docker in rootless mode. This redirect is currently