Skip to content

ENGDOCS-2298 #21339

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 5, 2024
Merged

ENGDOCS-2298 #21339

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/get-started/workshop/05_persisting_data.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 >}}
Expand Down
2 changes: 1 addition & 1 deletion content/get-started/workshop/06_bind_mounts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion content/guides/language-translation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion content/guides/named-entity-recognition.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion content/guides/sentiment-analysis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion content/guides/text-classification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion content/guides/text-summarization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
6 changes: 5 additions & 1 deletion content/manuals/accounts/create-account.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
2 changes: 1 addition & 1 deletion content/manuals/build/builders/manage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
2 changes: 1 addition & 1 deletion content/manuals/compose/install/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions content/manuals/desktop/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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/
Expand Down
2 changes: 1 addition & 1 deletion content/manuals/desktop/networking.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion content/manuals/desktop/previous-versions/2.x-windows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
28 changes: 14 additions & 14 deletions content/manuals/desktop/previous-versions/edge-releases-mac.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1560,9 +1560,9 @@

**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).

Check failure on line 1563 in content/manuals/desktop/previous-versions/edge-releases-mac.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.Capitalization] Please capitalize Docker.

Raw Output:
{"message": "[Docker.Capitalization] Please capitalize Docker.", "location": {"path": "content/manuals/desktop/previous-versions/edge-releases-mac.md", "range": {"start": {"line": 1563, "column": 62}}}, "severity": "ERROR"}

- 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**

Expand Down Expand Up @@ -1718,7 +1718,7 @@
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`.

Expand Down Expand Up @@ -1748,7 +1748,7 @@
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.

Expand Down Expand Up @@ -1782,7 +1782,7 @@
* 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`.

Expand All @@ -1808,7 +1808,7 @@

* 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

Expand All @@ -1831,7 +1831,7 @@

* 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

Expand Down Expand Up @@ -1878,7 +1878,7 @@

* 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).

Check failure on line 1881 in content/manuals/desktop/previous-versions/edge-releases-mac.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.Spacing] ' ' should have one space.

Raw Output:
{"message": "[Docker.Spacing] ' ' should have one space.", "location": {"path": "content/manuals/desktop/previous-versions/edge-releases-mac.md", "range": {"start": {"line": 1881, "column": 94}}}, "severity": "ERROR"}

* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart Docker.app

Expand Down Expand Up @@ -1922,7 +1922,7 @@

**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)

Expand All @@ -1948,7 +1948,7 @@

**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)

Expand All @@ -1969,7 +1969,7 @@

**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)

Expand All @@ -1988,7 +1988,7 @@

**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)

Expand All @@ -2010,7 +2010,7 @@

**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)

Expand All @@ -2034,7 +2034,7 @@

**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)

Expand Down
Loading
Loading