mirror of https://github.com/docker/docs.git
ENGDOCS-2298 (#21339)
<!--Delete sections as needed --> ## Description More DD IA improvements. Moves troubleshooting, faqs, support, and other misc. pages. ## Related issues or tickets <!-- Related issues, pull requests, or Jira tickets --> ## Reviews <!-- Notes for reviewers here --> <!-- List applicable reviews (optionally @tag reviewers) --> - [ ] Technical review - [ ] Editorial review - [ ] Product review
This commit is contained in:
Allie Sadler
GitHub
parent
3ea0cd758d
commit
502e61c960
|
|
@ -114,7 +114,7 @@ You can create the volume and start the container using the CLI or Docker Deskto
|
|||
> ```
|
||||
>
|
||||
> For more details about Git Bash's syntax differences, see
|
||||
> [Working with Git Bash](/desktop/troubleshoot/topics/#working-with-git-bash).
|
||||
> [Working with Git Bash](/desktop/troubleshoot-and-support/troubleshoot/topics/#working-with-git-bash).
|
||||
|
||||
|
||||
{{< /tab >}}
|
||||
|
|
|
|||
|
|
@ -50,7 +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 [File sharing](/manuals/desktop/settings.md#file-sharing).
|
||||
filesystem you can share with containers. For details about accessing the setting, see [File sharing](/manuals/desktop/settings-and-maintenance/settings.md#file-sharing).
|
||||
|
||||
2. Open a terminal and change directory to the `getting-started-app`
|
||||
directory.
|
||||
|
|
|
|||
|
|
@ -315,7 +315,7 @@ To run the application using Docker:
|
|||
>
|
||||
> For Windows users, you may get an error when running the container. Verify
|
||||
> that the line endings in the `entrypoint.sh` are `LF` (`\n`) and not `CRLF` (`\r\n`),
|
||||
> then rebuild the image. For more details, see [Avoid unexpected syntax errors, use Unix style line endings for files in containers](/desktop/troubleshoot/topics/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
|
||||
> then rebuild the image. For more details, see [Avoid unexpected syntax errors, use Unix style line endings for files in containers](/desktop/troubleshoot-and-support/troubleshoot/topics/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
|
||||
|
||||
You will see the following in your console after the container starts.
|
||||
|
||||
|
|
|
|||
|
|
@ -318,7 +318,7 @@ To run the application using Docker:
|
|||
>
|
||||
> For Windows users, you may get an error when running the container. Verify
|
||||
> that the line endings in the `entrypoint.sh` are `LF` (`\n`) and not `CRLF` (`\r\n`),
|
||||
> then rebuild the image. For more details, see [Avoid unexpected syntax errors, use Unix style line endings for files in containers](/desktop/troubleshoot/topics/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
|
||||
> then rebuild the image. For more details, see [Avoid unexpected syntax errors, use Unix style line endings for files in containers](/desktop/troubleshoot-and-support/troubleshoot/topics/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
|
||||
|
||||
You will see the following in your console after the container starts.
|
||||
|
||||
|
|
|
|||
|
|
@ -331,7 +331,7 @@ To run the application using Docker:
|
|||
>
|
||||
> For Windows users, you may get an error when running the container. Verify
|
||||
> that the line endings in the `entrypoint.sh` are `LF` (`\n`) and not `CRLF` (`\r\n`),
|
||||
> then rebuild the image. For more details, see [Avoid unexpected syntax errors, use Unix style line endings for files in containers](/desktop/troubleshoot/topics/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
|
||||
> then rebuild the image. For more details, see [Avoid unexpected syntax errors, use Unix style line endings for files in containers](/desktop/troubleshoot-and-support/troubleshoot/topics/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
|
||||
|
||||
You will see the following in your console after the container starts.
|
||||
|
||||
|
|
|
|||
|
|
@ -390,7 +390,7 @@ To run the application using Docker:
|
|||
>
|
||||
> For Windows users, you may get an error when running the container. Verify
|
||||
> that the line endings in the `entrypoint.sh` are `LF` (`\n`) and not `CRLF` (`\r\n`),
|
||||
> then rebuild the image. For more details, see [Avoid unexpected syntax errors, use Unix style line endings for files in containers](/desktop/troubleshoot/topics/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
|
||||
> then rebuild the image. For more details, see [Avoid unexpected syntax errors, use Unix style line endings for files in containers](/desktop/troubleshoot-and-support/troubleshoot/topics/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
|
||||
|
||||
You will see the following in your console after the container starts.
|
||||
|
||||
|
|
|
|||
|
|
@ -324,7 +324,7 @@ To run the application using Docker:
|
|||
>
|
||||
> For Windows users, you may get an error when running the container. Verify
|
||||
> that the line endings in the `entrypoint.sh` are `LF` (`\n`) and not `CRLF` (`\r\n`),
|
||||
> then rebuild the image. For more details, see [Avoid unexpected syntax errors, use Unix style line endings for files in containers](/desktop/troubleshoot/topics/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
|
||||
> then rebuild the image. For more details, see [Avoid unexpected syntax errors, use Unix style line endings for files in containers](/desktop/troubleshoot-and-support/troubleshoot/topics/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
|
||||
|
||||
You will see the following in your console after the container starts.
|
||||
|
||||
|
|
|
|||
|
|
@ -90,4 +90,8 @@ To reset your password, enter your email address on the [Sign in](https://login.
|
|||
|
||||
## Troubleshooting
|
||||
|
||||
For support and troubleshooting information, see [Get support](../support.md).
|
||||
If you have a paid Docker subscription, you can [contact the Support team](https://hub.docker.com/support/contact/).
|
||||
|
||||
All Docker users can seek troubleshooting information and support through the following resources, where Docker or the community respond on a best effort basis.
|
||||
- [Docker Community Forums](https://forums.docker.com/)
|
||||
- [Docker Community Slack](http://dockr.ly/comm-slack)
|
||||
|
|
|
|||
|
|
@ -123,4 +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](/manuals/desktop/settings.md#builders).
|
||||
you can inspect builders in [Docker Desktop settings](/manuals/desktop/settings-and-maintenance/settings.md#builders).
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ If you have already installed Docker Desktop, you can check which version of Com
|
|||
> $ sudo rm /usr/local/bin/docker-compose
|
||||
> $ sudo ln -s /Applications/Docker.app/Contents/Resources/cli-plugins/docker-compose /usr/local/bin/docker-compose
|
||||
> ```
|
||||
> Or enable [Automatically check configuration](/desktop/settings/) which will detect and fix it for you.
|
||||
> Or enable [Automatically check configuration](/manuals/desktop/settings-and-maintenance/settings.md) which will detect and fix it for you.
|
||||
|
||||
### Scenario two: Install the Compose plugin
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ grid:
|
|||
- title: Browse common FAQs
|
||||
description: Explore general FAQs or FAQs for specific platforms.
|
||||
icon: help
|
||||
link: /desktop/faqs/
|
||||
link: /desktop/troubleshoot-and-support/faqs/general/
|
||||
- title: Find additional resources
|
||||
description: |
|
||||
Find information on networking features, deploying on Kubernetes, and more.
|
||||
|
|
@ -33,7 +33,7 @@ grid:
|
|||
- title: Give feedback
|
||||
description: Provide feedback on Docker Desktop or Docker Desktop features.
|
||||
icon: sms
|
||||
link: /desktop/feedback/
|
||||
link: /desktop/troubleshoot-and-support/feedback/
|
||||
aliases:
|
||||
- /desktop/opensource/
|
||||
- /docker-for-mac/dashboard/
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ syntax for `-p` is `HOST_PORT:CLIENT_PORT`.
|
|||
|
||||
### HTTP/HTTPS Proxy support
|
||||
|
||||
See [Proxies](/manuals/desktop/settings.md#proxies)
|
||||
See [Proxies](/manuals/desktop/settings-and-maintenance/settings.md#proxies)
|
||||
|
||||
### SOCKS5 proxy support
|
||||
|
||||
|
|
|
|||
|
|
@ -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](/manuals/desktop/settings.md#file-sharing).
|
||||
- Starting with Docker Desktop 2.2.0.3, you must access all shared files using their original case. For example, if you have created a file called `test`, you must open it as `test`. Attempts to open the file as `Test` will fail with the error `No such file or directory`. For more information, see _Tips on shared drives, permissions, and volume mounts_ in [File sharing](/manuals/desktop/settings-and-maintenance/settings.md#file-sharing).
|
||||
|
||||
### Known issues
|
||||
|
||||
|
|
|
|||
|
|
@ -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)](/manuals/desktop/settings.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-and-maintenance/settings.md#docker-engine).
|
||||
|
||||
- Docker Experimental mode can be toggled. See [Daemon Basic (experimental mode and registries)](/manuals/desktop/settings.md#docker-engine).
|
||||
- Docker Experimental mode can be toggled. See [Daemon Basic (experimental mode and registries)](/manuals/desktop/settings-and-maintenance/settings.md#docker-engine).
|
||||
|
||||
**Upgrades**
|
||||
|
||||
|
|
@ -1718,7 +1718,7 @@ issue is being investigated. The workaround is to restart Docker.app.
|
|||
traversals of large directories are currently slow. Additionally, containers
|
||||
that perform large numbers of directory operations, such as repeated scans of
|
||||
large directory trees, may suffer from poor performance. More information is
|
||||
available in [Known Issues](../troubleshoot/known-issues.md) in Troubleshooting.
|
||||
available in [Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md) in Troubleshooting.
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart `Docker.app`.
|
||||
|
||||
|
|
@ -1748,7 +1748,7 @@ with `osxfs`. In particular, writes of small blocks and traversals of large
|
|||
directories are currently slow. Additionally, containers that perform large
|
||||
numbers of directory operations, such as repeated scans of large directory
|
||||
trees, may suffer from poor performance. More information is available in
|
||||
[Known Issues](../troubleshoot/known-issues.md) in Troubleshooting.
|
||||
[Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md) in Troubleshooting.
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart Docker.app.
|
||||
|
||||
|
|
@ -1782,7 +1782,7 @@ trees, may suffer from poor performance. More information is available in
|
|||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks and traversals of large
|
||||
directories are currently slow. Additionally, containers that perform large
|
||||
numbers of directory operations, such as repeated scans of large directory
|
||||
trees, may suffer from poor performance. For more information and workarounds, see the bullet on performance of bind-mounted directories in [Known Issues](../troubleshoot/known-issues.md) in Troubleshooting.
|
||||
trees, may suffer from poor performance. For more information and workarounds, see the bullet on performance of bind-mounted directories in [Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md) in Troubleshooting.
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart `Docker.app`.
|
||||
|
||||
|
|
@ -1808,7 +1808,7 @@ trees, may suffer from poor performance. For more information and workarounds, s
|
|||
|
||||
* Docker.app sometimes uses 200% CPU after macOS wakes up from sleep mode. The issue is being investigated. The workaround is to restart Docker.app
|
||||
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. For more information and workarounds, see the bullet on performance of bind-mounted directories in [Known Issues](../troubleshoot/known-issues.md) in Troubleshooting.
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. For more information and workarounds, see the bullet on performance of bind-mounted directories in [Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md) in Troubleshooting.
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart Docker.app
|
||||
|
||||
|
|
@ -1831,7 +1831,7 @@ trees, may suffer from poor performance. For more information and workarounds, s
|
|||
|
||||
* Docker.app sometimes uses 200% CPU after macOS wakes up from sleep mode. The issue is being investigated. The workaround is to restart Docker.app
|
||||
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. More information is available in [Known Issues](../troubleshoot/known-issues.md).
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. More information is available in [Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md).
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart Docker.app
|
||||
|
||||
|
|
@ -1878,7 +1878,7 @@ events or unexpected unmounts.
|
|||
|
||||
* Docker.app sometimes uses 200% CPU after macOS wakes up from sleep mode. The issue is being investigated. The workaround is to restart Docker.app
|
||||
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks, and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. For more information and workarounds, see [Known Issues](../troubleshoot/known-issues.md) in [Logs and Troubleshooting](../troubleshoot/_index.md).
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks, and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. For more information and workarounds, see [Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md) in [Logs and Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md).
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart Docker.app
|
||||
|
||||
|
|
@ -1922,7 +1922,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot/known-issues.md).
|
||||
* See [Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md).
|
||||
|
||||
### Beta 18.1 Release Notes (2016-07-07 1.12.0-rc3-beta18.1)
|
||||
|
||||
|
|
@ -1948,7 +1948,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot/known-issues.md).
|
||||
* See [Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md).
|
||||
|
||||
### Beta 18 Release Notes (2016-07-06 1.12.0-rc3-beta18)
|
||||
|
||||
|
|
@ -1969,7 +1969,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot/known-issues.md).
|
||||
* See [Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md).
|
||||
|
||||
### Beta 17 Release Notes (2016-06-29 1.12.0-rc2-beta17)
|
||||
|
||||
|
|
@ -1988,7 +1988,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot/known-issues.md).
|
||||
* See [Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md).
|
||||
|
||||
### Beta 16 Release Notes (2016-06-17 1.12.0-rc2-beta16)
|
||||
|
||||
|
|
@ -2010,7 +2010,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot/known-issues.md).
|
||||
* See [Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md).
|
||||
|
||||
### Beta 15 Release Notes (2016-06-10 1.11.2-beta15)
|
||||
|
||||
|
|
@ -2034,7 +2034,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot/known-issues.md).
|
||||
* See [Known Issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md).
|
||||
|
||||
### Beta 14 Release Notes (2016-06-02 1.11.1-beta14)
|
||||
|
||||
|
|
|
|||
|
|
@ -1723,7 +1723,7 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
|
|||
**New**
|
||||
|
||||
- Windows containers settings panel and options are working. In previous releases, settings were not implemented for
|
||||
[Windows containers mode](../faqs/windowsfaqs.md#how-do-i-switch-between-windows-and-linux-containers).
|
||||
[Windows containers mode](/manuals/desktop/troubleshoot-and-support/faqs/windowsfaqs.md#how-do-i-switch-between-windows-and-linux-containers).
|
||||
- Windows containers: Restart from the settings panel works
|
||||
- Windows containers: Factory default
|
||||
- Windows containers: `Daemon.json` can be modified
|
||||
|
|
@ -1992,7 +1992,7 @@ work. Some insider builds may not work.
|
|||
**Known issues**
|
||||
|
||||
* Only UTF-8 passwords are supported for host filesystem sharing
|
||||
* Docker automatically disables lingering net adapters. The only way to remove them is manually using `devmgmt.msc` as documented in [Troubleshooting](../troubleshoot/known-issues.md).
|
||||
* Docker automatically disables lingering net adapters. The only way to remove them is manually using `devmgmt.msc` as documented in [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md).
|
||||
|
||||
### Beta 22 Release (2016-08-11 1.12.0-beta22)
|
||||
|
||||
|
|
@ -2000,7 +2000,7 @@ Unreleased. See Beta 23 for changes.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* Docker automatically disables lingering net adapters. The only way to remove them is manually using `devmgmt.msc` as documented in [Troubleshooting](../troubleshoot/known-issues.md).
|
||||
* Docker automatically disables lingering net adapters. The only way to remove them is manually using `devmgmt.msc` as documented in [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md).
|
||||
|
||||
### Beta 21 Release (2016-07-28 1.12.0-beta21)
|
||||
|
||||
|
|
@ -2275,7 +2275,7 @@ This Beta release includes some significant changes:
|
|||
* The GUI now runs in non-elevated mode and connects to an elevated Windows service
|
||||
* Allocate virtual machine memory by 256 MB increments, instead of 1 GB
|
||||
* Show a meaningful error when the user has an empty password
|
||||
* Improved [Troubleshooting](../troubleshoot/_index.md) page
|
||||
* Improved [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md) page
|
||||
|
||||
**Upgrades**
|
||||
|
||||
|
|
@ -2299,7 +2299,7 @@ This Beta release includes some significant changes:
|
|||
|
||||
**Known issues**
|
||||
|
||||
* Due to limitation in the Windows NAT implementation, co-existence with other NAT prefixes needs to be carefully managed. See [Troubleshooting](../troubleshoot/known-issues.md) for more details.
|
||||
* Due to limitation in the Windows NAT implementation, co-existence with other NAT prefixes needs to be carefully managed. See [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md) for more details.
|
||||
|
||||
* Logs for the windows service are not aggregated with logs from the GUI. This is expected to be fixed in future versions.
|
||||
|
||||
|
|
@ -2327,7 +2327,7 @@ This Beta release includes some significant changes:
|
|||
|
||||
**Known issues**
|
||||
|
||||
* Due to limitation in the Windows NAT implementation, co-existence with other NAT prefixes needs to be carefully managed. See [Troubleshooting](../troubleshoot/_index.md) for more details.
|
||||
* Due to limitation in the Windows NAT implementation, co-existence with other NAT prefixes needs to be carefully managed. See [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md) for more details.
|
||||
|
||||
|
||||
### Beta 9 Release (2016-04-26 1.11.0-beta9)
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ aliases:
|
|||
weight: 220
|
||||
---
|
||||
|
||||
This page contains information about the new features, improvements, known issues, and bug fixes in Docker Desktop releases. For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/releases.md).
|
||||
This page contains information about the new features, improvements, known issues, and bug fixes in Docker Desktop releases. For frequently asked questions about Docker Desktop releases, see [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/releases.md).
|
||||
|
||||
Docker Desktop versions older than 6 months from the latest release are not available for download. Previous release notes are available in our [documentation repository](https://github.com/docker/docs/tree/main/content/manuals/desktop/previous-versions).
|
||||
|
||||
|
|
@ -239,7 +239,7 @@ Take a look at the [Docker Public Roadmap](https://github.com/orgs/docker/projec
|
|||
- [Docker Debug](/reference/cli/docker/debug.md) is now generally available.
|
||||
- BuildKit now evaluates Dockerfile rules to inform you of potential issues.
|
||||
- **Resource Allocation** settings can now be accessed directly from the resource usage data displayed in the Dashboard footer.
|
||||
- New and improved experience for [troubleshooting](/manuals/desktop/troubleshoot/_index.md).
|
||||
- New and improved experience for [troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md).
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -275,7 +275,7 @@ Take a look at the [Docker Public Roadmap](https://github.com/orgs/docker/projec
|
|||
|
||||
#### For Mac
|
||||
|
||||
- The Configuration integrity check feature now provides more context around what has changed with your Docker Desktop configuration. For more information, see the [FAQs](faqs/macfaqs.md).
|
||||
- The Configuration integrity check feature now provides more context around what has changed with your Docker Desktop configuration. For more information, see the [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/macfaqs.md).
|
||||
- The Configuration integrity check feature shows an error when it fails to repair Docker Desktop.
|
||||
- Fixed a bug where the IPv6 TCP was set to `host.docker.internal`. Fixes [docker/for-mac#7332](https://github.com/docker/for-mac/issues/7332).
|
||||
- Fixed an issue where the `docker-compose` symlink pointed to an empty location. Fixes [docker/for-mac#7345](https://github.com/docker/for-mac/issues/7345).
|
||||
|
|
@ -485,7 +485,7 @@ For more information, see [microsoft/WSL#11794](https://github.com/microsoft/WSL
|
|||
|
||||
#### For Windows
|
||||
|
||||
- Added support for [Kerberos and NTLM proxy authentication](/manuals/desktop/settings.md#proxy-authentication) on Windows. Requires a Business subscription.
|
||||
- Added support for [Kerberos and NTLM proxy authentication](/manuals/desktop/settings-and-maintenance/settings.md#proxy-authentication) on Windows. Requires a Business subscription.
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -965,7 +965,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](/manuals/desktop/settings.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-and-maintenance/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).
|
||||
|
|
@ -1026,7 +1026,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](/manuals/desktop/settings.md) 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-and-maintenance/settings.md) and set `"displaySwitchWinLinContainers": true`.
|
||||
|
||||
#### For all platforms
|
||||
|
||||
|
|
@ -1250,13 +1250,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](/manuals/desktop/settings.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-and-maintenance/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](/manuals/desktop/settings.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-and-maintenance/settings.md) in settings.
|
||||
|
||||
## 4.21.1
|
||||
|
||||
|
|
@ -1368,7 +1368,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](/manuals/desktop/settings.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-and-maintenance/settings.md#proxies).
|
||||
|
||||
#### For Linux
|
||||
|
||||
|
|
@ -2397,7 +2397,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](/manuals/desktop/settings.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-and-maintenance/settings.md#beta-features).
|
||||
|
||||
### Updates
|
||||
|
||||
|
|
@ -2676,7 +2676,7 @@ CVE-2021-44228](https://www.docker.com/blog/apache-log4j-2-cve-2021-44228/).
|
|||
|
||||
#### For Mac
|
||||
|
||||
- Docker Desktop on Apple silicon no longer requires Rosetta 2, with the exception of [three optional command line tools](troubleshoot/known-issues.md).
|
||||
- Docker Desktop on Apple silicon no longer requires Rosetta 2, with the exception of [three optional command line tools](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md).
|
||||
|
||||
#### For Windows
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,6 @@
|
|||
---
|
||||
build:
|
||||
render: never
|
||||
title: Settings and maintenance
|
||||
weight: 40
|
||||
---
|
||||
|
|
@ -2,7 +2,9 @@
|
|||
title: How to back up and restore your Docker Desktop data
|
||||
keywords: Docker Desktop, backup, restore, migration, reinstall, containers, images,
|
||||
volumes
|
||||
weight: 130
|
||||
weight: 20
|
||||
aliases:
|
||||
- /desktop/backup-and-restore.md
|
||||
---
|
||||
|
||||
Use the following procedure to save and restore your images and container data. This is useful if you want to reset your VM disk or to move your Docker environment to a new
|
||||
|
|
@ -27,16 +29,16 @@ computer, for example.
|
|||
If you used a [named volume](/manuals/engine/storage/_index.md#more-details-about-mount-types) to store container data, such as databases, refer to the [back up, restore, or migrate data volumes](/manuals/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section.
|
||||
|
||||
2. Use [`docker push`](/reference/cli/docker/image/push.md) to push any
|
||||
images you have built locally and want to keep to the [Docker Hub registry](../docker-hub/_index.md).
|
||||
images you have built locally and want to keep to the [Docker Hub registry](/manuals/docker-hub/_index.md).
|
||||
|
||||
Make sure to configure the [repository's visibility as "private"](../docker-hub/repos/_index.md)
|
||||
Make sure to configure the [repository's visibility as "private"](/manuals/docker-hub/repos/_index.md)
|
||||
for images that should not be publicly accessible.
|
||||
|
||||
Alternatively, use [`docker image save -o images.tar image1 [image2 ...]`](/reference/cli/docker/image/save.md)
|
||||
to save any images you want to keep to a local tar file.
|
||||
|
||||
After backing up your data, you can uninstall the current version of Docker Desktop
|
||||
and [install a different version](release-notes.md) or reset Docker Desktop to factory defaults.
|
||||
and [install a different version](/manuals/desktop/release-notes.md) or reset Docker Desktop to factory defaults.
|
||||
|
||||
## Restore your data
|
||||
|
||||
|
|
@ -8,12 +8,13 @@ aliases:
|
|||
- /desktop/settings/mac/
|
||||
- /desktop/settings/windows/
|
||||
- /desktop/settings/linux/
|
||||
weight: 160
|
||||
- /desktop/settings/
|
||||
weight: 10
|
||||
---
|
||||
|
||||
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 Desktop Dashboard.
|
||||
|
||||
You can also locate the `settings-store.json` file (or `settings.json` for Docker Desktop versions 4.34 and earlier) at:
|
||||
|
|
@ -57,7 +58,7 @@ If you choose the integrated terminal, you can run commands in a running contain
|
|||
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](/manuals/desktop/containerd.md).
|
||||
|
||||
- {{< badge color=blue text="Mac only" >}} **Choose Virtual Machine Manager (VMM)**. Choose the Virtual Machine Manager for creating and managing the Docker Desktop Linux VM.
|
||||
- Select **Docker VMM** for the latest and most performant Hypervisor/Virtual Machine Manager. This option is available only on Apple Silicon Macs running macOS 12.5 or later and is currently in Beta.
|
||||
|
|
@ -98,7 +99,7 @@ If you choose the integrated terminal, you can run commands in a running contain
|
|||
- 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](/manuals/desktop/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/troubleshoot-and-support/faqs/macfaqs.md#why-do-i-keep-getting-a-notification-telling-me-an-application-has-changed-my-desktop-configurations).
|
||||
|
||||
## Resources
|
||||
|
||||
|
|
@ -213,7 +214,7 @@ 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`](/manuals/desktop/troubleshoot/topics.md)
|
||||
> For more information, see [Volume mounting requires file sharing for any project directories outside of `/Users`](/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md)
|
||||
|
||||
#### Shared folders on demand
|
||||
|
||||
|
|
@ -226,7 +227,7 @@ 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**.
|
||||
|
||||
|
||||
|
||||
|
||||
### Proxies
|
||||
|
||||
|
|
@ -493,7 +494,7 @@ Use the **Notifications** tab to turn on or turn off notifications for the follo
|
|||
|
||||
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 Desktop Dashboard and then move to the **Notifications** drawer. To open the **Notifications** drawer, select {{< inline-image src="images/notifications.svg" alt="notifications" >}}.
|
||||
Notifications momentarily appear in the lower-right of the Docker Desktop Dashboard and then move to the **Notifications** drawer. To open the **Notifications** drawer, select {{< inline-image src="../images/notifications.svg" alt="notifications" >}}.
|
||||
|
||||
## Advanced
|
||||
|
||||
|
|
@ -40,7 +40,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](/manuals/desktop/settings.md#resources). Using a dedicated storage
|
||||
controls to restrict [its resources](/manuals/desktop/settings-and-maintenance/settings.md#resources). Using a dedicated storage
|
||||
location for Docker Desktop prevents it from interfering with a Docker Engine
|
||||
installation on the same machine.
|
||||
|
||||
|
|
@ -140,10 +140,10 @@ To install Docker Desktop successfully, your Linux host must meet the following
|
|||
- Gnome, KDE, or MATE Desktop environment.
|
||||
- For many Linux distros, the Gnome environment does not support tray icons. To add support for tray icons, you need to install a Gnome extension. For example, [AppIndicator](https://extensions.gnome.org/extension/615/appindicator-support/).
|
||||
- At least 4 GB of RAM.
|
||||
- Enable configuring ID mapping in user namespaces, see [File sharing](/manuals/desktop/faqs/linuxfaqs.md#how-do-i-enable-file-sharing). Note that for Docker Desktop version 4.35 and later, this is not required anymore.
|
||||
- Enable configuring ID mapping in user namespaces, see [File sharing](/manuals/desktop/troubleshoot-and-support/faqs/linuxfaqs.md#how-do-i-enable-file-sharing). Note that for Docker Desktop version 4.35 and later, this is not required anymore.
|
||||
- Recommended: [Initialize `pass`](/manuals/desktop/setup/sign-in.md#credentials-management-for-linux-users) for credentials management.
|
||||
|
||||
Docker Desktop for Linux runs a Virtual Machine (VM). For more information on why, see [Why Docker Desktop for Linux runs a VM](/manuals/desktop/faqs/linuxfaqs.md#why-does-docker-desktop-for-linux-run-a-vm).
|
||||
Docker Desktop for Linux runs a Virtual Machine (VM). For more information on why, see [Why Docker Desktop for Linux runs a VM](/manuals/desktop/troubleshoot-and-support/faqs/linuxfaqs.md#why-does-docker-desktop-for-linux-run-a-vm).
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
|
|
|
|||
|
|
@ -55,8 +55,8 @@ To install Docker Desktop successfully, you must meet the [general system requir
|
|||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- Take a look at the [Docker workshop](/get-started/workshop/_index.md) to learn how to build an image and run it as a containerized application.
|
||||
- [Explore Docker Desktop](/manuals/desktop/use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot/_index.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](/manuals/desktop/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](/manuals/desktop/release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
- [Back up and restore data](/manuals/desktop/backup-and-restore.md) provides instructions
|
||||
- [Back up and restore data](/manuals/desktop/settings-and-maintenance/backup-and-restore.md) provides instructions
|
||||
on backing up and restoring data related to Docker.
|
||||
|
|
|
|||
|
|
@ -90,8 +90,8 @@ Don't forget to substitute `<arch>` with the architecture you want.
|
|||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- Take a look at the [Docker workshop](/get-started/workshop/_index.md) to learn how to build an image and run it as a containerized application.
|
||||
- [Explore Docker Desktop](/manuals/desktop/use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot/_index.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](/manuals/desktop/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](/manuals/desktop/release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
- [Back up and restore data](/manuals/desktop/backup-and-restore.md) provides instructions
|
||||
- [Back up and restore data](/manuals/desktop/settings-and-maintenance/backup-and-restore.md) provides instructions
|
||||
on backing up and restoring data related to Docker.
|
||||
|
|
|
|||
|
|
@ -81,8 +81,8 @@ Don't forget to substitute `<arch>` with the architecture you want.
|
|||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- Take a look at the [Docker workshop](/get-started/workshop/_index.md) to learn how to build an image and run it as a containerized application.
|
||||
- [Explore Docker Desktop](/manuals/desktop/use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot/_index.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](/manuals/desktop/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](/manuals/desktop/release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
- [Back up and restore data](/manuals/desktop/backup-and-restore.md) provides instructions
|
||||
- [Back up and restore data](/manuals/desktop/settings-and-maintenance/backup-and-restore.md) provides instructions
|
||||
on backing up and restoring data related to Docker.
|
||||
|
|
|
|||
|
|
@ -143,8 +143,8 @@ $ sudo dnf install ./docker-desktop-<arch>-rhel.rpm
|
|||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- Take a look at the [Docker workshop](/get-started/workshop/_index.md) to learn how to build an image and run it as a containerized application.
|
||||
- [Explore Docker Desktop](/manuals/desktop/use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot/_index.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](/manuals/desktop/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](/manuals/desktop/release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
- [Back up and restore data](/manuals/desktop/backup-and-restore.md) provides instructions
|
||||
- [Back up and restore data](/manuals/desktop/settings-and-maintenance/backup-and-restore.md) provides instructions
|
||||
on backing up and restoring data related to Docker.
|
||||
|
|
|
|||
|
|
@ -90,8 +90,8 @@ Don't forget to substitute `<arch>` with the architecture you want.
|
|||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- Take a look at the [Docker workshop](/get-started/workshop/_index.md) to learn how to build an image and run it as a containerized application.
|
||||
- [Explore Docker Desktop](/manuals/desktop/use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot/_index.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](/manuals/desktop/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](/manuals/desktop/release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
- [Back up and restore data](/manuals/desktop/backup-and-restore.md) provides instructions
|
||||
- [Back up and restore data](/manuals/desktop/settings-and-maintenance/backup-and-restore.md) provides instructions
|
||||
on backing up and restoring data related to Docker.
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ This page contains download URLs, information about system requirements, and ins
|
|||
> Docker supports Docker Desktop on the most recent versions of macOS. That is, the current release of macOS and the previous two releases. As new major versions of macOS are made generally available, Docker stops supporting the oldest version and supports the newest version of macOS (in addition to the previous two releases).
|
||||
|
||||
- At least 4 GB of RAM.
|
||||
- For the best experience, it's recommended that you install Rosetta 2. There is no longer a hard requirement to install Rosetta 2, however there are a few optional command line tools that still require Rosetta 2 when using Darwin/AMD64. See [Known issues](/manuals/desktop/troubleshoot/known-issues.md). To install Rosetta 2 manually from the command line, run the following command:
|
||||
- For the best experience, it's recommended that you install Rosetta 2. There is no longer a hard requirement to install Rosetta 2, however there are a few optional command line tools that still require Rosetta 2 when using Darwin/AMD64. See [Known issues](/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md). To install Rosetta 2 manually from the command line, run the following command:
|
||||
|
||||
```console
|
||||
$ softwareupdate --install-rosetta
|
||||
|
|
@ -66,7 +66,7 @@ This page contains download URLs, information about system requirements, and ins
|
|||
|
||||
> [!TIP]
|
||||
>
|
||||
> See the [FAQs](/manuals/desktop/faqs/general.md#how-do-I-run-docker-desktop-without-administrator-privileges) on how to install and run Docker Desktop without needing administrator privileges.
|
||||
> See the [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md#how-do-I-run-docker-desktop-without-administrator-privileges) on how to install and run Docker Desktop without needing administrator privileges.
|
||||
|
||||
### Install interactively
|
||||
|
||||
|
|
@ -92,7 +92,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](/manuals/desktop/settings.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-and-maintenance/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
|
||||
|
|
@ -133,9 +133,9 @@ The `install` command accepts the following flags:
|
|||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- [Get started with Docker](/get-started/introduction/_index.md).
|
||||
- [Explore Docker Desktop](/manuals/desktop/use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot/_index.md) describes common problems, workarounds, how
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md) describes common problems, workarounds, how
|
||||
to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](/manuals/desktop/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](/manuals/desktop/release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
- [Back up and restore data](/manuals/desktop/backup-and-restore.md) provides instructions
|
||||
- [Back up and restore data](/manuals/desktop/settings-and-maintenance/backup-and-restore.md) provides instructions
|
||||
on backing up and restoring data related to Docker.
|
||||
|
|
|
|||
|
|
@ -65,7 +65,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`](/manuals/desktop/settings.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-and-maintenance/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.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ aliases:
|
|||
|
||||
### What happens to user data if they have an older Docker Desktop installation (i.e. `.exe`)?
|
||||
|
||||
If they have an older `.exe` installation, users must [uninstall](/manuals/desktop/uninstall.md) this version before using the new MSI version. This deletes all Docker containers, images, volumes, and other Docker-related data local to the machine, and removes the files generated by the application. For older versions, users should [backup](/manuals/desktop/backup-and-restore.md) any containers that they want to keep.
|
||||
If they have an older `.exe` installation, users must [uninstall](/manuals/desktop/uninstall.md) this version before using the new MSI version. This deletes all Docker containers, images, volumes, and other Docker-related data local to the machine, and removes the files generated by the application. For older versions, users should [backup](/manuals/desktop/settings-and-maintenance/backup-and-restore.md) any containers that they want to keep.
|
||||
|
||||
For Docker Desktop versions 4.30 and later of the `exe` installer, a `-keep-data` flag is available. It removes Docker Desktop but keeps underlying data, such as the VMs that run containers.
|
||||
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ _For checksums, see [Release notes](/manuals/desktop/release-notes.md)_
|
|||
- 64-bit processor with [Second Level Address Translation (SLAT)](https://en.wikipedia.org/wiki/Second_Level_Address_Translation)
|
||||
- 4GB system RAM
|
||||
- Enable hardware virtualization in BIOS. For more information, see
|
||||
[Virtualization](/manuals/desktop/troubleshoot/topics.md#virtualization).
|
||||
[Virtualization](/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md#virtualization).
|
||||
|
||||
For more information on setting up WSL 2 with Docker Desktop, see [WSL](/manuals/desktop/wsl/_index.md).
|
||||
|
||||
|
|
@ -82,7 +82,7 @@ For more information on setting up WSL 2 with Docker Desktop, see [WSL](/manuals
|
|||
- 4GB system RAM
|
||||
- Turn on BIOS-level hardware virtualization support in the
|
||||
BIOS settings. For more information, see
|
||||
[Virtualization](/manuals/desktop/troubleshoot/topics.md#virtualization).
|
||||
[Virtualization](/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md#virtualization).
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
|
|
@ -106,7 +106,7 @@ For more information on setting up WSL 2 with Docker Desktop, see [WSL](/manuals
|
|||
- 64-bit processor with [Second Level Address Translation (SLAT)](https://en.wikipedia.org/wiki/Second_Level_Address_Translation)
|
||||
- 4GB system RAM
|
||||
- Enable hardware virtualization in BIOS. For more information, see
|
||||
[Virtualization](/manuals/desktop/troubleshoot/topics.md#virtualization).
|
||||
[Virtualization](/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md#virtualization).
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
|
|
@ -161,7 +161,7 @@ again when you switch back.
|
|||
|
||||
> [!TIP]
|
||||
>
|
||||
> See the [FAQs](/manuals/desktop/faqs/general.md#how-do-I-run-docker-desktop-without-administrator-privileges) on how to install and run Docker Desktop without needing administrator privileges.
|
||||
> See the [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md#how-do-I-run-docker-desktop-without-administrator-privileges) on how to install and run Docker Desktop without needing administrator privileges.
|
||||
|
||||
### Install interactively
|
||||
|
||||
|
|
@ -272,8 +272,8 @@ Docker Desktop does not start automatically after installation. To start Docker
|
|||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- [Get started with Docker](/get-started/introduction/_index.md).
|
||||
- [Explore Docker Desktop](/manuals/desktop/use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot/_index.md) describes common problems, workarounds, and
|
||||
- [Troubleshooting](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md) describes common problems, workarounds, and
|
||||
how to get support.
|
||||
- [FAQs](/manuals/desktop/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](/manuals/desktop/release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
- [Back up and restore data](/manuals/desktop/backup-and-restore.md) provides instructions on backing up and restoring data related to Docker.
|
||||
- [Back up and restore data](/manuals/desktop/settings-and-maintenance/backup-and-restore.md) provides instructions on backing up and restoring data related to Docker.
|
||||
|
|
|
|||
|
|
@ -110,4 +110,4 @@ docker.io/molly/privateimage:latest
|
|||
|
||||
- [Explore Docker Desktop](/manuals/desktop/use-desktop/_index.md) and its features.
|
||||
- Change your Docker Desktop settings
|
||||
- [Browse common FAQs](/manuals/desktop/faqs/general.md)
|
||||
- [Browse common FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md)
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ To run Docker Desktop in a virtual desktop environment, it is essential nested v
|
|||
>
|
||||
> Support for running Docker Desktop on a virtual desktop is available to Docker Business customers, on VMware ESXi or Azure VMs only.
|
||||
|
||||
The support available from Docker extends to installing and running Docker Desktop inside the VM, once the nested virtualization is set up correctly. The only hypervisors we have successfully tested are VMware ESXi and Azure, and there is no support for other VMs. For more information on Docker Desktop support, see [Get support](/manuals/desktop/support.md).
|
||||
The support available from Docker extends to installing and running Docker Desktop inside the VM, once the nested virtualization is set up correctly. The only hypervisors we have successfully tested are VMware ESXi and Azure, and there is no support for other VMs. For more information on Docker Desktop support, see [Get support](/manuals/desktop/troubleshoot-and-support/support.md).
|
||||
|
||||
For troubleshooting problems and intermittent failures that are outside of Docker's control, you should contact your hypervisor vendor. Each hypervisor vendor offers different levels of support. For example, Microsoft supports running nested Hyper-V both on-prem and on Azure, with some version constraints. This may not be the case for VMWare ESXi.
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,6 @@
|
|||
---
|
||||
build:
|
||||
render: never
|
||||
title: Troubleshoot and support
|
||||
weight: 50
|
||||
---
|
||||
|
|
@ -2,5 +2,7 @@
|
|||
build:
|
||||
render: never
|
||||
title: FAQs
|
||||
weight: 190
|
||||
weight: 30
|
||||
aliases:
|
||||
- /desktop/faqs/
|
||||
---
|
||||
|
|
@ -19,17 +19,17 @@ cannot access features that require an active internet
|
|||
connection. Additionally, any functionality that requires you to sign in won't work while using Docker Desktop offline or in air-gapped environments.
|
||||
This includes:
|
||||
|
||||
- The resources in the [Learning Center](../use-desktop/_index.md)
|
||||
- The resources in the [Learning Center](/manuals/desktop/use-desktop/_index.md)
|
||||
- Pulling or pushing an image to Docker Hub
|
||||
- [Image Access Management](../../security/for-developers/access-tokens.md)
|
||||
- [Static vulnerability scanning](../../docker-hub/vulnerability-scanning.md)
|
||||
- [Image Access Management](/manuals/security/for-developers/access-tokens.md)
|
||||
- [Static vulnerability scanning](/manuals/docker-hub/vulnerability-scanning.md)
|
||||
- Viewing remote images in the Docker Dashboard
|
||||
- Setting up [Dev Environments](../dev-environments/_index.md)
|
||||
- Setting up [Dev Environments](/manuals/desktop/dev-environments/_index.md)
|
||||
- Docker Build when using [BuildKit](/manuals/build/buildkit/_index.md#getting-started).
|
||||
You can work around this by disabling BuildKit. Run `DOCKER_BUILDKIT=0 docker build .` to disable BuildKit.
|
||||
- [Kubernetes](../kubernetes.md) (Images are download when you enable Kubernetes for the first time)
|
||||
- [Kubernetes](/manuals/desktop/kubernetes.md) (Images are download when you enable Kubernetes for the first time)
|
||||
- Checking for updates
|
||||
- [In-app diagnostics](/manuals/desktop/troubleshoot/_index.md#diagnose-from-the-app) (including the [Self-diagnose tool](/manuals/desktop/troubleshoot/_index.md#diagnose-from-the-app))
|
||||
- [In-app diagnostics](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md#diagnose-from-the-app) (including the [Self-diagnose tool](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md#diagnose-from-the-app))
|
||||
- Sending usage statistics
|
||||
|
||||
### How do I connect to the remote Docker Engine API?
|
||||
|
|
@ -59,7 +59,7 @@ The host has a changing IP address, or none if you have no network access.
|
|||
We recommend that you connect to the special DNS name `host.docker.internal`,
|
||||
which resolves to the internal IP address used by the host.
|
||||
|
||||
For more information and examples, see [how to connect from a container to a service on the host](../networking.md#i-want-to-connect-from-a-container-to-a-service-on-the-host).
|
||||
For more information and examples, see [how to connect from a container to a service on the host](/manuals/desktop/networking.md#i-want-to-connect-from-a-container-to-a-service-on-the-host).
|
||||
|
||||
### Can I pass through a USB device to a container?
|
||||
|
||||
|
|
@ -22,14 +22,14 @@ 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](/manuals/desktop/settings.md#file-sharing) for
|
||||
the Unix-style permissions on [shared volumes](/manuals/desktop/settings-and-maintenance/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
|
||||
`group`) which is not configurable.
|
||||
|
||||
For workarounds and to learn more, see
|
||||
[Permissions errors on data directories for shared volumes](../troubleshoot/topics.md#permissions-errors-on-data-directories-for-shared-volumes).
|
||||
[Permissions errors on data directories for shared volumes](/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md#permissions-errors-on-data-directories-for-shared-volumes).
|
||||
|
||||
### How do symlinks work on Windows?
|
||||
|
||||
|
|
@ -71,7 +71,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](/manuals/desktop/settings.md#docker-engine)). Docker Desktop ignores
|
||||
[Docker Daemon](/manuals/desktop/settings-and-maintenance/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.
|
||||
|
|
@ -3,7 +3,7 @@ description: Find a way to provide feedback that's right for you
|
|||
keywords: Feedback, Docker Desktop, Linux, Mac, Windows, Dev Environments, Extensions,
|
||||
Community forum, bugs, problems, issues
|
||||
title: Give feedback
|
||||
weight: 180
|
||||
weight: 40
|
||||
---
|
||||
|
||||
There are many ways you can provide feedback on Docker Desktop or Docker Desktop features.
|
||||
|
|
@ -2,7 +2,9 @@
|
|||
description: See what support is available for Docker Desktop
|
||||
keywords: Support, Docker Desktop, Linux, Mac, Windows
|
||||
title: Get support
|
||||
weight: 170
|
||||
weight: 20
|
||||
aliases:
|
||||
- /desktop/support/
|
||||
---
|
||||
|
||||
Find information on how to get support, and the scope of Docker Desktop support.
|
||||
|
|
@ -16,27 +18,36 @@ Find information on how to get support, and the scope of Docker Desktop support.
|
|||
|
||||
### How do I get Docker Desktop support?
|
||||
|
||||
If you have a paid Docker subscription, raise a ticket through [Docker Desktop support](https://hub.docker.com/support/desktop/).
|
||||
If you have a paid Docker subscription, you can [contact the Support team](https://hub.docker.com/support/contact/).
|
||||
|
||||
Docker Community users can get support through our Github repos for-win, for-mac, for-linux, where we respond on a best-effort basis.
|
||||
All Docker users can seek support through the following resources, where Docker or the community respond on a best effort basis.
|
||||
- [Docker Desktop for Windows GitHub repo](https://github.com/docker/for-win)
|
||||
- [Docker Desktop for Mac GitHub repo](https://github.com/docker/for-mac)
|
||||
- [Docker Desktop for Linux GitHub repo](https://github.com/docker/desktop-linux)
|
||||
- [Docker Community Forums](https://forums.docker.com/)
|
||||
- [Docker Community Slack](http://dockr.ly/comm-slack)
|
||||
|
||||
### What support can I get?
|
||||
|
||||
If you have a paid Docker subscription, you can request for support on the following types of issues:
|
||||
* Account management related issues
|
||||
* Automated builds
|
||||
* Basic product 'how to' questions
|
||||
* Billing or subscription issues
|
||||
* Configuration issues
|
||||
* Desktop installation issues
|
||||
* Installation crashes
|
||||
* Failure to launch Docker Desktop on first run
|
||||
* Desktop update issues
|
||||
* Sign-in issues in both the command line interface and Docker Hub user interface
|
||||
* Push or pull issues, including rate limiting
|
||||
* Usage issues
|
||||
* Crash closing software
|
||||
* Docker Desktop not behaving as expected
|
||||
|
||||
* Desktop upgrade issues
|
||||
* Desktop installation issues
|
||||
* Installation crashes
|
||||
* Failure to launch Docker Desktop on first run
|
||||
* Usage issues
|
||||
* Crash closing software
|
||||
* Docker Desktop not behaving as expected
|
||||
* Configuration issues
|
||||
* Basic product ‘how to’ questions
|
||||
|
||||
For Windows users, you can also request support on:
|
||||
* Enabling virtualization in BIOS
|
||||
* Enabling Windows features
|
||||
For Windows users, you can also request support on:
|
||||
* Turning on virtualization in BIOS
|
||||
* Turning on Windows features
|
||||
* Running inside [certain VM or VDI environments](/manuals/desktop/setup/vm-vdi.md) (Docker Business customers only)
|
||||
|
||||
### What is not supported?
|
||||
|
||||
|
|
@ -57,15 +68,18 @@ Docker Desktop excludes support for the following types of issues:
|
|||
* Defects in the Docker software due to hardware malfunction, abuse, or improper use
|
||||
* Any version of the Docker software other than the latest version
|
||||
* Reimbursing and expenses spent for third-party services not provided by Docker
|
||||
* Docker Support excludes training, customization, and integration
|
||||
* Docker support excludes training, customization, and integration
|
||||
* Running multiple instances of Docker Desktop on a single machine
|
||||
|
||||
>Note
|
||||
> [!NOTE]
|
||||
>
|
||||
> Support for [running Docker Desktop in a VM or VDI environment](/manuals/desktop/setup/vm-vdi.md) is only available to Docker Business customers.
|
||||
|
||||
### What versions are supported?
|
||||
|
||||
We currently only offer support for the latest version of Docker Desktop. If you are running an older version, you may be asked to upgrade before we investigate your support request.
|
||||
For Docker Business customers, Docker offers support for versions up to six months older than the latest version, although any fixes will be on the latest version.
|
||||
|
||||
For Pro and Team customers, Docker only offers support for the latest version of Docker Desktop. If you are running an older version, Docker may ask you to update before investigating your support request.
|
||||
|
||||
### How many machines can I get support for Docker Desktop on?
|
||||
|
||||
|
|
@ -15,8 +15,9 @@ aliases:
|
|||
- /docker-for-win/troubleshoot/
|
||||
- /docker-for-windows/troubleshoot/
|
||||
- /desktop/troubleshoot/overview/
|
||||
- /desktop/troubleshoot/
|
||||
tags: [ Troubleshooting ]
|
||||
weight: 160
|
||||
weight: 10
|
||||
---
|
||||
|
||||
This page contains information on how to diagnose and troubleshoot Docker Desktop, and how to check the logs.
|
||||
|
|
@ -25,14 +26,14 @@ This page contains information on how to diagnose and troubleshoot Docker Deskto
|
|||
|
||||
To navigate to **Troubleshoot** either:
|
||||
|
||||
- Select the Docker menu Docker menu {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}} and then **Troubleshoot**.
|
||||
- Select the Docker menu Docker menu {{< inline-image src="../../images/whale-x.svg" alt="whale menu" >}} and then **Troubleshoot**.
|
||||
- Select the **Troubleshoot** icon near the top-right corner of Docker Dashboard.
|
||||
|
||||
The **Troubleshooting** menu contains the following options:
|
||||
|
||||
- **Restart Docker Desktop**.
|
||||
|
||||
- **Reset Kubernetes cluster**. Select to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](/manuals/desktop/settings.md#kubernetes).
|
||||
- **Reset Kubernetes cluster**. Select to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](/manuals/desktop/settings-and-maintenance/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.
|
||||
|
|
@ -65,7 +66,7 @@ If you are a Mac or Linux user, you also have the option to **Uninstall** Docker
|
|||
- If you have a paid Docker subscription, select **Contact support**. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied in step three to the **Diagnostics ID field**. Then, select **Submit ticket** to request Docker Desktop support.
|
||||
> [!NOTE]
|
||||
>
|
||||
> You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](../../support/_index.md).
|
||||
> You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](/manuals/desktop/troubleshoot-and-support/support.md).
|
||||
- If you don't have a paid Docker subscription, select **Report a Bug** to open a new Docker Desktop issue on GitHub. Complete the information required and ensure you add the diagnostic ID you copied in step three.
|
||||
|
||||
### Diagnose from an error message
|
||||
|
|
@ -76,7 +77,7 @@ If you are a Mac or Linux user, you also have the option to **Uninstall** Docker
|
|||
- If you have a paid Docker subscription, select **Contact support**. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied in step three to the **Diagnostics ID field**. Then, select **Submit ticket** to request Docker Desktop support.
|
||||
> [!NOTE]
|
||||
>
|
||||
> You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](../../support/_index.md).
|
||||
> You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](/manuals/desktop/troubleshoot-and-support/support.md).
|
||||
- If you don't have a paid Docker subscription, you can open a new Docker Desktop issue on GitHub for [Mac](https://github.com/docker/for-mac/issues), [Windows](https://github.com/docker/for-win/issues), or [Linux](https://github.com/docker/for-linux/issues). Complete the information required and ensure you add the diagnostic ID printed in step two.
|
||||
|
||||
### Diagnose from the terminal
|
||||
|
|
@ -57,7 +57,7 @@ After updating the `settings-store.json` file, close and restart Docker Desktop
|
|||
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](/manuals/desktop/settings.md#file-sharing).
|
||||
you might need to turn on [file sharing](/manuals/desktop/settings-and-maintenance/settings.md#file-sharing).
|
||||
|
||||
Volume mounting requires shared drives for projects that live outside of the
|
||||
`/home/<user>` directory. From **Settings**, select **Resources** and then **File sharing**. Share the drive that contains the Dockerfile and volume.
|
||||
|
|
@ -117,7 +117,7 @@ To continue using VPNKit, add `"networkType":"vpnkit"` to your `settings-store.j
|
|||
|
||||
#### Permissions errors on data directories for shared volumes
|
||||
|
||||
When sharing files from Windows, Docker Desktop sets permissions on [shared volumes](/manuals/desktop/settings.md#file-sharing)
|
||||
When sharing files from Windows, Docker Desktop sets permissions on [shared volumes](/manuals/desktop/settings-and-maintenance/settings.md#file-sharing)
|
||||
to a default value of [0777](https://chmodcommand.com/chmod-0777/)
|
||||
(`read`, `write`, `execute` permissions for `user` and for `group`).
|
||||
|
||||
|
|
@ -128,7 +128,7 @@ volumes or find a way to make the applications work with the default file
|
|||
permissions.
|
||||
|
||||
See also,
|
||||
[Can I change permissions on shared volumes for container-specific deployment requirements?](../faqs/windowsfaqs.md#can-i-change-permissions-on-shared-volumes-for-container-specific-deployment-requirements)
|
||||
[Can I change permissions on shared volumes for container-specific deployment requirements?](/manuals/desktop/troubleshoot-and-support/faqs/windowsfaqs.md#can-i-change-permissions-on-shared-volumes-for-container-specific-deployment-requirements)
|
||||
in the FAQs.
|
||||
|
||||
#### Volume mounting requires shared folders for Linux containers
|
||||
|
|
@ -136,14 +136,14 @@ 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](/manuals/desktop/settings.md#file-sharing).
|
||||
you might need to turn on [shared folders](/manuals/desktop/settings-and-maintenance/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.
|
||||
|
||||
#### Support for symlinks
|
||||
|
||||
Symlinks work within and across containers. To learn more, see [How do symlinks work on Windows?](../faqs/windowsfaqs.md#how-do-symlinks-work-on-windows).
|
||||
Symlinks work within and across containers. To learn more, see [How do symlinks work on Windows?](/manuals/desktop/troubleshoot-and-support/faqs/windowsfaqs.md#how-do-symlinks-work-on-windows).
|
||||
|
||||
#### Avoid unexpected syntax errors, use Unix style line endings for files in containers
|
||||
|
||||
|
|
@ -290,7 +290,7 @@ In the subsequent screen, verify that Hyper-V is enabled.
|
|||
|
||||
#### Virtualization must be turned on
|
||||
|
||||
In addition to [Hyper-V](#hyper-v) or [WSL 2](../wsl/_index.md), virtualization must be turned on. Check the
|
||||
In addition to [Hyper-V](#hyper-v) or [WSL 2](/manuals/desktop/wsl/_index.md), virtualization must be turned on. Check the
|
||||
Performance tab on the Task Manager. Alternatively, you can type 'systeminfo' into your terminal. If you see 'Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed', then virtualization is enabled.
|
||||
|
||||
|
||||
|
|
@ -327,7 +327,7 @@ Try [enabling nested virtualization](/manuals/desktop/setup/vm-vdi.md#turn-on-ne
|
|||
### Windows containers and Windows Server
|
||||
|
||||
Docker Desktop is not supported on Windows Server. If you have questions about how to run Windows containers on Windows 10, see
|
||||
[Switch between Windows and Linux containers](../faqs/windowsfaqs.md#how-do-i-switch-between-windows-and-linux-containers).
|
||||
[Switch between Windows and Linux containers](/manuals/desktop/troubleshoot-and-support/faqs/windowsfaqs.md#how-do-i-switch-between-windows-and-linux-containers).
|
||||
|
||||
A full tutorial is available in [docker/labs](https://github.com/docker/labs) on
|
||||
[Getting Started with Windows Containers](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md).
|
||||
|
|
@ -10,7 +10,7 @@ weight: 210
|
|||
>
|
||||
> Uninstalling Docker Desktop destroys Docker containers, images, volumes, and
|
||||
> other Docker-related data local to the machine, and removes the files generated
|
||||
> by the application. To learn how to preserve important data before uninstalling, refer to the [back up and restore data](backup-and-restore.md) section .
|
||||
> by the application. To learn how to preserve important data before uninstalling, refer to the [back up and restore data](/manuals/desktop/settings-and-maintenance/backup-and-restore.md) section .
|
||||
|
||||
{{< tabs >}}
|
||||
{{< tab name="Windows" >}}
|
||||
|
|
|
|||
|
|
@ -211,4 +211,4 @@ The **Builder settings** view in the Docker Desktop settings lets you:
|
|||
|
||||
|
||||
|
||||
For more information about managing builders, see [Change settings](/manuals/desktop/settings.md#builders)
|
||||
For more information about managing builders, see [Change settings](/manuals/desktop/settings-and-maintenance/settings.md#builders)
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ description: Discover Docker Desktop for Mac's Virtual Machine Manager (VMM) opt
|
|||
weight: 150
|
||||
---
|
||||
|
||||
The Virtual Machine Manager (VMM) in Docker Desktop for Mac is responsible for creating and managing the virtual machine used to run containers. Depending on your system architecture and performance needs, you can choose from multiple VMM options in Docker Desktop's [settings](/manuals/desktop/settings.md#general). This page provides an overview of the available options.
|
||||
The Virtual Machine Manager (VMM) in Docker Desktop for Mac is responsible for creating and managing the virtual machine used to run containers. Depending on your system architecture and performance needs, you can choose from multiple VMM options in Docker Desktop's [settings](/manuals/desktop/settings-and-maintenance/settings.md#general). This page provides an overview of the available options.
|
||||
|
||||
## Docker VMM (Beta)
|
||||
|
||||
|
|
|
|||
|
|
@ -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 settings](/manuals/desktop/settings.md)
|
||||
> Read more about this and other Windows settings at [Changing settings](/manuals/desktop/settings-and-maintenance/settings.md)
|
||||
|
||||
## Enabling Docker support in WSL 2 distros
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +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 Docker Desktop.
|
||||
For instructions, see [configuring Docker Desktop to use HTTP/HTTPS proxies](/manuals/desktop/settings.md#proxies).
|
||||
For instructions, see [configuring Docker Desktop to use HTTP/HTTPS proxies](/manuals/desktop/settings-and-maintenance/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)
|
||||
|
|
|
|||
|
|
@ -33,7 +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 [settings page](/manuals/desktop/settings.md#docker-engine).
|
||||
> using Docker Desktop, refer to the [settings page](/manuals/desktop/settings-and-maintenance/settings.md#docker-engine).
|
||||
|
||||
## Configure the Docker daemon
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Docker CLI to use a proxy server](/manuals/engine/cli/proxy.md).
|
|||
> [!IMPORTANT]
|
||||
> Proxy configurations specified in the `daemon.json` are ignored by Docker
|
||||
> Desktop. If you use Docker Desktop, you can configure proxies using the
|
||||
> [Docker Desktop settings](/manuals/desktop/settings.md#proxies).
|
||||
> [Docker Desktop settings](/manuals/desktop/settings-and-maintenance/settings.md#proxies).
|
||||
|
||||
There are two ways you can configure these settings:
|
||||
|
||||
|
|
|
|||
|
|
@ -100,7 +100,7 @@ on your development host. Use the following command to bind-mount the `target/`
|
|||
directory into your container at `/app/`. Run the command from within the
|
||||
`source` directory. The `$(pwd)` sub-command expands to the current working
|
||||
directory on Linux or macOS hosts.
|
||||
If you're on Windows, see also [Path conversions on Windows](/manuals/desktop/troubleshoot/topics.md).
|
||||
If you're on Windows, see also [Path conversions on Windows](/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md).
|
||||
|
||||
The `--mount` and `-v` examples below produce the same result. You
|
||||
can't run them both unless you remove the `devtest` container after running the
|
||||
|
|
|
|||
|
|
@ -62,7 +62,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.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-and-maintenance/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”
|
||||
|
|
|
|||
|
|
@ -1,101 +0,0 @@
|
|||
---
|
||||
description: Get support
|
||||
keywords: Support, Docker Desktop, Docker Hub, Hub, Linux, Mac, Windows
|
||||
title: Get support
|
||||
aliases:
|
||||
- /desktop/support/
|
||||
---
|
||||
|
||||
Find information on how to get support, and the scope of support.
|
||||
|
||||
## How do I get support?
|
||||
|
||||
If you have a paid Docker subscription, you can [contact the Support team](https://hub.docker.com/support/contact/).
|
||||
|
||||
All Docker users can seek support through the following resources, where Docker or the community respond on a best effort basis.
|
||||
- [Docker Desktop for Windows GitHub repo](https://github.com/docker/for-win)
|
||||
- [Docker Desktop for Mac GitHub repo](https://github.com/docker/for-mac)
|
||||
- [Docker Desktop for Linux GitHub repo](https://github.com/docker/desktop-linux)
|
||||
- [Docker Community Forums](https://forums.docker.com/)
|
||||
- [Docker Community Slack](http://dockr.ly/comm-slack)
|
||||
|
||||
|
||||
## What support can I get?
|
||||
|
||||
If you have a paid Docker subscription, you can get support for the following types of issues:
|
||||
|
||||
* Account management related issues
|
||||
* Automated builds
|
||||
* Basic product 'how to' questions
|
||||
* Billing or subscription issues
|
||||
* Configuration issues
|
||||
* Desktop installation issues
|
||||
* Installation crashes
|
||||
* Failure to launch Docker Desktop on first run
|
||||
* Desktop update issues
|
||||
* Sign-in issues in both the command line interface and Docker Hub user interface
|
||||
* Push or pull issues, including rate limiting
|
||||
* Usage issues
|
||||
* Crash closing software
|
||||
* Docker Desktop not behaving as expected
|
||||
|
||||
For Windows users, you can also request support on:
|
||||
* Turning on virtualization in BIOS
|
||||
* Turning on Windows features
|
||||
* Running inside [certain VM or VDI environments](/manuals/desktop/setup/vm-vdi.md) (Docker Business customers only)
|
||||
|
||||
|
||||
## What is not supported?
|
||||
|
||||
Docker excludes support for the following types of issues:
|
||||
* Altered or modified Docker software
|
||||
* Any version of the Docker software other than the latest version
|
||||
* Defects in the Docker software due to hardware malfunction, abuse, or improper use
|
||||
* Docker support excludes training, customization, and integration
|
||||
* Features labeled as experimental or beta
|
||||
* Reimbursing and expenses spent for third-party services not provided by Docker
|
||||
* Routine product maintenance (data backup, cleaning disk space and configuring log rotation)
|
||||
* Running containers of a different architecture using emulation
|
||||
* Running on unsupported operating systems, including beta or preview versions of operating systems
|
||||
* Scale deployment/multi-machine installation of Desktop
|
||||
* Support for Kubernetes
|
||||
* Support for the Docker Engine, Docker CLI, or other bundled Linux components
|
||||
* Supporting Desktop as a production runtime
|
||||
* System/Server administration activities
|
||||
* Third-party applications not provided by Docker
|
||||
* Use on or in conjunction with hardware or software other than that specified in the applicable documentation
|
||||
* Running multiple instances of Docker Desktop on a single machine
|
||||
|
||||
## What Docker Desktop versions are supported?
|
||||
|
||||
For Docker Business customers, Docker offers support for versions up to six months older than the latest version, although any fixes will be on the latest version.
|
||||
|
||||
For Pro and Team customers, Docker only offers support for the latest version of Docker Desktop. If you are running an older version, Docker may ask you to update before investigating your support request.
|
||||
|
||||
## How many machines can I get support for Docker Desktop on?
|
||||
|
||||
As a Pro user you can get support for Docker Desktop on a single machine.
|
||||
As a Team user, you can get support for Docker Desktop for the number of machines equal to the number of seats as part of your plan.
|
||||
|
||||
## What OS’s are supported?
|
||||
|
||||
Docker Desktop is available for Mac, Linux, and Windows. The supported version information can be found on the following pages:
|
||||
|
||||
* [Mac system requirements](/manuals/desktop/setup/install/mac-install.md#system-requirements)
|
||||
* [Windows system requirements](/manuals/desktop/setup/install/windows-install.md#system-requirements)
|
||||
* [Linux system requirements](/manuals/desktop/setup/install/linux/_index.md#system-requirements)
|
||||
|
||||
## How is personal diagnostic data handled in Docker Desktop?
|
||||
|
||||
When uploading diagnostics to help Docker with investigating issues, the uploaded diagnostics bundle may contain personal data such as usernames and IP addresses. The diagnostics bundles are only accessible to Docker, Inc.
|
||||
employees who are directly involved in diagnosing Docker Desktop issues.
|
||||
|
||||
By default, Docker, Inc. will delete uploaded diagnostics bundles after 30 days. You may also request the removal of a diagnostics bundle by either specifying the diagnostics ID or via your GitHub ID (if the diagnostics ID is mentioned in a GitHub issue). Docker, Inc. will only use the data in the diagnostics bundle to investigate specific user issues but may derive high-level (non personal) metrics such as the rate of issues from it.
|
||||
|
||||
For more information, see [Docker Data Processing Agreement](https://www.docker.com/legal/data-processing-agreement).
|
||||
|
||||
## What can I do before seeking support?
|
||||
|
||||
Before seeking support, you can perform basic troubleshooting. See [Diagnose and troubleshooting](/manuals/desktop/troubleshoot/_index.md) for more information.
|
||||
|
||||
You can also see if an answer already exists in the [FAQs](/tags/faq/).
|
||||
|
|
@ -88,7 +88,7 @@
|
|||
"/desktop/use-desktop/pause/":
|
||||
- /go/mac-desktop-pause/
|
||||
- /go/win-desktop-pause/
|
||||
"/desktop/settings/#file-sharing":
|
||||
"/desktop/settings-and-maintenance/settings/#file-sharing":
|
||||
- /go/mac-file-sharing/
|
||||
"/engine/security/rootless/":
|
||||
# Instructions on running docker in rootless mode. This redirect is currently
|
||||
|
|
|
|||
Loading…
Reference in New Issue