docker · aevesdocker · Feb 27, 2025 · Feb 27, 2025 · Feb 28, 2025 · Feb 28, 2025
diff --git a/content/get-started/workshop/05_persisting_data.md b/content/get-started/workshop/05_persisting_data.md
@@ -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-and-support/troubleshoot/topics/#working-with-git-bash).
+   > [Working with Git Bash](/desktop/troubleshoot-and-support/troubleshoot/topics/#issue-docker-commands-failing-in-git-bash).
 
 
 {{< /tab >}}

diff --git a/content/guides/language-translation.md b/content/guides/language-translation.md
@@ -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-and-support/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/#Issue-Unexpected-syntax-errors-use-Unix-style-line endings-for-files-in-containers).
 
    You will see the following in your console after the container starts.
 

diff --git a/content/guides/named-entity-recognition.md b/content/guides/named-entity-recognition.md
@@ -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-and-support/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/#Issue-Unexpected-syntax-errors-use-Unix-style-line endings-for-files-in-containers).
 
    You will see the following in your console after the container starts.
 

diff --git a/content/guides/sentiment-analysis.md b/content/guides/sentiment-analysis.md
@@ -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-and-support/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/#Issue-Unexpected-syntax-errors-use-Unix-style-line endings-for-files-in-containers).
 
    You will see the following in your console after the container starts.
 

diff --git a/content/guides/text-classification.md b/content/guides/text-classification.md
@@ -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-and-support/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/#Issue-Unexpected-syntax-errors-use-Unix-style-line endings-for-files-in-containers).
 
    You will see the following in your console after the container starts.
 

diff --git a/content/guides/text-summarization.md b/content/guides/text-summarization.md
@@ -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-and-support/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/#Issue-Unexpected-syntax-errors-use-Unix-style-line endings-for-files-in-containers).
 
    You will see the following in your console after the container starts.
 

@@ -58,7 +58,7 @@ For details, see [Docker Engine API](/reference/api/engine/_index.md).
 ### How do I connect from a container to a service on the host?
 
 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`,
+It is 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](/manuals/desktop/features/networking.md#i-want-to-connect-from-a-container-to-a-service-on-the-host).

@@ -55,11 +55,11 @@
 supports subordinate ID delegation configured via files. Docker Desktop maps the
 current user ID and GID to 0 in the containers. It uses the first entry
 corresponding to the current user in `/etc/subuid` and `/etc/subgid` to set up
-mappings for IDs above 0 in the containers.
+mappings for IDs greater than 0 in the containers.
 
 | ID in container | ID on host                                                                       |
 | --------------- | -------------------------------------------------------------------------------- |
-| 0 (root)        | ID of the user running DD (e.g. 1000)                                            |
+| 0 (root)        | ID of the user running Docker Desktop (e.g. 1000)                                            |
 | 1               | 0 + beginning of ID range specified in `/etc/subuid`/`/etc/subgid` (e.g. 100000) |
 | 2               | 1 + beginning of ID range specified in `/etc/subuid`/`/etc/subgid` (e.g. 100001) |
 | 3               | 2 + beginning of ID range specified in `/etc/subuid`/`/etc/subgid` (e.g. 100002) |

@@ -11,34 +11,16 @@ aliases:
 weight: 20
 ---
 
-### Why do I keep getting a notification telling me an application has changed my Desktop configurations?
-
-You receive this notification because the Configuration integrity check feature has detected that a third-party application has altered your Docker Desktop configuration. This usually happens due to incorrect or missing symlinks. The notification ensures you are aware of these changes so you can review and repair any potential issues to maintain system reliability.
-
-Opening the notification presents a pop-up window which provides detailed information about the detected integrity issues.
-
-If you choose to ignore the notification, it will be shown again only at the next Docker Desktop startup. If you choose to repair your configuration, you won't be prompted again.
-
-If you want to switch off Configuration integrity check notifications, navigate to Docker Desktop's settings and in the **General** tab, clear the **Automatically check configuration** setting. 
-
-If you have feedback on how to further improve the Configuration integrity check feature, [fill out the feedback form](https://docs.google.com/forms/d/e/1FAIpQLSeD_Odqc__4ihRXDtH_ba52QJuaKZ00qGnNa_tM72MmH32CZw/viewform).
-
 ### What is HyperKit?
 
 HyperKit is a hypervisor built on top of the Hypervisor.framework in macOS. It runs entirely in userspace and has no other dependencies.
 
-We use HyperKit to eliminate the need for other VM products, such as Oracle
-VirtualBox or VMWare Fusion.
+Docker uses HyperKit to eliminate the need for other VM products, such as Oracle
+VirtualBox or VMware Fusion.
 
 ### What is the benefit of HyperKit?
 
-HyperKit is thinner than VirtualBox and VMWare fusion, and the version included is customized for Docker workloads on Mac.
-
-### Why is com.docker.vmnetd still running after I quit the app?
-
-The privileged helper process `com.docker.vmnetd` is started by `launchd` and
-runs in the background. The process does not consume any resources unless
-`Docker.app` connects to it, so it's safe to ignore.
+HyperKit is thinner than VirtualBox and VMware fusion, and the version included is customized for Docker workloads on Mac.
 
 ### Where does Docker Desktop store Linux containers and images? 
 

@@ -19,18 +19,6 @@ Docker Desktop uses the Windows Hyper-V features. While older Windows versions h
 
 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-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](/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md#permissions-errors-on-data-directories-for-shared-volumes).
-
 ### How do symlinks work on Windows?
 
 Docker Desktop supports two types of symlinks: Windows native symlinks and symlinks created inside a container.

@@ -317,5 +317,4 @@ to learn how to view the Docker Daemon logs.
 ## Further resources
 
 - View specific [troubleshoot topics](topics.md).
-- Implement [workarounds for common problems](workarounds.md)
 - View information on [known issues](known-issues.md)
@@ -9,20 +9,13 @@
 ---
 
 {{< tabs >}}
-{{< tab name="For all platforms" >}}
-* IPv6 is not yet supported on Docker Desktop.
-{{< /tab >}}
 {{< tab name="For Mac with Intel chip" >}}
-* The Mac Activity Monitor reports that Docker is using twice the amount of memory it's actually using. This is due to a bug in MacOS. We have written [a detailed report](https://docs.google.com/document/d/17ZiQC1Tp9iH320K-uqVLyiJmk4DHJ3c4zgQetJiKYQM/edit?usp=sharing) on this.
-
-* Force-ejecting the `.dmg` after running `Docker.app` from it can cause the
-  whale icon to become unresponsive, Docker tasks to show as not responding in
-  the Activity Monitor, and for some processes to consume a large amount of CPU
-  resources. Reboot and restart Docker to resolve these issues.
+- The Mac Activity Monitor reports that Docker is using twice the amount of memory it's actually using. This is due to a [bug in macOS].(https://docs.google.com/document/d/17ZiQC1Tp9iH320K-uqVLyiJmk4DHJ3c4zgQetJiKYQM/edit?usp=sharing) on this.
 
-* Docker doesn't auto-start after sign in even when it's enabled in **Settings**. This is related to a   set of issues with Docker helper, registration, and versioning.
+- Force-ejecting the `.dmg` after running `Docker.app` from it can cause the
+  whale icon to become unresponsive, Docker tasks to show as not responding in the Activity Monitor, and for some processes to consume a large amount of CPU resources. Reboot and restart Docker to resolve these issues.
 
-* Docker Desktop uses the `HyperKit` hypervisor
+- Docker Desktop uses the `HyperKit` hypervisor
   (https://github.com/docker/hyperkit) in macOS 10.10 Yosemite and higher. If
   you are developing with tools that have conflicts with `HyperKit`, such as
   [Intel Hardware Accelerated Execution Manager
@@ -32,7 +25,7 @@
   This allows you to continue work with the other tools and prevent `HyperKit`
   from interfering.
 
-* If you are working with applications like [Apache
+- If you are working with applications like [Apache
   Maven](https://maven.apache.org/) that expect settings for `DOCKER_HOST` and
   `DOCKER_CERT_PATH` environment variables, specify these to connect to Docker
   instances through Unix sockets. For example:
@@ -41,39 +34,18 @@
   $ export DOCKER_HOST=unix:///var/run/docker.sock
   ```
 
-* There are a number of issues with the performance of directories bind-mounted
-  into containers. 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. Applications that behave in this way
-  include:
-
-  - `rake`
-  - `ember build`
-  - Symfony
-  - Magento
-  - Zend Framework
-  - PHP applications that use [Composer](https://getcomposer.org) to install
-    dependencies in a `vendor` folder
-
-  As a workaround for this behavior, you can put vendor or third-party library
-  directories in Docker volumes, perform temporary file system operations
-  outside of bind mounts, and use third-party tools like Unison or `rsync` to
-  synchronize between container directories and bind-mounted directories. We are
-  actively working on performance improvements using a number of different
-  techniques.  To learn more, see the [topic on our roadmap](https://github.com/docker/roadmap/issues/7).
 {{< /tab >}}
 {{< tab name="For Mac with Apple silicon" >}}
-- On Apple silicon in native `arm64` containers, older versions of `libssl` such as `debian:buster`, `ubuntu:20.04`, and `centos:8` will segfault when connected to some TLS servers, for example, `curl https://dl.yarnpkg.com`. The bug is fixed in newer versions of `libssl` in `debian:bullseye`, `ubuntu:21.04`, and `fedora:35`.
+
 - Some command line tools do not work when Rosetta 2 is not installed.
   - The old version 1.x of `docker-compose`. Use Compose V2 instead - type `docker compose`.
   - The `docker-credential-ecr-login` credential helper.
 - Some images do not support the ARM64 architecture. You can add `--platform linux/amd64` to run (or build) an Intel image using emulation.
 
-   However, attempts to run Intel-based containers on Apple silicon machines under emulation can crash as qemu sometimes fails to run the container. In addition, filesystem change notification APIs (`inotify`) do not work under qemu emulation. Even when the containers do run correctly under emulation, they will be slower and use more memory than the native equivalent.
+   However, attempts to run Intel-based containers on Apple silicon machines under emulation can crash as QEMU sometimes fails to run the container. In addition, filesystem change notification APIs (`inotify`) do not work under QEMU emulation. Even when the containers do run correctly under emulation, they will be slower and use more memory than the native equivalent.
 
-   In summary, running Intel-based containers on Arm-based machines should be regarded as "best effort" only. We recommend running arm64 containers on Apple silicon machines whenever possible, and encouraging container authors to produce arm64, or multi-arch, versions of their containers. This issue should become less common over time, as more and more images are rebuilt [supporting multiple architectures](https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/).
-- `ping` from inside a container to the Internet does not work as expected.  To test the network, use `curl` or `wget`. See [docker/for-mac#5322](https://github.com/docker/for-mac/issues/5322#issuecomment-809392861).
+   In summary, running Intel-based containers on Arm-based machines should be regarded as "best effort" only. We recommend running `arm64` containers on Apple silicon machines whenever possible, and encouraging container authors to produce `arm64`, or multi-arch, versions of their containers. This issue should become less common over time, as more and more images are rebuilt [supporting multiple architectures](https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/).
 - Users may occasionally experience data drop when a TCP stream is half-closed.
+
 {{< /tab >}}
 {{< /tabs >}}