mirror of https://github.com/docker/docs.git
troubleshoot fix (#17778)
* troubleshoot fix * fix build * fix build * fix build * fix build --------- Co-authored-by: aevesdocker <alliesadler@f693mt7fh6.home>
This commit is contained in:
Allie Sadler
GitHub
parent
f18630af26
commit
1f491f5393
|
|
@ -67,132 +67,176 @@ This opens the in-app **Support** page and starts collecting the diagnostics.
|
|||
In some cases, it's useful to run the diagnostics yourself, for instance, if
|
||||
Docker Desktop cannot start.
|
||||
|
||||
1. Locate the `com.docker.diagnose` tool:
|
||||
<ul class="nav nav-tabs">
|
||||
<li class="active"><a data-toggle="tab" data-target="#windows1">Windows</a></li>
|
||||
<li><a data-toggle="tab" data-target="#mac1">Mac</a></li>
|
||||
<li><a data-toggle="tab" data-target="#linux1">Linux</a></li>
|
||||
</ul>
|
||||
<div class="tab-content">
|
||||
<div id="windows1" class="tab-pane fade in active" markdown="1">
|
||||
|
||||
<ul class="nav nav-tabs">
|
||||
<li class="active"><a data-toggle="tab" data-target="#windows1">Windows</a></li>
|
||||
<li><a data-toggle="tab" data-target="#mac1">Mac</a></li>
|
||||
<li><a data-toggle="tab" data-target="#linux1">Linux</a></li>
|
||||
</ul>
|
||||
<div class="tab-content">
|
||||
<div id="windows1" class="tab-pane fade in active" markdown="1">
|
||||
1. Locate the `com.docker.diagnose` tool:
|
||||
|
||||
```console
|
||||
$ C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe
|
||||
```
|
||||
|
||||
</div>
|
||||
<div id="mac1" class="tab-pane fade" markdown="1">
|
||||
|
||||
```console
|
||||
$ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose
|
||||
```
|
||||
|
||||
</div>
|
||||
<div id="linux1" class="tab-pane fade" markdown="1">
|
||||
|
||||
```console
|
||||
$ /opt/docker-desktop/bin/com.docker.diagnose
|
||||
```
|
||||
|
||||
</div>
|
||||
</div>
|
||||
2. Create and upload the diagnostics ID. Run:
|
||||
|
||||
```console
|
||||
$ "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" gather -upload
|
||||
```
|
||||
|
||||
After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example `BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051`.
|
||||
After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example `BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051`.
|
||||
|
||||
To view the contents of the diagnostic file, run:
|
||||
</div>
|
||||
<div id="mac1" class="tab-pane fade" markdown="1">
|
||||
|
||||
<ul class="nav nav-tabs">
|
||||
<li class="active"><a data-toggle="tab" data-target="#windows2">Windows</a></li>
|
||||
<li><a data-toggle="tab" data-target="#mac2">Mac</a></li>
|
||||
<li><a data-toggle="tab" data-target="#linux2">Linux</a></li>
|
||||
</ul>
|
||||
<div class="tab-content">
|
||||
<div id="windows2" class="tab-pane fade in active" markdown="1">
|
||||
<br>
|
||||
1. Unzip the file. In PowerShell, copy and paste the path to the diagnostics file into the following command and then run it. It should be similar to the following example:
|
||||
```powershell
|
||||
$ Expand-Archive -LiteralPath "C:\Users\testUser\AppData\Local\Temp\5DE9978A-3848-429E-8776-950FC869186F\20230607101602.zip" -DestinationPath "C:\Users\testuser\AppData\Local\Temp\5DE9978A-3848-429E-8776-950FC869186F\20230607101602"
|
||||
```
|
||||
2. Open the file in your preferred text editor. Run:
|
||||
```powershell
|
||||
$ code <path-to-file>
|
||||
```
|
||||
|
||||
</div>
|
||||
<div id="mac2" class="tab-pane fade" markdown="1">
|
||||
|
||||
```console
|
||||
$ open /tmp/<your-diagnostics-ID>.zip
|
||||
```
|
||||
|
||||
</div>
|
||||
<div id="linux2" class="tab-pane fade" markdown="1">
|
||||
|
||||
```console
|
||||
$ unzip –l /tmp/<your-diagnostics-ID>.zip
|
||||
```
|
||||
|
||||
</div>
|
||||
</div>
|
||||
3. Use your diagnostics ID to get help:
|
||||
- If you have a paid Docker subscription, open the [Docker Desktop support](https://hub.docker.com/support/desktop/){:target="_blank" rel="noopener" class="_"} form. Fill in the information required and add the ID to the Diagnostics ID field. Make sure you provide the full diagnostics ID, and not just the user ID. Select **Submit** to request Docker Desktop support.
|
||||
- If you don't have a paid Docker subscription, create an issue on GitHub:
|
||||
- [For Linux](https://github.com/docker/desktop-linux/issues){:target="_blank" rel="noopener" class="_"}
|
||||
- [For Mac](https://github.com/docker/for-mac/issues){:target="_blank" rel="noopener" class="_"}
|
||||
- [For Windows](https://github.com/docker/for-win/issues){:target="_blank" rel="noopener" class="_"}
|
||||
|
||||
### Self-diagnose tool
|
||||
|
||||
Docker Desktop contains a self-diagnose tool which can help you identify some common problems.
|
||||
|
||||
1. Locate the `com.docker.diagnose` tool. It is located at:
|
||||
|
||||
<ul class="nav nav-tabs">
|
||||
<li class="active"><a data-toggle="tab" data-target="#windows3">Windows</a></li>
|
||||
<li><a data-toggle="tab" data-target="#mac3">Mac</a></li>
|
||||
<li><a data-toggle="tab" data-target="#linux3">Linux</a></li>
|
||||
</ul>
|
||||
<div class="tab-content">
|
||||
<div id="windows3" class="tab-pane fade in active" markdown="1">
|
||||
|
||||
```console
|
||||
$ C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe
|
||||
```
|
||||
|
||||
</div>
|
||||
<div id="mac3" class="tab-pane fade" markdown="1">
|
||||
1. Locate the `com.docker.diagnose` tool:
|
||||
|
||||
```console
|
||||
$ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose
|
||||
```
|
||||
```
|
||||
|
||||
</div>
|
||||
<div id="linux3" class="tab-pane fade" markdown="1">
|
||||
2. Create and upload the diagnostics ID. Run:
|
||||
|
||||
```console
|
||||
$ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose gather -upload
|
||||
```
|
||||
|
||||
After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example `BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051`.
|
||||
|
||||
</div>
|
||||
<div id="linux1" class="tab-pane fade" markdown="1">
|
||||
|
||||
1. Locate the `com.docker.diagnose` tool:
|
||||
|
||||
```console
|
||||
$ /opt/docker-desktop/bin/com.docker.diagnose
|
||||
```
|
||||
|
||||
</div>
|
||||
</div>
|
||||
2. Create and upload the diagnostics ID. Run:
|
||||
|
||||
```console
|
||||
$ /opt/docker-desktop/bin/com.docker.diagnose gather -upload
|
||||
```
|
||||
|
||||
After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example `BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051`.
|
||||
</div>
|
||||
</div>
|
||||
|
||||
To view the contents of the diagnostic file:
|
||||
|
||||
<ul class="nav nav-tabs">
|
||||
<li class="active"><a data-toggle="tab" data-target="#windows2">Windows</a></li>
|
||||
<li><a data-toggle="tab" data-target="#mac2">Mac</a></li>
|
||||
<li><a data-toggle="tab" data-target="#linux2">Linux</a></li>
|
||||
</ul>
|
||||
<div class="tab-content">
|
||||
<div id="windows2" class="tab-pane fade in active" markdown="1">
|
||||
<br>
|
||||
1. Unzip the file. In PowerShell, copy and paste the path to the diagnostics file into the following command and then run it. It should be similar to the following example:
|
||||
|
||||
```powershell
|
||||
$ Expand-Archive -LiteralPath "C:\Users\testUser\AppData\Local\Temp\5DE9978A-3848-429E-8776-950FC869186F\20230607101602.zip" -DestinationPath "C:\Users\testuser\AppData\Local\Temp\5DE9978A-3848-429E-8776-950FC869186F\20230607101602"
|
||||
```
|
||||
2. Open the file in your preferred text editor. Run:
|
||||
|
||||
```powershell
|
||||
$ code <path-to-file>
|
||||
```
|
||||
|
||||
</div>
|
||||
<div id="mac2" class="tab-pane fade" markdown="1">
|
||||
|
||||
Run:
|
||||
|
||||
```console
|
||||
$ open /tmp/<your-diagnostics-ID>.zip
|
||||
```
|
||||
|
||||
</div>
|
||||
<div id="linux2" class="tab-pane fade" markdown="1">
|
||||
|
||||
Run:
|
||||
|
||||
```console
|
||||
$ unzip –l /tmp/<your-diagnostics-ID>.zip
|
||||
```
|
||||
</div>
|
||||
</div>
|
||||
|
||||
#### Use your diagnostics ID to get help
|
||||
|
||||
If you have a paid Docker subscription, open the [Docker Desktop support](https://hub.docker.com/support/desktop/){:target="_blank" rel="noopener" class="_"} form. Fill in the information required and add the ID to the Diagnostics ID field. Make sure you provide the full diagnostics ID, and not just the user ID. Select **Submit** to request Docker Desktop support.
|
||||
|
||||
If you don't have a paid Docker subscription, create an issue on GitHub:
|
||||
- [For Linux](https://github.com/docker/desktop-linux/issues){:target="_blank" rel="noopener" class="_"}
|
||||
- [For Mac](https://github.com/docker/for-mac/issues){:target="_blank" rel="noopener" class="_"}
|
||||
- [For Windows](https://github.com/docker/for-win/issues){:target="_blank" rel="noopener" class="_"}
|
||||
|
||||
### Self-diagnose tool
|
||||
|
||||
Docker Desktop contains a self-diagnose tool which can help you identify some common problems.
|
||||
|
||||
<ul class="nav nav-tabs">
|
||||
<li class="active"><a data-toggle="tab" data-target="#windows3">Windows</a></li>
|
||||
<li><a data-toggle="tab" data-target="#mac3">Mac</a></li>
|
||||
<li><a data-toggle="tab" data-target="#linux3">Linux</a></li>
|
||||
</ul>
|
||||
<div class="tab-content">
|
||||
<div id="windows3" class="tab-pane fade in active" markdown="1">
|
||||
|
||||
1. Locate the `com.docker.diagnose` tool.
|
||||
|
||||
```console
|
||||
$ C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe
|
||||
```
|
||||
|
||||
2. Run the self-diagnose tool:
|
||||
|
||||
```console
|
||||
$ "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
|
||||
```
|
||||
|
||||
The tool runs a suite of checks and displays **PASS** or **FAIL** next to each check. If there are any failures, it highlights the most relevant at the end of the report.
|
||||
</div>
|
||||
<div id="mac3" class="tab-pane fade" markdown="1">
|
||||
|
||||
You can then create an issue on GitHub:
|
||||
- [For Linux](https://github.com/docker/desktop-linux/issues){:target="_blank" rel="noopener" class="_"}
|
||||
- [For Mac](https://github.com/docker/for-mac/issues){:target="_blank" rel="noopener" class="_"}
|
||||
- [For Windows](https://github.com/docker/for-win/issues){:target="_blank" rel="noopener" class="_"}
|
||||
1. Locate the `com.docker.diagnose` tool.
|
||||
|
||||
```console
|
||||
$ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose
|
||||
```
|
||||
|
||||
2. Run the self-diagnose tool:
|
||||
|
||||
```console
|
||||
$ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
|
||||
```
|
||||
|
||||
</div>
|
||||
<div id="linux3" class="tab-pane fade" markdown="1">
|
||||
|
||||
1. Locate the `com.docker.diagnose` tool.
|
||||
|
||||
```console
|
||||
$ /opt/docker-desktop/bin/com.docker.diagnose
|
||||
```
|
||||
|
||||
2. Run the self-diagnose tool:
|
||||
|
||||
```console
|
||||
$ /opt/docker-desktop/bin/com.docker.diagnose check
|
||||
```
|
||||
</div>
|
||||
</div>
|
||||
|
||||
The tool runs a suite of checks and displays **PASS** or **FAIL** next to each check. If there are any failures, it highlights the most relevant at the end of the report.
|
||||
|
||||
You can then create an issue on GitHub:
|
||||
- [For Linux](https://github.com/docker/desktop-linux/issues){:target="_blank" rel="noopener" class="_"}
|
||||
- [For Mac](https://github.com/docker/for-mac/issues){:target="_blank" rel="noopener" class="_"}
|
||||
- [For Windows](https://github.com/docker/for-win/issues){:target="_blank" rel="noopener" class="_"}
|
||||
|
||||
## Check the logs
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue