Skip to content
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

ENGDOCS-2451 #22117

Merged
merged 8 commits into from
Mar 6, 2025
+250 −271
Merged

ENGDOCS-2451 #22117

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
b038341
ENGDOCS-2451
aevesdocker Feb 27, 2025
f86de3c
move some faqs
aevesdocker Feb 27, 2025
1c3950f
edits
aevesdocker Feb 28, 2025
2187d5d
edits
aevesdocker Feb 28, 2025
58431cd
fix links
aevesdocker Feb 28, 2025
e79fb8d
review edits
aevesdocker Mar 4, 2025
4fe3e95
link fix
aevesdocker Mar 4, 2025
9fea886
toc tweak
aevesdocker Mar 6, 2025
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
Prev Previous commit
Next Next commit
review edits
  • Loading branch information
@aevesdocker
aevesdocker committed Mar 4, 2025
commit e79fb8dbc97087acb70bc3af2749d7d838cf1291
36 changes: 19 additions & 17 deletions content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md
View file
Original file line number Diff line number Diff line change
@@ -21,7 +21,7 @@

## Topics for all platforms

### Issue: Certificates not set up correctly
### Certificates not set up correctly

#### Error message

@@ -49,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
### Docker Desktop's UI appears green, distorted, or has visual artifacts

#### Cause

@@ -73,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
### 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

Check warning on line 76 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.HeadingLength] Try to keep headings short (< 8 words).

Raw Output:
{"message": "[Docker.HeadingLength] Try to keep headings short (\u003c 8 words).", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md", "range": {"start": {"line": 76, "column": 5}}}, "severity": "INFO"}

#### Cause

@@ -91,7 +91,7 @@
1. From **Settings**, select **Shared Folders**.
2. Share the folder that contains the Dockerfile and volume mount paths.

### Issue: `port already allocated` errors
### `port already allocated` errors

#### Error message

@@ -124,7 +124,7 @@

## Topics for Linux and Mac

### Issue: Docker Desktop fails to start on Mac or Linux platforms
### Docker Desktop fails to start on Mac or Linux platforms

Check warning on line 127 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.HeadingLength] Try to keep headings short (< 8 words).

Raw Output:
{"message": "[Docker.HeadingLength] Try to keep headings short (\u003c 8 words).", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md", "range": {"start": {"line": 127, "column": 5}}}, "severity": "INFO"}

#### Error message

@@ -156,7 +156,7 @@

## Topics for Mac

### Issue: Persistent notification telling me an application has changed my Desktop configurations
### Persistent notification telling me an application has changed my Desktop configurations

Check warning on line 159 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.HeadingLength] Try to keep headings short (< 8 words).

Raw Output:
{"message": "[Docker.HeadingLength] Try to keep headings short (\u003c 8 words).", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md", "range": {"start": {"line": 159, "column": 5}}}, "severity": "INFO"}

#### Cause

@@ -170,20 +170,22 @@

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
### `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
### Incompatible CPU detected

#### Solution
#### Cause

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

#### Solution

Check that:

- You've installed the correct Docker Desktop for your architecture
@@ -201,15 +203,15 @@
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
### 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 later.

Check failure on line 210 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'gVisor'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'gVisor'?", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md", "range": {"start": {"line": 210, "column": 33}}}, "severity": "ERROR"}

Check failure on line 210 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'vpnkit' instead of 'VPNKit'.

Raw Output:
{"message": "[Vale.Terms] Use 'vpnkit' instead of 'VPNKit'.", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md", "range": {"start": {"line": 210, "column": 49}}}, "severity": "ERROR"}

#### Solution

To continue using VPNKit:

Check failure on line 214 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'vpnkit' instead of 'VPNKit'.

Raw Output:
{"message": "[Vale.Terms] Use 'vpnkit' instead of 'VPNKit'.", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md", "range": {"start": {"line": 214, "column": 19}}}, "severity": "ERROR"}

1. Open your `settings-store.json` file located at `~/Library/Group Containers/group.com.docker/settings-store.json`
2. Add:
@@ -221,7 +223,7 @@

## Topics for Windows

### Issue: Docker Desktop fails to start when anti-virus software is installed
### Docker Desktop fails to start when anti-virus software is installed

Check warning on line 226 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.HeadingLength] Try to keep headings short (< 8 words).

Raw Output:
{"message": "[Docker.HeadingLength] Try to keep headings short (\u003c 8 words).", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md", "range": {"start": {"line": 226, "column": 5}}}, "severity": "INFO"}

#### Cause

@@ -235,7 +237,7 @@
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
### Permissions errors on data directories for shared volumes

#### Cause

@@ -252,11 +254,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
### Unexpected syntax errors, use Unix style line endings for files in containers

Check warning on line 257 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.HeadingLength] Try to keep headings short (< 8 words).

Raw Output:
{"message": "[Docker.HeadingLength] Try to keep headings short (\u003c 8 words).", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md", "range": {"start": {"line": 257, "column": 5}}}, "severity": "INFO"}

#### 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.

Check warning on line 261 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.Acronyms] 'RUN' has no definition.

Raw Output:
{"message": "[Docker.Acronyms] 'RUN' has no definition.", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md", "range": {"start": {"line": 261, "column": 152}}}, "severity": "WARNING"}

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
@@ -271,9 +273,9 @@
```console
$ dos2unix script.sh
```
- In VS Code, set line endings to `LF` (Unix) instead of `CRLF` (Windows).

Check warning on line 276 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.Acronyms] 'VS' has no definition.

Raw Output:
{"message": "[Docker.Acronyms] 'VS' has no definition.", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md", "range": {"start": {"line": 276, "column": 6}}}, "severity": "WARNING"}

Check warning on line 276 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Docker.RecommendedWords] Consider using 'versus' instead of 'VS'

Raw Output:
{"message": "[Docker.RecommendedWords] Consider using 'versus' instead of 'VS'", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md", "range": {"start": {"line": 276, "column": 6}}}, "severity": "INFO"}

### Issue: Path conversion errors on Windows
### Path conversion errors on Windows

#### Cause

@@ -306,7 +308,7 @@
$ docker run --rm -ti -v /c/Users/user/work:/work alpine ls /work
```

### Issue: Docker commands failing in Git Bash
### Docker commands failing in Git Bash

#### Error message

@@ -341,7 +343,7 @@

Portability of the scripts is not affected as Linux treats multiple `/` as a single entry.

### Issue: Docker Desktop fails due to Virtualization settings
### Docker Desktop fails due to Virtualization settings

#### Cause

@@ -420,7 +422,7 @@

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
### `Docker Desktop Access Denied` error message when starting Docker Desktop

#### Error message

Loading