From b0383414a49fabf9534610d5e680639b40f36e27 Mon Sep 17 00:00:00 2001 From: aevesdocker Date: Thu, 27 Feb 2025 13:28:32 +0000 Subject: [PATCH 1/5] ENGDOCS-2451 --- .../faqs/windowsfaqs.md | 12 - .../troubleshoot/topics.md | 301 ++++++++++-------- 2 files changed, 161 insertions(+), 152 deletions(-) diff --git a/content/manuals/desktop/troubleshoot-and-support/faqs/windowsfaqs.md b/content/manuals/desktop/troubleshoot-and-support/faqs/windowsfaqs.md index 949fc957435..ea1da99fc25 100644 --- a/content/manuals/desktop/troubleshoot-and-support/faqs/windowsfaqs.md +++ b/content/manuals/desktop/troubleshoot-and-support/faqs/windowsfaqs.md @@ -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. diff --git a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md index 8d6b14f013a..6425d9b6f0f 100644 --- a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md +++ b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md @@ -20,57 +20,83 @@ aliases: ## Topics for all platforms -### Make sure certificates are set up correctly +### Issue: Certificates not set up correctly -Docker Desktop ignores certificates listed under insecure registries, and -does not send client certificates to them. Commands like `docker run` that -attempt to pull from the registry produces error messages on the command line, -like this: +#### Error message + +When attempting to pull from a registry using `docker run`, you may encounter the following error: ```console Error response from daemon: Get http://192.168.203.139:5858/v2/: malformed HTTP response "\x15\x03\x01\x00\x02\x02" ``` -As well as on the registry. For example: +Additionally, logs from the registry may show: ```console 2017/06/20 18:15:30 http: TLS handshake error from 192.168.203.139:52882: tls: client didn't provide a certificate 2017/06/20 18:15:30 http: TLS handshake error from 192.168.203.139:52883: tls: first record does not look like a TLS handshake ``` -### Docker Desktop's UI appears green, distorted, or has visual artifacts +#### Possible causes -Docker Desktop uses hardware-accelerated graphics by default, which may cause problems for some GPUs. In such cases, -Docker Desktop will launch successfully, but some screens may appear green, distorted, -or have some visual artifacts. +- Docker Desktop ignores certificates listed under insecure registries. +- Client certificates are not sent to insecure registries, causing handshake failures. -To work around this issue, disable hardware acceleration by creating a `"disableHardwareAcceleration": true` entry in Docker Desktop's `settings-store.json` file (or `settings.json` for Docker Desktop versions 4.34 and earlier). You can find this file at: +#### Solution -- Mac: `~/Library/Group Containers/group.com.docker/settings-store.json` -- Windows: `C:\Users\[USERNAME]\AppData\Roaming\Docker\settings-store.json` -- Linux: `~/.docker/desktop/settings-store.json.` +- Ensure that your registry is properly configured with valid SSL certificates. +- 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. -After updating the `settings-store.json` file, close and restart Docker Desktop to apply the changes. +### Issue: Docker Desktop's UI appears green, distorted, or has visual artifacts -## Topics for Linux and Mac +#### Cause + +Docker Desktop uses hardware-accelerated graphics by default, which may cause problems for some GPUs. + +#### Solution + +Disable hardware acceleration: + +1. Edit Docker Desktop's `settings-store.json` file (or `settings.json` for Docker Desktop versions 4.34 and earlier). You can find this file at: + + - Mac: `~/Library/Group Containers/group.com.docker/settings-store.json` + - Windows: `C:\Users\[USERNAME]\AppData\Roaming\Docker\settings-store.json` + - Linux: `~/.docker/desktop/settings-store.json.` + +2. Add the following entry: -### Volume mounting requires file sharing for any project directories outside of `$HOME` + ```JSON + $ "disableHardwareAcceleration": true + ``` -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-and-maintenance/settings.md#file-sharing). +3. Save the file and restart Docker Desktop. -Volume mounting requires shared drives for projects that live outside of the -`/home/` directory. From **Settings**, select **Resources** and then **File sharing**. Share the drive that contains the Dockerfile and volume. +### 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 -### Docker Desktop fails to start on MacOS or Linux platforms +#### Cause + +If your project directory is located outside your home directory (`/home/`), Docker Desktop requires file sharing permissions to access it. + +#### Solution + +Enable file sharing in Docker Desktop for Mac and Linux: + +1. Navigate to **Settings**, select **Resources** and then **File sharing**. +2. Add the drive or folder that contains the Dockerfile and volume mount paths. + +Enable file sharing in Docker Desktop for Windows: + +1. From **Settings**, select **Shared Folders**. +2. Share the folder that contains the Dockerfile and volume mount paths. + +## Topics for Linux and Mac -On MacOS and Linux, Docker Desktop creates Unix domain sockets used for inter-process communication. +### Issue: Docker Desktop fails to start on Mac or Linux platforms -Docker fails to start if the absolute path length of any of these sockets exceeds the OS limitation which is 104 characters on MacOS and 108 characters on Linux. These sockets are created under the user's home directory. If the user ID length is such that the absolute path of the socket exceeds the OS path length limitation, then Docker Desktop is unable to create the socket and fails to start. The workaround for this is to shorten the user ID which we recommend has a maximum length of 33 characters on MacOS and 55 characters on Linux. +#### Error message -Following are the examples of errors on MacOS which indicate that the startup failure was due to exceeding the above mentioned OS limitation: +Docker fails to start due to Unix domain socket path length limitations: ```console [vpnkit-bridge][F] listen unix /Library/Containers/com.docker.docker/Data/http-proxy-control.sock: bind: invalid argument @@ -80,96 +106,113 @@ Following are the examples of errors on MacOS which indicate that the startup fa [com.docker.backend][E] listen(vsock:4099) failed: listen unix /Library/Containers/com.docker.docker/Data/vms/0/00000002.00001003: bind: invalid argument ``` +#### Cause + +On Mac and Linux, Docker Desktop creates Unix domain sockets used for inter-process communication. These sockets are created under the user's home directory. + +Unix domain sockets have a maximum path length: + - 104 characters on Mac + - 108 characters on Linux + +If your home directory path is too long, Docker Desktop fails to create necessary sockets. + +#### Solution + +Ensure your username is short enough to keep paths within the allowed limit: + - Mac: Username should be ≤ 33 characters + - Linux: Username should be ≤ 55 characters + ## Topics for Mac -### Incompatible CPU detected +### Issue: Incompatible CPU detected -> [!TIP] -> -> If you are seeing this error, check you've installed the correct Docker Desktop for your architecture. +#### Solution Docker Desktop requires a processor (CPU) that supports virtualization and, more specifically, the [Apple Hypervisor framework](https://developer.apple.com/library/mac/documentation/DriversKernelHardware/Reference/Hypervisor/). -Docker Desktop is only compatible with Mac systems that have a CPU that supports the Hypervisor framework. Most Macs built in 2010 and later support it,as described in the Apple Hypervisor Framework documentation about supported hardware: -*Generally, machines with an Intel VT-x feature set that includes Extended Page -Tables (EPT) and Unrestricted Mode are supported.* +Check that: -To check if your Mac supports the Hypervisor framework, run the following command in a terminal window. + - You've installed the correct Docker Desktop for your architecture + - Your Mac supports Apple's Hypervisor framework. To check if your Mac supports the Hypervisor framework, run the following command in a terminal window. -```console -$ sysctl kern.hv_support -``` + ```console + $ sysctl kern.hv_support + ``` -If your Mac supports the Hypervisor Framework, the command prints -`kern.hv_support: 1`. + If your Mac supports the Hypervisor Framework, the command prints `kern.hv_support: 1`. -If not, the command prints `kern.hv_support: 0`. + If not, the command prints `kern.hv_support: 0`. See also, [Hypervisor Framework 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). -### VPNKit keeps breaking +### Issue: VPNKit keeps breaking + +#### Cause In Docker Desktop version 4.19, gVisor replaced VPNKit to enhance the performance of VM networking when using the Virtualization framework on macOS 13 and above. -To continue using VPNKit, add `"networkType":"vpnkit"` to your `settings-store.json` file located at `~/Library/Group Containers/group.com.docker/settings-store.json`. +#### 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: + + ```JSON + $ "networkType":"vpnkit" + ``` +3. Save the file and restart Docker Desktop. ## Topics for Windows -### Volumes +### Issue: Permissions errors on data directories for shared volumes -#### Permissions errors on data directories for shared volumes +#### Cause 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`). -The default permissions on shared volumes are not configurable. If you are -working with applications that require permissions different from the shared -volume defaults at container runtime, you need to either use non-host-mounted -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?](/manuals/desktop/troubleshoot-and-support/faqs/windowsfaqs.md#can-i-change-permissions-on-shared-volumes-for-container-specific-deployment-requirements) -in the FAQs. +The default permissions on shared volumes are not configurable. -#### Volume mounting requires shared folders for Linux containers +#### Solution -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-and-maintenance/settings.md#file-sharing). +If you are +working with applications that require different permissions, either: + - Use non-host-mounted volumes + - Find a way to make the applications work with the default file permissions -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. +### Issue: Unexpected syntax errors, use Unix style line endings for files in containers -#### Support for symlinks +#### Cause -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). +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. -#### Avoid unexpected syntax errors, use Unix style line endings for files in containers - -Any file destined to run inside a container must use Unix style `\n` line -endings. This includes files referenced at the command line for builds and in -RUN commands in Docker files. - -Docker containers and `docker build` run in a Unix environment, so files in -containers must use Unix style line endings: `\n`, _not_ Windows style: `\r\n`. 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 commands ultimately get passed to Unix commands inside a Unix based container (for example, a shell script passed to `/bin/sh`). If Windows style line endings are used, `docker run` fails with syntax errors. -For an example of this issue and the resolution, see this issue on GitHub: -[Docker RUN fails to execute shell -script](https://github.com/moby/moby/issues/24388). +#### Solution + + - Convert files to Unix-style line endings using: + + ```console + $ dos2unix script.sh + ``` +- In VS Code, set line endings to `LF` (Unix) instead of `CRLF` (Windows). + +### Issue: Path conversion errors on Windows + +#### Cause + +Unlike Linux, Windows requires explicit path conversion for volume mounting. -#### Path conversion on Windows On Linux, the system takes care of mounting a path to another path. For example, when you run the following command on Linux: @@ -179,7 +222,9 @@ $ docker run --rm -ti -v /home/user/work:/work alpine It adds a `/work` directory to the target container to mirror the specified path. -However, on Windows, you must update the source path. For example, if you are using +#### Solution + +Update the source path. For example, if you are using the legacy Windows shell (`cmd.exe`), you can use the following command: ```console @@ -195,73 +240,53 @@ Docker Desktop also allows you to use Unix-style path to the appropriate format. $ docker run --rm -ti -v /c/Users/user/work:/work alpine ls /work ``` -#### Working with Git Bash +### Issue: Docker commands failing in Git Bash -Git Bash (or MSYS) provides a Unix-like environment on Windows. These tools apply their own -preprocessing on the command line. For example, if you run the following command in Git Bash, it gives an error: +#### Error message: ```console $ docker run --rm -ti -v C:\Users\user\work:/work alpine docker: Error response from daemon: mkdir C:UsersUserwork: Access is denied. ``` -This is because the `\` character has a special meaning in Git Bash. If you are using Git Bash, you must neutralize it using `\\`: - -```console -$ docker run --rm -ti -v C:\\Users\\user\\work:/work alpine -``` - -Also, in scripts, the `pwd` command is used to avoid hard-coding file system locations. Its output is a Unix-style path. - -```console -$ pwd -/c/Users/user/work -``` - -Combined with the `$()` syntax, the command below works on Linux, however, it fails on Git Bash. - ```console $ docker run --rm -ti -v $(pwd):/work alpine docker: Error response from daemon: OCI runtime create failed: invalid mount {Destination:\Program Files\Git\work Type:bind Source:/run/desktop/mnt/host/c/Users/user/work;C Options:[rbind rprivate]}: mount destination \Program Files\Git\work not absolute: unknown. ``` -You can work around this issue by using an extra `/` +#### Cause -```console -$ docker run --rm -ti -v /$(pwd):/work alpine -``` +Git Bash (or MSYS) provides a Unix-like environment on Windows. These tools apply their own +preprocessing on the command line. -Portability of the scripts is not affected as Linux treats multiple `/` as a single entry. -Each occurrence of paths on a single line must be neutralized. +This affects `$(pwd)`, colon-separated paths, and tilde (`~`) -```console -$ docker run --rm -ti -v /$(pwd):/work alpine ls /work -ls: C:/Program Files/Git/work: No such file or directory -``` +Also, the `\` character has a special meaning in Git Bash. -In this example, The `$(pwd)` is not converted because of the preceding '/'. However, the second '/work' is transformed by the -POSIX layer before passing it to Docker Desktop. You can also work around this issue by using an extra `/`. +#### Solution -```console -$ docker run --rm -ti -v /$(pwd):/work alpine ls //work -``` + - Disable Git Bash path conversion temporarily. For example, run the command with MSYS path conversion disable: + ```console + $ MSYS_NO_PATHCONV=1 docker run --rm -ti -v $(pwd):/work alpine + ``` + - Use proper path formatting: + - Use double forward and backslashes (`\\` `//`) instead of single (`\` `/`). + - If referencing `$(pwd)`, add an extra `/`: -To verify whether the errors are generated from your script, or from another source, you can use an environment variable. For example: +Portability of the scripts is not affected as Linux treats multiple `/` as a single entry. -```console -$ MSYS_NO_PATHCONV=1 docker run --rm -ti -v $(pwd):/work alpine ls /work -``` +### Issue: Docker Desktop fails due to Virtualization settings -It only expects the environment variable here. The value doesn't matter. +#### Cause -In some cases, MSYS also transforms colons to semicolon. Similar conversions can also occur -when using `~` because the POSIX layer translates it to a DOS path. `MSYS_NO_PATHCONV` also works in this case. +- Virtualization settings are disabled in the BIOS. +- Windows Hyper-V or WSL 2 components are missing. -### Virtualization +#### Solutions Your machine must have the following features for Docker Desktop to function correctly: -#### WSL 2 and Windows Home +##### WSL 2 and Windows Home 1. Virtual Machine Platform 2. [Windows Subsystem for Linux](https://docs.microsoft.com/en-us/windows/wsl/install-win10) @@ -271,7 +296,7 @@ Your machine must have the following features for Docker Desktop to function cor ![WSL 2 enabled](../../images/wsl2-enabled.png) -#### Hyper-V +##### Hyper-V On Windows 10 Pro or Enterprise, you can also use Hyper-V with the following features enabled: @@ -294,10 +319,10 @@ To install Hyper-V manually, see [Install Hyper-V on Windows 10](https://msdn.mi From the start menu, type **Turn Windows features on or off** and press enter. In the subsequent screen, verify that Hyper-V is enabled. -#### Virtualization must be turned on +##### Virtualization must be turned on In addition to [Hyper-V](#hyper-v) or [WSL 2](/manuals/desktop/features/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. +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. ![Task Manager](../../images/virtualization-enabled.png) @@ -306,7 +331,7 @@ Docker Desktop cannot start. To turn on nested virtualization, see [Run Docker Desktop for Windows in a VM or VDI environment](/manuals/desktop/setup/vm-vdi.md#turn-on-nested-virtualization). -#### Hypervisor enabled at Windows startup +##### Hypervisor enabled at Windows startup If you have completed the steps described above and are still experiencing Docker Desktop startup issues, this could be because the Hypervisor is installed, @@ -319,7 +344,7 @@ Virtual Box) and video game installers turn off hypervisor on boot. To turn it b You can also refer to the [Microsoft TechNet article](https://social.technet.microsoft.com/Forums/en-US/ee5b1d6b-09e2-49f3-a52c-820aafc316f9/hyperv-doesnt-work-after-upgrade-to-windows-10-1809?forum=win10itprovirt) on Code flow guard (CFG) settings. -#### Turn on nested virtualization +##### Turn on nested virtualization If you are using Hyper-V and you get the following error message when running Docker Desktop in a VDI environment: @@ -329,29 +354,25 @@ The Virtual Machine Management Service failed to start the virtual machine 'Dock Try [enabling nested virtualization](/manuals/desktop/setup/vm-vdi.md#turn-on-nested-virtualization). +### Issue: `Docker Desktop Access Denied` error message when starting Docker Desktop -### 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](/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). +#### Error message -You can install a native Windows binary which allows you to develop and run -Windows containers without Docker Desktop. However, if you install Docker this way, you cannot develop or run Linux containers. If you try to run a Linux container on the native Docker daemon, an error occurs: +When starting Docker Desktop, the following error appears: -```none -C:\Program Files\Docker\docker.exe: - image operating system "linux" cannot be used on this platform. - See 'C:\Program Files\Docker\docker.exe run --help'. +```text +Docker Desktop - Access Denied ``` -### `Docker Desktop Access Denied` error message when starting Docker Desktop +#### Cause -Docker Desktop displays the **Docker Desktop - Access Denied** error if a Windows user is not part of the **docker-users** group. +The user is not part of the `docker-users` group, which is required for permissions. -If your admin account is different to your user account, add the **docker-users** group. Run **Computer Management** as an administrator and navigate to **Local Users and Groups** > **Groups** > **docker-users**. +#### Solution -Right-click to add the user to the group. Sign out and sign back in for the changes to take effect. +If your admin account is different to your user account, add it: +1. Run **Computer Management** as an administrator. +2. Navigate to **Local Users and Groups** > **Groups** > **docker-users**. +3. Right-click to add the user to the group. +4. Sign out and sign back in for the changes to take effect From f86de3cb7cd0ba68235a19816c9be3d96bdee345 Mon Sep 17 00:00:00 2001 From: aevesdocker Date: Thu, 27 Feb 2025 16:48:09 +0000 Subject: [PATCH 2/5] move some faqs --- .../troubleshoot-and-support/faqs/macfaqs.md | 18 ----- .../troubleshoot/known-issues.md | 6 -- .../troubleshoot/topics.md | 66 +++++++++++++++++++ .../troubleshoot/workarounds.md | 51 -------------- 4 files changed, 66 insertions(+), 75 deletions(-) delete mode 100644 content/manuals/desktop/troubleshoot-and-support/troubleshoot/workarounds.md diff --git a/content/manuals/desktop/troubleshoot-and-support/faqs/macfaqs.md b/content/manuals/desktop/troubleshoot-and-support/faqs/macfaqs.md index e1129dbd0cd..7a3f1ce6cd2 100644 --- a/content/manuals/desktop/troubleshoot-and-support/faqs/macfaqs.md +++ b/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. diff --git a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md index 6cef6929241..46963190b99 100644 --- a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md +++ b/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 >}} diff --git a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md index 6425d9b6f0f..3b36d8262b5 100644 --- a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md +++ b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md @@ -8,6 +8,7 @@ tags: [ Troubleshooting ] weight: 10 aliases: - /desktop/troubleshoot/topics/ + - /manuals/desktop/troubleshoot-and-support/troubleshoot/workarounds/ --- > [!TIP] @@ -90,6 +91,37 @@ Enable file sharing in Docker Desktop for Windows: 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 @@ -124,6 +156,26 @@ Ensure your username is short enough to keep paths within the allowed limit: ## 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 @@ -169,6 +221,20 @@ To continue using VPNKit: ## 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 diff --git a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/workarounds.md b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/workarounds.md deleted file mode 100644 index 8720454e17e..00000000000 --- a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/workarounds.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -description: Common workarounds -keywords: linux, mac, windows, troubleshooting, workarounds, Docker Desktop -title: Workarounds for common problems -tags: [ Troubleshooting ] -weight: 20 -aliases: - - /desktop/troubleshoot/workarounds/ ---- - -### Reboot - -Restart your PC to stop / discard any vestige of the daemon running from the -previously installed version. - -### Unset `DOCKER_HOST` - -The `DOCKER_HOST` environmental variable does not need to be set. If you use -bash, use the command `unset ${!DOCKER_*}` to unset it. For other shells, -consult the shell's documentation. - -### Make sure Docker is running for webserver examples - -For the `hello-world-nginx` example and others, Docker Desktop must be -running to get to the webserver on `http://localhost/`. Make sure that the -Docker whale is showing in the menu bar, and that you run the Docker commands in -a shell that is connected to the Docker Desktop Engine. Otherwise, you might start the webserver container but get a "web page -not available" error when you go to `docker`. - -### How to solve `port already allocated` errors - -If you see errors like `Bind for 0.0.0.0:8080 failed: port is already allocated` -or `listen tcp:0.0.0.0:8080: bind: address is already in use` ... - -These errors are often caused by some other software on Windows using those -ports. To discover the identity of this software, either use the `resmon.exe` -GUI and click "Network" and then "Listening Ports" or in a 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). Decide -whether to shut the other process down, or to use a different port in your -docker app. - -### Docker Desktop fails to start when anti-virus software is installed - -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. - -For a temporary workaround, uninstall the anti-virus software, or -explore other workarounds suggested on Docker Desktop forums. From 1c3950f586ef19fbb6211d32c927d14368643859 Mon Sep 17 00:00:00 2001 From: aevesdocker Date: Fri, 28 Feb 2025 10:08:09 +0000 Subject: [PATCH 3/5] edits --- .../troubleshoot-and-support/faqs/general.md | 2 +- .../faqs/linuxfaqs.md | 4 +- .../troubleshoot-and-support/faqs/macfaqs.md | 6 +-- .../troubleshoot/known-issues.md | 40 +++++-------------- .../troubleshoot/topics.md | 6 +-- 5 files changed, 18 insertions(+), 40 deletions(-) diff --git a/content/manuals/desktop/troubleshoot-and-support/faqs/general.md b/content/manuals/desktop/troubleshoot-and-support/faqs/general.md index cbfe06a3f75..d21afd8e306 100644 --- a/content/manuals/desktop/troubleshoot-and-support/faqs/general.md +++ b/content/manuals/desktop/troubleshoot-and-support/faqs/general.md @@ -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). diff --git a/content/manuals/desktop/troubleshoot-and-support/faqs/linuxfaqs.md b/content/manuals/desktop/troubleshoot-and-support/faqs/linuxfaqs.md index 3f8729ba6e9..5257cfb3206 100644 --- a/content/manuals/desktop/troubleshoot-and-support/faqs/linuxfaqs.md +++ b/content/manuals/desktop/troubleshoot-and-support/faqs/linuxfaqs.md @@ -55,11 +55,11 @@ and `/etc/subgid` (see `subgid(5)`) must be present. Docker Desktop only 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) | diff --git a/content/manuals/desktop/troubleshoot-and-support/faqs/macfaqs.md b/content/manuals/desktop/troubleshoot-and-support/faqs/macfaqs.md index 7a3f1ce6cd2..d11a00f7db2 100644 --- a/content/manuals/desktop/troubleshoot-and-support/faqs/macfaqs.md +++ b/content/manuals/desktop/troubleshoot-and-support/faqs/macfaqs.md @@ -15,12 +15,12 @@ weight: 20 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. +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? diff --git a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md index 46963190b99..d4d6afc5638 100644 --- a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md +++ b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/known-issues.md @@ -10,14 +10,12 @@ aliases: {{< tabs >}} {{< 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. +- 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. -* 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. +- 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 @@ -27,7 +25,7 @@ aliases: 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: @@ -36,38 +34,18 @@ aliases: $ 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/). + 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 >}} diff --git a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md index 3b36d8262b5..b62a879c503 100644 --- a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md +++ b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md @@ -205,7 +205,7 @@ in the Apple documentation, and Docker Desktop [Mac system requirements](/manual #### Cause -In Docker Desktop version 4.19, gVisor replaced VPNKit to enhance the performance of VM networking when using the Virtualization framework on macOS 13 and above. +In Docker Desktop version 4.19, gVisor replaced VPNKit to enhance the performance of VM networking when using the Virtualization framework on macOS 13 and later. #### Solution @@ -308,7 +308,7 @@ $ docker run --rm -ti -v /c/Users/user/work:/work alpine ls /work ### Issue: Docker commands failing in Git Bash -#### Error message: +#### Error message ```console $ docker run --rm -ti -v C:\Users\user\work:/work alpine @@ -399,7 +399,7 @@ To turn on nested virtualization, see [Run Docker Desktop for Windows in a VM or ##### Hypervisor enabled at Windows startup -If you have completed the steps described above and are still experiencing +If you have completed the previous steps and are still experiencing Docker Desktop startup issues, this could be because the Hypervisor is installed, but not launched during Windows startup. Some tools (such as older versions of Virtual Box) and video game installers turn off hypervisor on boot. To turn it back on: From 2187d5d3367fe2b3eca19df847050aee5be9bad2 Mon Sep 17 00:00:00 2001 From: aevesdocker Date: Fri, 28 Feb 2025 10:11:02 +0000 Subject: [PATCH 4/5] edits --- .../desktop/troubleshoot-and-support/troubleshoot/_index.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md index 730ac70575e..622441faf00 100644 --- a/content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md +++ b/content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md @@ -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) From 58431cde0bc33f18c495774222008926fa8b96b6 Mon Sep 17 00:00:00 2001 From: aevesdocker Date: Fri, 28 Feb 2025 10:20:48 +0000 Subject: [PATCH 5/5] fix links --- content/get-started/workshop/05_persisting_data.md | 2 +- content/guides/language-translation.md | 2 +- content/guides/named-entity-recognition.md | 2 +- content/guides/sentiment-analysis.md | 2 +- content/guides/text-classification.md | 2 +- content/guides/text-summarization.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/get-started/workshop/05_persisting_data.md b/content/get-started/workshop/05_persisting_data.md index 60b0e17c2b7..5efae0461dd 100644 --- 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 index 64ad491c935..f6464647de0 100644 --- 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 index 8c5e087c072..b39d91e0077 100644 --- 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 index ea6f5ab5a41..e5d666e4767 100644 --- 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 index 6c3e6ee4a8f..a17a3f14e9d 100644 --- 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 index ef6cbd290df..4e1cb1d0cd2 100644 --- 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.