move some faqs

content/manuals/desktop/troubleshoot-and-support/faqs/macfaqs.md

@@ -11,18 +11,6 @@ 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.
@@ -34,12 +22,6 @@ VirtualBox or VMWare Fusion.
 
 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.
-
 ### Where does Docker Desktop store Linux containers and images? 
 
 Docker Desktop stores Linux containers and images in a single, large "disk image" file in the Mac filesystem. This is different from Docker on Linux, which usually stores containers and images in the `/var/lib/docker` directory.

content/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md

@@ -9,9 +9,6 @@ aliases:
 ---
 
 {{< 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.
 
@@ -20,8 +17,6 @@ aliases:
   the Activity Monitor, and for some processes to consume a large amount of CPU
   resources. Reboot and restart Docker to resolve these issues.
 
-* 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.
-
 * 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
@@ -73,7 +68,6 @@ aliases:
    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).
 - Users may occasionally experience data drop when a TCP stream is half-closed.
 {{< /tab >}}
 {{< /tabs >}}

content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

@@ -8,6 +8,7 @@
 weight: 10 
 aliases:
  - /desktop/troubleshoot/topics/
+ - /manuals/desktop/troubleshoot-and-support/troubleshoot/workarounds/
 ---
 
 > [!TIP]
@@ -48,7 +49,7 @@
 - If your registry is self-signed, configure Docker to trust the certificate by adding it to Docker’s certificates directory (/etc/docker/certs.d/ on Linux).
 - If the issue persists, check your Docker daemon configuration and enable TLS authentication.
 
 ### Issue: Docker Desktop's UI appears green, distorted, or has visual artifacts
 
 #### Cause
 
@@ -72,7 +73,7 @@
 
 3. Save the file and restart Docker Desktop.
 
 ### Issue: Using mounted volumes and getting runtime errors indicating an application file is not found, access to a volume mount is denied, or a service cannot start
 
 #### Cause
 
@@ -90,9 +91,40 @@
 1. From **Settings**, select **Shared Folders**. 
 2. Share the folder that contains the Dockerfile and volume mount paths.
 
+### Issue: `port already allocated` errors
+
+#### Error message
+
+When starting a container, you may see an error like:
+
+```text
+Bind for 0.0.0.0:8080 failed: port is already allocated
+```
+
+Or
+
+```text
+listen tcp:0.0.0.0:8080: bind: address is already in use
+```
+
+#### Cause
+
+- Another application on your system is already using the specified port.
+- A previously running container was not stopped properly and is still bound to the port.
+
+#### Solution
+
+To discover the identity of this software, either:
+- Use the `resmon.exe` GUI, select **Network** and then **Listening Ports**
+- In PowerShell, use `netstat -aon | find /i "listening "` to discover the PID of the process
+currently using the port (the PID is the number in the rightmost column). 
+
+Then, decide whether to shut the other process down, or to use a different port in your
+Docker app.
+
 ## Topics for Linux and Mac
 
 ### Issue: Docker Desktop fails to start on Mac or Linux platforms
 
 #### Error message 
 
@@ -124,6 +156,26 @@
 
 ## Topics for Mac
 
+### Issue: Persistent notification telling me an application has changed my Desktop configurations
+
+#### Cause 
+
+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.
+
+#### Solution
+
+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. 
+
+### Issue: `com.docker.vmnetd` is 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.
+
 ### Issue: Incompatible CPU detected
 
 #### Solution
@@ -149,7 +201,7 @@
 Reference](https://developer.apple.com/library/mac/documentation/DriversKernelHardware/Reference/Hypervisor/)
 in the Apple documentation, and Docker Desktop [Mac system requirements](/manuals/desktop/setup/install/mac-install.md#system-requirements).
 
 ### Issue: VPNKit keeps breaking
 
 #### Cause
 
@@ -157,7 +209,7 @@
 
 #### Solution
 
 To continue using VPNKit:
 
 1. Open your `settings-store.json` file located at `~/Library/Group Containers/group.com.docker/settings-store.json`
 2. Add:
@@ -169,7 +221,21 @@
 
 ## Topics for Windows
 
+### Issue: Docker Desktop fails to start when anti-virus software is installed
+
+#### Cause
+
+Some anti-virus software may be incompatible with Hyper-V and Microsoft
+Windows 10 builds. The conflict
+typically occurs after a Windows update and
+manifests as an error response from the Docker daemon and a Docker Desktop start failure.
+
+#### Solution
+
+For a temporary workaround, uninstall the anti-virus software, or
+add Docker to the exclusions/exceptions in your antivirus software.
+
 ### Issue: Permissions errors on data directories for shared volumes
 
 #### Cause 
 
@@ -186,11 +252,11 @@
  - Use non-host-mounted volumes  
  - Find a way to make the applications work with the default file permissions
 
 ### Issue: Unexpected syntax errors, use Unix style line endings for files in containers
 
 #### Cause 
 
 Docker containers expect Unix-style line `\n` endings, not Windows style: `\r\n`. This includes files referenced at the command line for builds and in RUN commands in Docker files.
 
 Keep this in mind when authoring files such as shell scripts using Windows
 tools, where the default is likely to be Windows style line endings. These