mirror of https://github.com/docker/docs.git
create a global setting section for DD (#15122)
* create a global setting section for DD * fix broken links * fix broken links * fix broken links
This commit is contained in:
parent
c065baddf5
commit
d17f279abc
|
@ -1181,6 +1181,14 @@ manuals:
|
|||
title: Logs and troubleshooting
|
||||
- path: /desktop/dashboard/
|
||||
title: Dashboard
|
||||
- sectiontitle: Change settings
|
||||
section:
|
||||
- path: /desktop/settings/mac-settings/
|
||||
title: On Mac
|
||||
- path: /desktop/settings/windows-settings/
|
||||
title: On Windows
|
||||
- path: /desktop/settings/linux-settings/
|
||||
title: On Linux
|
||||
- path: /desktop/networking/
|
||||
title: Explore networking features
|
||||
- sectiontitle: Dev Environments (Beta)
|
||||
|
|
|
@ -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/mac/index.md#file-sharing) on Docker
|
||||
For more information, see [File sharing](../desktop/settings/mac-settings.md#file-sharing) on Docker
|
||||
for Mac, and the general examples on how to
|
||||
> [Manage data in containers](../storage/volumes.md).
|
||||
>
|
||||
|
|
|
@ -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](../windows/index.md#file-sharing) for
|
||||
the Unix-style permissions on [shared volumes](../settings/windows-settings.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
|
||||
|
|
Binary file not shown.
After Width: | Height: | Size: 42 KiB |
Before Width: | Height: | Size: 73 KiB After Width: | Height: | Size: 73 KiB |
Binary file not shown.
After Width: | Height: | Size: 568 B |
|
@ -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](../linux/index.md#resources). Using a dedicated storage
|
||||
controls to restrict [its resources](../settings/linux-settings.md#resources). Using a dedicated storage
|
||||
location for Docker Desktop prevents it from interfering with a Docker Engine
|
||||
installation on the same machine.
|
||||
|
||||
|
|
|
@ -4,164 +4,10 @@ keywords: linux, tutorial, run, docker, local, machine
|
|||
title: Docker Desktop for Linux user manual
|
||||
---
|
||||
|
||||
Welcome to Docker Desktop! The Docker Desktop for Linux user manual provides information on how to configure and manage your Docker Desktop settings.
|
||||
|
||||
Docker Desktop is an easy-to-install application that enables you to build and share containerized applications and microservices.
|
||||
The Docker Desktop for Linux user manual provides information on how to manage your credentials.
|
||||
|
||||
For information about Docker Desktop download, system requirements, and installation instructions, see [Install Docker Desktop](../install/linux-install.md).
|
||||
|
||||
## Settings
|
||||
|
||||
The Docker **Settings** menu allows you to configure your Docker settings such as installation, updates, version channels, Docker Hub login,
|
||||
and more.
|
||||
|
||||
Choose the Docker menu {: .inline} > **Settings** from the
|
||||
menu bar and configure the runtime options described below.
|
||||
|
||||
### General
|
||||
|
||||
{:width="750px"}
|
||||
|
||||
On the **General** tab, you can configure when to start Docker and specify other settings:
|
||||
|
||||
- **Start Docker Desktop when you log in**: Automatically starts Docker Desktop when you open your session.
|
||||
|
||||
- **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.
|
||||
|
||||
- **Show weekly tips**: Displays useful advice and suggestions about using Docker.
|
||||
|
||||
- **Open Docker Desktop dashboard at startup**: Automatically opens the dashboard when starting Docker Desktop.
|
||||
|
||||
- **Enable Docker Compose V1/V2 compatibility mode**: Select this option to enable the `docker-compose` command to use Docker Compose V2.
|
||||
|
||||
### 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 Docker.
|
||||
|
||||
{:width="750px"}
|
||||
|
||||
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 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.
|
||||
|
||||
- **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 get a prompt asking if you want to use the existing image or replace it.
|
||||
|
||||
#### 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.
|
||||
|
||||
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).
|
||||
|
||||
#### Proxies
|
||||
|
||||
To configure HTTP proxies, switch on the **Manual proxy configuration** setting.
|
||||
|
||||
Your proxy settings, however, will not be propagated into the containers you start.
|
||||
If you wish to set the proxy settings for your containers, you need to define
|
||||
environment variables for them, just like you would do on Linux, for example:
|
||||
|
||||
```console
|
||||
$ docker run -e HTTP_PROXY=http://proxy.example.com:3128 alpine env
|
||||
|
||||
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
|
||||
HOSTNAME=b7edf988b2b5
|
||||
TERM=xterm
|
||||
HOME=/root
|
||||
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).
|
||||
|
||||
#### Network
|
||||
|
||||
Docker Desktop uses a private IPv4 network for internal services such as a DNS server and an HTTP proxy. In case the choice of subnet clashes with something in your environment, specify a custom subnet using the **Network** setting.
|
||||
|
||||
### Docker Engine
|
||||
|
||||
The Docker Engine page 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
|
||||
|
||||
On the **Experimental Features** page, you can specify whether or not to enable experimental features.
|
||||
|
||||
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.
|
||||
|
||||
### 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 **Reset Kubernetes cluster** to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../kubernetes.md){:target="_blank" rel="noopener" class="_"}.
|
||||
|
||||
- Click **Apply & Restart** for your changes to take effect.
|
||||
|
||||
### Reset
|
||||
|
||||
> Reset and Restart options
|
||||
>
|
||||
> On Docker Desktop Linux, the **Restart Docker Desktop**, **Reset to factory defaults**, and other reset options are available from the **Troubleshoot** menu.
|
||||
|
||||
For information about the reset options, see [Logs and Troubleshooting](troubleshoot.md).
|
||||
|
||||
### Software Updates
|
||||
|
||||
The **Software Updates** section 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.
|
||||
|
||||
## Dashboard
|
||||
|
||||
The Docker Dashboard enables you to interact with containers and applications and manage the lifecycle of your applications directly from your machine. The Dashboard UI shows all running, stopped, and started containers with their state. It provides an intuitive interface to perform common actions to inspect and manage containers and existing Docker Compose applications. For more information, see [Docker Dashboard](../dashboard.md).
|
||||
|
||||
## Credentials management
|
||||
|
||||
Docker Desktop relies on [`pass`](https://www.passwordstore.org/){: target="_blank" rel="noopener" class="_"} to store credentials in gpg2-encrypted files.
|
||||
|
|
|
@ -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).
|
||||
|
||||
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](index.md#kubernetes).
|
||||
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../settings/linux-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.
|
||||
|
@ -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](index.md#file-sharing).
|
||||
you might need to enable [file sharing](../settings/linux-settings.md#file-sharing).
|
||||
|
||||
Volume mounting requires shared drives for projects that live outside of the
|
||||
`/home/<user>` directory. Go to {: .inline} >
|
||||
|
|
|
@ -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](./index.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-settings.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.
|
||||
|
|
|
@ -19,210 +19,10 @@ redirect_from:
|
|||
title: Docker Desktop for Mac user manual
|
||||
---
|
||||
|
||||
Welcome to Docker Desktop! The Docker Desktop for Mac user manual provides information on how to configure and manage your Docker Desktop settings.
|
||||
The Docker Desktop for Mac user manual provides information on how to Add TLS certificates and other useful topics.
|
||||
|
||||
For information about Docker Desktop download, system requirements, and installation instructions, see [Install Docker Desktop](../install/mac-install.md).
|
||||
|
||||
## Preferences
|
||||
|
||||
The Docker **Preferences** menu allows you to configure your Docker settings such as installation, updates, version channels, Docker Hub login,
|
||||
and more.
|
||||
|
||||
Choose the Docker menu {: .inline} > **Preferences** from the
|
||||
menu bar and configure the runtime options described below.
|
||||
|
||||
### General
|
||||
|
||||
{:width="750px"}
|
||||
|
||||
On the **General** tab, you can configure when to start Docker and specify other settings:
|
||||
|
||||
- **Start Docker Desktop when you log in**: Automatically starts Docker Desktop when you open your session.
|
||||
|
||||
- **Include VM in Time Machine backups**: Select this option 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.
|
||||
|
||||
- **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.
|
||||
|
||||
- **Show weekly tips**: Displays useful advice and suggestions about using Docker.
|
||||
|
||||
- **Open Docker Desktop dashboard at startup**: Automatically opens the dashboard when starting Docker Desktop.
|
||||
|
||||
- **Use Docker Compose V2**: Select this option 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.
|
||||
|
||||
#### Advanced
|
||||
|
||||
On the Advanced tab, you can limit resources available to Docker.
|
||||
|
||||
{:width="750px"}
|
||||
|
||||
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 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.
|
||||
|
||||
- **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 get a prompt asking if you want to use the existing image or replace it.
|
||||
|
||||
#### 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.
|
||||
|
||||
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).
|
||||
>
|
||||
* 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`](troubleshoot.md#volume-mounting-requires-file-sharing-for-any-project-directories-outside-of-users).)
|
||||
|
||||
#### 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**
|
||||
in the **Settings > Resources > Proxies** in Docker Dashboard and enter a single upstream proxy URL
|
||||
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).
|
||||
|
||||
The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY` environment variable.
|
||||
|
||||
#### Network
|
||||
|
||||
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.
|
||||
|
||||
### Docker Engine
|
||||
|
||||
The Docker Engine page 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
|
||||
|
||||
On the **Experimental Features** page, you can specify whether or not to enable experimental features.
|
||||
|
||||
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.
|
||||
|
||||
#### Enable the new Apple Virtualization framework
|
||||
|
||||
Select **Use the new Virtualization framework** to allow Docker Desktop to use the new `virtualization.framework` instead of the ‘hypervisor.framework’. Ensure to reset your Kubernetes cluster when you enable the new Virtualization framework for the first time.
|
||||
|
||||
#### Enable VirtioFS
|
||||
|
||||
Docker Desktop for Mac lets developers use a new experimental file-sharing implementation called [virtiofS](https://virtio-fs.gitlab.io/){: target='_blank' rel='noopener' class='_'}; the current default is gRPC-FUSE. virtiofs has been found to significantly improve file sharing performance on macOS. For more details, see our blog post [Speed boost achievement unlocked on Docker Desktop 4.6 for Mac](https://www.docker.com/blog/speed-boost-achievement-unlocked-on-docker-desktop-4-6-for-mac/){:target="_blank" rel="noopener" class="_"}.
|
||||
|
||||
To enable virtioFS:
|
||||
|
||||
1. Verify that you are on the following macOS version:
|
||||
- macOS 12.2 or later (for Apple Silicon)
|
||||
- macOS 12.3 or later (for Intel)
|
||||
|
||||
2. Select **Enable VirtioFS accelerated directory sharing** to enable virtioFS.
|
||||
|
||||
3. Click **Apply & Restart**.
|
||||
|
||||
### 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**.
|
||||
|
||||
- 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="_"}.
|
||||
|
||||
- Click **Apply & Restart** for your changes to take effect.
|
||||
|
||||
### Reset
|
||||
|
||||
> Reset and Restart options
|
||||
>
|
||||
> On Docker Desktop Mac, the **Restart Docker Desktop**, **Reset to factory defaults**, and other reset options are available from the **Troubleshoot** menu.
|
||||
|
||||
For information about the reset options, see [Logs and Troubleshooting](troubleshoot.md).
|
||||
|
||||
### Software Updates
|
||||
|
||||
The **Software Updates** section 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](../mac/release-notes/index.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.
|
||||
|
||||
## Dashboard
|
||||
|
||||
The Docker Dashboard enables you to interact with containers and applications and manage the lifecycle of your applications directly from your machine. The Dashboard UI shows all running, stopped, and started containers with their state. It provides an intuitive interface to perform common actions to inspect and manage containers and existing Docker Compose applications. For more information, see [Docker Dashboard](../dashboard.md).
|
||||
|
||||
## Add TLS certificates
|
||||
|
||||
You can add trusted Certificate Authorities (CAs) (used to verify registry
|
||||
|
|
|
@ -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).
|
||||
|
||||
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](index.md#kubernetes).
|
||||
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../settings/mac-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.
|
||||
|
@ -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](index.md#file-sharing).
|
||||
you might need to enable [file sharing](../settings/mac-settings.md#file-sharing).
|
||||
|
||||
Volume mounting requires shared drives for projects that live outside of the
|
||||
`/Users` directory. Go to {: .inline} >
|
||||
|
|
|
@ -46,9 +46,9 @@ syntax for `-p` is `HOST_PORT:CLIENT_PORT`.
|
|||
### HTTP/HTTPS Proxy Support
|
||||
|
||||
See:
|
||||
- [Proxies on Linux](linux/index.md#proxies)
|
||||
- [Proxies on Mac](mac/index.md#proxies)
|
||||
- [Proxies on Windows](windows/index.md#proxies)
|
||||
- [Proxies on Linux](settings/linux-settings.md#proxies)
|
||||
- [Proxies on Mac](settings/mac-settings.md#proxies)
|
||||
- [Proxies on Windows](settings/windows-settings.md#proxies)
|
||||
|
||||
## Features for Mac and Linux
|
||||
|
||||
|
|
|
@ -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](../windows/index.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-settings.md#file-sharing).
|
||||
|
||||
### Known issues
|
||||
|
||||
|
|
|
@ -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)](../mac/index.md#docker-engine).
|
||||
- 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).
|
||||
|
||||
- Docker Experimental mode can be toggled. See [Daemon Basic (experimental mode and registries)](../mac/index.md#docker-engine).
|
||||
- Docker Experimental mode can be toggled. See [Daemon Basic (experimental mode and registries)](../settings/mac-settings.md#docker-engine).
|
||||
|
||||
**Upgrades**
|
||||
|
||||
|
|
|
@ -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](../mac/#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-settings.md#experimental-features).
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
|
@ -0,0 +1,151 @@
|
|||
---
|
||||
description: Docker Desktop settings
|
||||
keywords: Settings, Docker Desktop, Linux
|
||||
title: Change Docker Dektop 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} 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.
|
||||
|
||||
- **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.
|
||||
|
||||
- **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.
|
||||
|
||||
#### 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.
|
||||
|
||||
- **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.
|
||||
|
||||
- **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
|
||||
|
||||
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.
|
||||
|
||||
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).
|
||||
|
||||
### Proxies
|
||||
|
||||
To configure HTTP proxies, switch on the **Manual proxy configuration** setting.
|
||||
|
||||
Your proxy settings, however, are not propagated into the containers you start.
|
||||
If you wish to set the proxy settings for your containers, you need to define
|
||||
environment variables for them, just like you would do on Linux, for example:
|
||||
|
||||
```console
|
||||
$ docker run -e HTTP_PROXY=http://proxy.example.com:3128 alpine env
|
||||
|
||||
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
|
||||
HOSTNAME=b7edf988b2b5
|
||||
TERM=xterm
|
||||
HOME=/root
|
||||
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).
|
||||
|
||||
### Network
|
||||
|
||||
Docker Desktop uses a private IPv4 network for internal services such as a DNS server and an HTTP proxy. In case the choice of subnet clashes with something in your environment, specify a custom subnet using the **Network** setting.
|
||||
|
||||
### 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
|
||||
|
||||
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, see [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.
|
||||
|
||||
> **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 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).
|
|
@ -0,0 +1,193 @@
|
|||
---
|
||||
description: Docker Desktop settings
|
||||
keywords: Settings, Docker Desktop, Mac
|
||||
title: Change Docker Dektop 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 {: .inline} and then **Preferences**
|
||||
- Select the **Preferences** 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.
|
||||
|
||||
- **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.
|
||||
|
||||
- **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.
|
||||
|
||||
- **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.
|
||||
|
||||
- **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.
|
||||
|
||||
### 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.
|
||||
|
||||
- **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.
|
||||
|
||||
- **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
|
||||
|
||||
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.
|
||||
|
||||
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).
|
||||
>
|
||||
* 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).)
|
||||
|
||||
### 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`.
|
||||
|
||||
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).
|
||||
|
||||
The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY` environment variable.
|
||||
|
||||
### Network
|
||||
|
||||
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.
|
||||
|
||||
## 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 %}
|
||||
|
||||
### Enable the new Apple Virtualization framework
|
||||
|
||||
Select **Use the new Virtualization framework** to allow Docker Desktop to use the new `virtualization.framework` instead of the ‘hypervisor.framework’. Ensure to reset your Kubernetes cluster when you enable the new Virtualization framework for the first time.
|
||||
|
||||
### Enable VirtioFS
|
||||
|
||||
Docker Desktop for Mac lets developers use a new experimental file-sharing implementation called [virtiofS](https://virtio-fs.gitlab.io/){: target='_blank' rel='noopener' class='_'}; the current default is gRPC-FUSE. virtiofs has been found to significantly improve file sharing performance on macOS. For more details, see our blog post [Speed boost achievement unlocked on Docker Desktop 4.6 for Mac](https://www.docker.com/blog/speed-boost-achievement-unlocked-on-docker-desktop-4-6-for-mac/){:target="_blank" rel="noopener" class="_"}.
|
||||
|
||||
To enable virtioFS:
|
||||
|
||||
1. Verify that you are on the following macOS version:
|
||||
- macOS 12.2 or later (for Apple Silicon)
|
||||
- macOS 12.3 or later (for Intel)
|
||||
|
||||
2. Select **Enable VirtioFS accelerated directory sharing** to enable virtioFS.
|
||||
|
||||
3. Click **Apply & Restart**.
|
||||
|
||||
## 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**.
|
||||
|
||||
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="_"}.
|
||||
|
||||
## 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).
|
|
@ -0,0 +1,214 @@
|
|||
---
|
||||
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 {: .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**.
|
||||
|
||||
{: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).
|
|
@ -16,275 +16,16 @@ redirect_from:
|
|||
title: Docker Desktop for Windows user manual
|
||||
---
|
||||
|
||||
Welcome to Docker Desktop! The Docker Desktop for Windows user manual provides information on how to configure and manage your Docker Desktop settings.
|
||||
Welcome to Docker Desktop! The Docker Desktop for Windows user manual provides information on how to add TLS certificates and switch between Windows and Linux containers.
|
||||
|
||||
For information about Docker Desktop download, system requirements, and installation instructions, see [Install Docker Desktop](../install/windows-install.md).
|
||||
|
||||
## Settings
|
||||
|
||||
The **Docker Desktop** menu allows you to open the Docker Dashboard, run the Quick Start Guide, configure your Docker settings such as installation, updates, version channels, Docker Hub login, and more.
|
||||
|
||||
This section explains the configuration options accessible from the **Settings** dialog.
|
||||
|
||||
1. To open the Docker Desktop menu, right-click the Docker icon in the Notifications area (or System tray):
|
||||
|
||||
{:width="250px"}
|
||||
|
||||
2. Select **Settings** to open the Settings dialog:
|
||||
|
||||
{:width="300px"}
|
||||
|
||||
### General
|
||||
|
||||
On the **General** tab, you can configure when to start Docker and specify other settings.
|
||||
|
||||
{:width="750px"}
|
||||
|
||||
- **Start Docker when you log in**: Select this option to automatically start Docker Desktop when you log into your Windows machine.
|
||||
|
||||
- **Expose daemon on tcp://localhost:2375 without TLS**: Click 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](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**: Displays useful advice and suggestions about using Docker.
|
||||
|
||||
- **Open Docker Desktop dashboard at startup**: Automatically opens the dashboard when starting Docker Desktop.
|
||||
|
||||
- **Use Docker Compose V2**: Select this option 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 get a prompt asking 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](#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.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.
|
||||
|
||||
- **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](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**.
|
||||
|
||||
{: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**
|
||||
in the **Settings** > **Resources** **Proxies** in the Docker Dashboard 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 will be 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](wsl.md).
|
||||
|
||||
### Docker Engine
|
||||
|
||||
The Docker Engine page 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.
|
||||
|
||||
### Command Line
|
||||
|
||||
On the Command Line page, you can specify whether or not to enable experimental features.
|
||||
|
||||
You can toggle the experimental features on and off in Docker Desktop. If you toggle the experimental features off, Docker Desktop uses the current generally available release of Docker Engine.
|
||||
|
||||
#### Experimental features
|
||||
|
||||
{% include experimental.md %}
|
||||
|
||||
Run `docker version` to verify whether you have enabled experimental features. Experimental mode
|
||||
is listed under `Server` data. If `Experimental` is `true`, then Docker is
|
||||
running in experimental mode, as shown here:
|
||||
|
||||
```console
|
||||
> docker version
|
||||
|
||||
Client: Docker Engine - Community
|
||||
Version: 19.03.1
|
||||
API version: 1.40
|
||||
Go version: go1.12.5
|
||||
Git commit: 74b1e89
|
||||
Built: Thu Jul 25 21:17:08 2019
|
||||
OS/Arch: windows/amd64
|
||||
Experimental: true
|
||||
|
||||
Server: Docker Engine - Community
|
||||
Engine:
|
||||
Version: 19.03.1
|
||||
API version: 1.40 (minimum version 1.12)
|
||||
Go version: go1.12.5
|
||||
Git commit: 74b1e89
|
||||
Built: Thu Jul 25 21:17:52 2019
|
||||
OS/Arch: linux/amd64
|
||||
Experimental: true
|
||||
containerd:
|
||||
Version: v1.2.6
|
||||
GitCommit: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
|
||||
runc:
|
||||
Version: 1.0.0-rc8
|
||||
GitCommit: 425e105d5a03fabd737a126ad93d62a9eeede87f
|
||||
docker-init:
|
||||
Version: 0.18.0
|
||||
GitCommit: fec3683
|
||||
```
|
||||
|
||||
### 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** section 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](../windows/release-notes/index.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.
|
||||
|
||||
## Dashboard
|
||||
|
||||
The Docker Dashboard enables you to interact with containers and applications and manage the lifecycle of your applications directly from your machine. The Dashboard UI shows all running, stopped, and started containers with their state. It provides an intuitive interface to perform common actions to inspect and manage containers and existing Docker Compose applications. For more information, see [Docker Dashboard](../dashboard.md).
|
||||
|
||||
## Add TLS certificates
|
||||
|
||||
You can add trusted Certificate Authorities (CAs) (used to verify registry
|
||||
server certificates) and client certificates (used to authenticate to
|
||||
registries) to your Docker daemon.
|
||||
|
||||
### Reset
|
||||
|
||||
The **Restart Docker Desktop** and **Reset to factory defaults** options are now available on the **Troubleshoot** menu. For information, see [Logs and Troubleshooting](troubleshoot.md).
|
||||
|
||||
### Troubleshoot
|
||||
|
||||
Visit our [Logs and Troubleshooting](troubleshoot.md) guide for more details.
|
||||
|
||||
## Switch between Windows and Linux containers
|
||||
|
||||
From the Docker Desktop menu, you can toggle which daemon (Linux or Windows)
|
||||
|
@ -312,10 +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](#general)
|
||||
* [Proxies](#proxies)
|
||||
* [Daemon](#docker-engine)
|
||||
* [Reset](#reset)
|
||||
* [General](../settings/windows-settings.md#general)
|
||||
* [Proxies](../settings/windows-settings.md#proxies)
|
||||
* [Daemon](../settings/windows-settings.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,
|
||||
|
@ -405,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](#docker-engine)). Docker Desktop ignores
|
||||
[Docker Daemon](../settings/windows-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.
|
||||
|
|
|
@ -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).
|
||||
|
||||
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](index.md#kubernetes).
|
||||
* **Reset Kubernetes cluster**: Select this option to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](../settings/windows-settings.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](index.md#file-sharing)
|
||||
When sharing files from Windows, Docker Desktop sets permissions on [shared volumes](../settings/windows-settings.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](index.md#file-sharing).
|
||||
you might need to enable [shared folders](../settings/windows-settings.md#file-sharing).
|
||||
|
||||
With the Hyper-V backend, mounting files from Windows requires shared folders for Linux containers. Click {: .inline}
|
||||
and then **Settings** > **Shared Folders** and share the folder that contains the
|
||||
|
|
|
@ -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/mac/index.md#proxies), [proxies on Windows](../desktop/windows/index.md#proxies), and [proxies on Linux](../desktop/linux/index.md#proxies).
|
||||
> 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).
|
||||
|
||||
> If you are not running Docker Desktop, and have installed the Docker Engine in
|
||||
> other ways, refer to the "HTTP/HTTPS proxy" section in
|
||||
|
|
|
@ -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/windows/index.md#file-sharing) and
|
||||
[Docker Desktop for Mac](../desktop/mac/index.md#file-sharing), you
|
||||
[Docker Desktop for Windows](../desktop/settings/windows-settings.md#file-sharing) and
|
||||
[Docker Desktop for Mac](../desktop/settings/mac-settings.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/mac/index.md#advanced) and
|
||||
[Docker Desktop for Windows](../desktop/windows/index.md#advanced).
|
||||
[Docker Desktop for Mac](../desktop/settings/mac-settings.md#advanced) and
|
||||
[Docker Desktop for Windows](../desktop/settings/windows-settings.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
|
||||
|
|
Loading…
Reference in New Issue