mirror of https://github.com/docker/docs.git
Update troubleshoot.md
This commit is contained in:
parent
014f7899f3
commit
0abd45205f
|
@ -7,12 +7,12 @@ title: Logs and troubleshooting
|
|||
---
|
||||
|
||||
Here is information about how to diagnose and troubleshoot problems, send logs
|
||||
and communicate with the Docker for Mac team, use our forums and Knowledge Hub,
|
||||
and communicate with the Docker Desktop for Mac team, use our forums and Knowledge Hub,
|
||||
browse and log issues on GitHub, and find workarounds for known problems.
|
||||
|
||||
## Docker Knowledge Hub
|
||||
|
||||
**Looking for help with Docker for Mac?** Check out the [Docker Knowledge
|
||||
**Looking for help with Docker Desktop for Mac?** Check out the [Docker Knowledge
|
||||
Hub](http://success.docker.com/) for knowledge base articles, FAQs, and
|
||||
technical support for various subscription levels.
|
||||
|
||||
|
@ -20,8 +20,8 @@ technical support for various subscription levels.
|
|||
|
||||
### In-app diagnostics
|
||||
If you encounter problems for which you do not find solutions in this
|
||||
documentation, on [Docker for Mac issues on
|
||||
GitHub](https://github.com/docker/for-mac/issues), or the [Docker for Mac
|
||||
documentation, on [Docker Desktop for Mac issues on
|
||||
GitHub](https://github.com/docker/for-mac/issues), or the [Docker Desktop for Mac
|
||||
forum](https://forums.docker.com/c/docker-for-mac), we can help you troubleshoot
|
||||
the log data.
|
||||
|
||||
|
@ -39,7 +39,7 @@ Desktop](https://docs.docker.com/docker-for-mac/faqs/#how-is-personal-data-handl
|
|||
{:width="600px"}
|
||||
|
||||
If you click **Report an issue**, this opens [Docker for Mac issues on
|
||||
If you click **Report an issue**, this opens [Docker Desktop for Mac issues on
|
||||
GitHub](https://github.com/docker/for-mac/issues/) in your web browser in a
|
||||
"create new issue" template, to be completed before submission. Do not forget to
|
||||
copy/paste your diagnostic ID.
|
||||
|
@ -49,9 +49,9 @@ copy/paste your diagnostic ID.
|
|||
### Diagnosing from the terminal
|
||||
|
||||
On occasions it is useful to run the diagnostics yourself, for instance if
|
||||
Docker for Mac cannot start.
|
||||
Docker Desktop for Mac cannot start.
|
||||
|
||||
First locate the `com.docker.diagnose` tool. If you installed Docker for Mac in
|
||||
First locate the `com.docker.diagnose` tool. If you installed Docker Desktop for Mac in
|
||||
the Applications directory, then it is
|
||||
`/Applications/Docker.app/Contents/MacOS/com.docker.diagnose`.
|
||||
|
||||
|
@ -89,7 +89,7 @@ documentation](v17.12/docker-for-mac/troubleshoot/#logs).
|
|||
|
||||
#### In a terminal
|
||||
|
||||
To watch the live flow of Docker for Mac logs at the command line, run this from
|
||||
To watch the live flow of Docker Desktop for Mac logs at the command line, run this from
|
||||
your favorite shell.
|
||||
|
||||
```bash
|
||||
|
@ -127,7 +127,7 @@ ways, and create reports.
|
|||
|
||||
### Make sure certificates are set up correctly
|
||||
|
||||
Docker for Mac ignores certificates listed under insecure registries, and does
|
||||
Docker Desktop for Mac 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:
|
||||
|
||||
|
@ -145,9 +145,9 @@ As well as on the registry. For example:
|
|||
For more about using client and server side certificates, see [Adding TLS
|
||||
certificates](index.md#adding-tls-certificates) in the Getting Started topic.
|
||||
|
||||
### Docker for Mac does not start if Mac user account and home folder are renamed after installing the app
|
||||
### Docker Desktop for Mac does not start if Mac user account and home folder are renamed after installing the app
|
||||
|
||||
See [Do I need to reinstall Docker for Mac if I change the name of my macOS
|
||||
See [Do I need to reinstall Docker Desktop for Mac if I change the name of my macOS
|
||||
account?](faqs.md#do-i-need-to-reinstall-docker-for-mac-if-i-change-the-name-of-my-macos-account)
|
||||
in the FAQs.
|
||||
|
||||
|
@ -165,10 +165,10 @@ Dockerfile and volume.
|
|||
|
||||
### Incompatible CPU detected
|
||||
|
||||
Docker for Mac requires a processor (CPU) that supports virtualization and, more
|
||||
Docker Desktop for Mac 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 for Mac is only compatible with Macs that have a CPU that supports the
|
||||
Docker Desktop for Mac is only compatible with Macs 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:
|
||||
|
||||
|
@ -189,15 +189,15 @@ 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 for Mac system requirements in [What to
|
||||
in the Apple documentation, and Docker Desktop for Mac system requirements in [What to
|
||||
know before you install](install.md#what-to-know-before-you-install).
|
||||
|
||||
|
||||
### Workarounds for common problems
|
||||
|
||||
* If Docker for Mac fails to install or start properly:
|
||||
* If Docker Desktop for Mac fails to install or start properly:
|
||||
|
||||
* Make sure you quit Docker for Mac before installing a new version of the
|
||||
* Make sure you quit Docker Desktop for Mac before installing a new version of the
|
||||
application ({: .inline} → **Quit
|
||||
Docker**). Otherwise, you get an "application in use" error when you try to
|
||||
copy the new app from the `.dmg` to `/Applications`.
|
||||
|
@ -216,8 +216,8 @@ know before you install](install.md#what-to-know-before-you-install).
|
|||
* If you use bash, use the following command: `unset ${!DOCKER_*}`
|
||||
|
||||
* For other shells, unset each environment variable individually as described
|
||||
in [Setting up to run Docker for
|
||||
Mac](docker-toolbox.md#setting-up-to-run-docker-for-mac) in [Docker for Mac
|
||||
in [Setting up to run Docker Desktop for
|
||||
Mac](docker-toolbox.md#setting-up-to-run-docker-for-mac) in [Docker Desktop for Mac
|
||||
vs. Docker Toolbox](docker-toolbox.md).
|
||||
|
||||
|
||||
|
@ -226,13 +226,13 @@ know before you install](install.md#what-to-know-before-you-install).
|
|||
incoming connections so that the VM can get an IP address.
|
||||
|
||||
|
||||
* For the `hello-world-nginx` example, Docker for Mac must be running to get to
|
||||
* For the `hello-world-nginx` example, Docker Desktop for Mac 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 for Mac Engine (not Engine from Toolbox).
|
||||
is connected to the Docker Desktop for Mac Engine (not Engine from Toolbox).
|
||||
Otherwise, you might start the webserver container but get a "web page not
|
||||
available" error when you go to `localhost`. For more on distinguishing
|
||||
between the two environments, see [Docker for Mac vs. Docker
|
||||
between the two environments, see [Docker Desktop for Mac vs. Docker
|
||||
Toolbox](docker-toolbox.md).
|
||||
|
||||
<p></p>
|
||||
|
@ -249,12 +249,12 @@ know before you install](install.md#what-to-know-before-you-install).
|
|||
|
||||
## Known issues
|
||||
|
||||
* IPv6 is not (yet) supported on Docker for Mac.
|
||||
* IPv6 is not (yet) supported on Docker Desktop for Mac.
|
||||
|
||||
A workaround is provided that auto-filters out the IPv6 addresses in DNS
|
||||
server lists and enables successful network access. For example,
|
||||
`2001:4860:4860::8888` would become `8.8.8.8`. To learn more, see these
|
||||
issues on GitHub and Docker for Mac forums:
|
||||
issues on GitHub and Docker Desktop for Mac forums:
|
||||
|
||||
* [Network timeout when top two DNS servers in /etc/resolv.conf are IPv6
|
||||
addresses](https://github.com/docker/for-mac/issues/9)
|
||||
|
@ -264,7 +264,7 @@ know before you install](install.md#what-to-know-before-you-install).
|
|||
|
||||
<p></p>
|
||||
|
||||
* You might encounter errors when using `docker-compose up` with Docker for Mac
|
||||
* You might encounter errors when using `docker-compose up` with Docker Desktop for Mac
|
||||
(`ValueError: Extra Data`). We've identified this is likely related to data
|
||||
and/or events being passed all at once rather than one by one, so sometimes
|
||||
the data comes back as 2+ objects concatenated and causes an error.
|
||||
|
@ -280,13 +280,13 @@ know before you install](install.md#what-to-know-before-you-install).
|
|||
|
||||
<p></p>
|
||||
|
||||
* Docker for Mac uses the `HyperKit` hypervisor
|
||||
* Docker Desktop for Mac 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
|
||||
(HAXM)](https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager/),
|
||||
the current workaround is not to run them at the same time. You can pause
|
||||
`HyperKit` by quitting Docker for Mac temporarily while you work with HAXM.
|
||||
`HyperKit` by quitting Docker Desktop for Mac temporarily while you work with HAXM.
|
||||
This allows you to continue work with the other tools and prevent `HyperKit`
|
||||
from interfering.
|
||||
|
||||
|
@ -340,7 +340,7 @@ know before you install](install.md#what-to-know-before-you-install).
|
|||
and roadmap](osxfs.md#performance-issues-solutions-and-roadmap).
|
||||
|
||||
* If your system does not have access to an NTP server, then after a hibernate
|
||||
the time seen by Docker for Mac may be considerably out of sync with the host.
|
||||
the time seen by Docker Desktop for Mac may be considerably out of sync with the host.
|
||||
Furthermore, the time may slowly drift out of sync during use. To manually
|
||||
reset the time after hibernation, run:
|
||||
|
||||
|
|
Loading…
Reference in New Issue