Skip to content

updates to troubleshooting page #24151

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

Closed
karman-docker wants to merge 3 commits into from
Closed

updates to troubleshooting page #24151

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d5d72ed
updates to troubleshooting page
karman-docker Feb 17, 2026
afe9f7e
update release requirement
karman-docker Feb 17, 2026
081d4b1
review comments
karman-docker Feb 17, 2026
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
21 changes: 17 additions & 4 deletions content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,10 +52,11 @@

### Diagnose from the app

1. From **Troubleshoot**, select **Get support**. This opens the in-app Support page and starts collecting the diagnostics.
2. When the diagnostics collection process is complete, select **Upload to get a Diagnostic ID**.
3. When the diagnostics are uploaded, Docker Desktop prints a diagnostic ID. Copy this ID.
4. Use your diagnostics ID to get help:
1. If the Docker Desktop Dashboard is unresponsive, you may be unable to generate a diagnostic bundle from the application. In that case, collect and upload the diagnostics using the terminal. Refer to the instructions in [Diagnose from the terminal](#diagnose-from-the-terminal) section below.

Check warning on line 55 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md

View workflow job for this annotation

GitHub Actions / validate (vale) 

[vale] reported by reviewdog 🐶
[Docker.RecommendedWords] Consider using 'following' instead of 'below'

Raw Output:
{"message": "[Docker.RecommendedWords] Consider using 'following' instead of 'below'", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md", "range": {"start": {"line": 55, "column": 289}}}, "severity": "INFO"}
Copy link
Contributor

@aevesdocker aevesdocker Feb 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't really a step, more of a callout. I'd move this whole line to below the steps and put it in a callout, maybe [!IMPORTANT]

2. From **Troubleshoot**, select **Get support**. This opens the in-app Support page and starts collecting the diagnostics.
3. When the diagnostics collection process is complete, select **Upload to get a Diagnostic ID**.
4. When the diagnostics are uploaded, Docker Desktop prints a diagnostic ID. Copy this ID.
5. Use your diagnostics ID to get help:
- If you have a paid Docker subscription, select **Contact support**. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied in step three to the **Diagnostics ID field**. Then, select **Submit ticket** to request Docker Desktop support.
> [!NOTE]
>
Expand All @@ -80,6 +81,10 @@

{{< tabs group="os" >}}
{{< tab name="Windows" >}}
#### Using docker CLI (Docker Desktop 4.60 and later)

Check failure on line 84 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md

View workflow job for this annotation

GitHub Actions / validate (vale) 

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

Raw Output:
{"message": "[Docker.Capitalization] Please capitalize Docker.", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md", "range": {"start": {"line": 84, "column": 11}}}, "severity": "ERROR"}
Copy link
Contributor

@aevesdocker aevesdocker Feb 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already have this info neatly in tip callout, so I don't think this is necessary here, I'd remove all these changes.

Image

Copy link
Contributor Author

@karman-docker karman-docker Feb 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry I didn't notice that. Agree, we can drop this change.

$ docker desktop diagnose

#### Using diagnose executable

1. Locate the `com.docker.diagnose` tool:

Expand All @@ -97,6 +102,10 @@

{{< /tab >}}
{{< tab name="Mac" >}}
#### Using docker CLI (Docker Desktop 4.60 and later)

Check failure on line 105 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md

View workflow job for this annotation

GitHub Actions / validate (vale) 

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

Raw Output:
{"message": "[Docker.Capitalization] Please capitalize Docker.", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md", "range": {"start": {"line": 105, "column": 11}}}, "severity": "ERROR"}
$ docker desktop diagnose

#### Using diagnose executable

1. Locate the `com.docker.diagnose` tool:

Expand All @@ -114,6 +123,10 @@

{{< /tab >}}
{{< tab name="Linux" >}}
#### Using docker CLI (Docker Desktop 4.60 and later)

Check failure on line 126 in content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md

View workflow job for this annotation

GitHub Actions / validate (vale) 

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

Raw Output:
{"message": "[Docker.Capitalization] Please capitalize Docker.", "location": {"path": "content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md", "range": {"start": {"line": 126, "column": 11}}}, "severity": "ERROR"}
$ docker desktop diagnose

#### Using diagnose executable

1. Locate the `com.docker.diagnose` tool:

Expand Down
Loading