mirror of https://github.com/docker/docs.git
Update faqs.md
This commit is contained in:
paigehargrave
GitHub
parent
397c7da3a4
commit
f36feeaadc
|
|
@ -4,26 +4,26 @@ keywords: windows faqs
|
|||
title: Frequently asked questions (FAQ)
|
||||
---
|
||||
|
||||
**Looking for popular FAQs on Docker for Windows?** Check out the
|
||||
**Looking for popular FAQs on Docker Desktop for Windows?** Check out the
|
||||
[Docker Success Center](http://success.docker.com/){: target="_blank" class="_"}
|
||||
for knowledge base articles, FAQs, technical support for subscription levels, and more.
|
||||
|
||||
### Questions about Stable and Edge channels
|
||||
|
||||
#### How do I get the Stable or Edge version of Docker for Windows?
|
||||
#### How do I get the Stable or Edge version of Docker Desktop for Windows?
|
||||
|
||||
Use the download links for the channels given in the topic
|
||||
[Download Docker for Windows](install#download-docker-for-windows).
|
||||
[Download Docker Desktop for Windows](install#download-docker-for-windows).
|
||||
|
||||
This topic also has more information about the two channels.
|
||||
|
||||
#### What is the difference between the Stable and Edge versions of Docker for Windows?
|
||||
#### What is the difference between the Stable and Edge versions of Docker Desktop for Windows?
|
||||
|
||||
Two different download channels are available for Docker for Windows:
|
||||
Two different download channels are available for Docker Desktop for Windows:
|
||||
|
||||
* The **Stable channel** provides a general availability release-ready installer
|
||||
for a fully baked and tested, more reliable app. The Stable version of Docker
|
||||
for Windows comes with the latest released version of Docker Engine. The
|
||||
Desktop for Windows comes with the latest released version of Docker Engine. The
|
||||
release schedule is synced with Docker Engine releases and hotfixes. On the
|
||||
Stable channel, you can select whether to send usage statistics and other data.
|
||||
|
||||
|
|
@ -35,7 +35,7 @@ Two different download channels are available for Docker for Windows:
|
|||
Stable, often one or more per month. Usage statistics and crash reports are
|
||||
sent by default. You do not have the option to disable this on the Edge channel.
|
||||
|
||||
#### Can I switch back and forth between Stable and Edge versions of Docker for Windows?
|
||||
#### Can I switch back and forth between Stable and Edge versions of Docker Desktop for Windows?
|
||||
|
||||
Yes, you can switch between versions to try out the Edge release to see what's
|
||||
new, then go back to Stable for other work. However, **you can have only one app
|
||||
|
|
@ -43,7 +43,7 @@ installed at a time**. Switching back and forth between Stable and Edge apps can
|
|||
destabilize your development environment, particularly in cases where you switch
|
||||
from a newer (Edge) channel to older (Stable).
|
||||
|
||||
For example, containers created with a newer Edge version of Docker for Windows
|
||||
For example, containers created with a newer Edge version of Docker Desktop for Windows
|
||||
may not work after you switch back to Stable because they may have been created
|
||||
leveraging Edge features that aren't in Stable yet. Just keep this in mind as
|
||||
you create and work with Edge containers, perhaps in the spirit of a playground
|
||||
|
|
@ -88,12 +88,12 @@ You can find the list of frequent issues in
|
|||
[Logs and Troubleshooting](troubleshoot).
|
||||
|
||||
If you do not find a solution in Troubleshooting, browse issues on
|
||||
[Docker for Windows issues on GitHub](https://github.com/docker/for-win/issues){: target="_blank" class="_"}
|
||||
[Docker Desktop for Windows issues on GitHub](https://github.com/docker/for-win/issues){: target="_blank" class="_"}
|
||||
or create a new one. You can also create new issues based on diagnostics. To
|
||||
learn more about running diagnostics and about Docker for Windows GitHub issues,
|
||||
learn more about running diagnostics and about Docker Desktop for Windows GitHub issues,
|
||||
see [Diagnose and Feedback](/docker-for-windows#diagnose--feedback).
|
||||
|
||||
[Docker for Windows forum](https://forums.docker.com/c/docker-for-windows){: target="_blank" class="_"}
|
||||
[Docker Desktop for Windows forum](https://forums.docker.com/c/docker-for-windows){: target="_blank" class="_"}
|
||||
provides discussion threads as well, and you can create discussion topics there,
|
||||
but we recommend using the GitHub issues over the forums for better tracking and
|
||||
response.
|
||||
|
|
@ -120,13 +120,13 @@ ID is mentioned in a GitHub issue). Docker Inc. will only use the data in the
|
|||
diagnostics bundle to investigate specific user issues, but may derive high
|
||||
level (non personal) metrics such as the rate of issues from it.
|
||||
|
||||
### Can I use Docker for Windows with new swarm mode?
|
||||
### Can I use Docker Desktop for Windows with new swarm mode?
|
||||
|
||||
Yes! You can use Docker for Windows to test single-node features of
|
||||
Yes! You can use Docker Desktop for Windows to test single-node features of
|
||||
[swarm mode](/engine/swarm/) introduced with Docker Engine 1.12, including
|
||||
initializing a swarm with a single node, creating services, and scaling
|
||||
services. Docker “Moby” on Hyper-V serves as the single swarm node. You can also
|
||||
use Docker Machine, which comes with Docker for Windows, to create and
|
||||
use Docker Machine, which comes with Docker Desktop for Windows, to create and
|
||||
experiment with a multi-node swarm. Check out the tutorial at
|
||||
[Get started with swarm mode](/engine/swarm/swarm-tutorial/).
|
||||
|
||||
|
|
@ -134,21 +134,21 @@ experiment with a multi-node swarm. Check out the tutorial at
|
|||
|
||||
You might need to provide the location of the Engine API for Docker clients and development tools.
|
||||
|
||||
On Docker for Windows, clients can connect to the Docker Engine through a
|
||||
On Docker Desktop for Windows, clients can connect to the Docker Engine through a
|
||||
**named pipe**: `npipe:////./pipe/docker_engine`, or **TCP socket** at this URL:
|
||||
`tcp://localhost:2375`.
|
||||
|
||||
This sets `DOCKER_HOST` and `DOCKER_CERT_PATH` environment variables to the
|
||||
given values (for the named pipe or TCP socket, whichever you use).
|
||||
|
||||
See also [Docker Engine API](/engine/api) and the Docker for Windows forums
|
||||
See also [Docker Engine API](/engine/api) and the Docker Desktop for Windows forums
|
||||
topic
|
||||
[How to find the remote API](https://forums.docker.com/t/how-to-find-the-remote-api/20988){: target="_blank" class="_"}.
|
||||
|
||||
### Volumes
|
||||
#### Can I change permissions on shared volumes for container-specific deployment requirements?
|
||||
|
||||
No, at this point, Docker for Windows does not enable you to control (`chmod`)
|
||||
No, at this point, Docker Desktop for Windows does not enable you to control (`chmod`)
|
||||
the Unix-style permissions on [shared volumes](/docker-for-windows#shared-drives) for
|
||||
deployed containers, but rather sets permissions to a default value of
|
||||
[0777](http://permissions-calculator.org/decode/0777/){: target="_blank" class="_"}
|
||||
|
|
@ -167,7 +167,7 @@ in [Troubleshooting](troubleshoot).
|
|||
|
||||
#### Are symlinks supported?
|
||||
|
||||
Docker for Windows supports symbolic links (symlinks) created within containers.
|
||||
Docker Desktop for Windows supports symbolic links (symlinks) created within containers.
|
||||
Symlinks resolve within and across containers.
|
||||
Symlinks created outside of Docker do not work.
|
||||
|
||||
|
|
@ -176,7 +176,7 @@ To learn more about the reasons for this limitation, see the following discussio
|
|||
* GitHub issue:
|
||||
[Symlinks don't work as expected](https://github.com/docker/for-win/issues/109#issuecomment-251307391){: target="_blank" class="_"}
|
||||
|
||||
* Docker for Windows forums topic:
|
||||
* Docker Desktop for Windows forums topic:
|
||||
[Symlinks on shared volumes not supported](https://forums.docker.com/t/symlinks-on-shared-volumes-not-supported/9288){: target="_blank" class="_"}
|
||||
|
||||
|
||||
|
|
@ -184,15 +184,15 @@ To learn more about the reasons for this limitation, see the following discussio
|
|||
|
||||
#### How do I add custom CA certificates?
|
||||
|
||||
Starting with Docker for Windows 1.12.1, 2016-09-16 (Stable) and Beta 26
|
||||
Starting with Docker Desktop for Windows 1.12.1, 2016-09-16 (Stable) and Beta 26
|
||||
(2016-09-14 1.12.1-beta26), all trusted Certificate Authorities (CA) (root or
|
||||
intermediate) are supported. Docker recognizes certs stored under Trust Root
|
||||
Certification Authorities or Intermediate Certification Authorities.
|
||||
|
||||
Docker for Windows creates a certificate bundle of all user-trusted CAs based on
|
||||
Docker Desktop for Windows creates a certificate bundle of all user-trusted CAs based on
|
||||
the Windows certificate store, and appends it to Moby trusted certificates. So
|
||||
if an enterprise SSL certificate is trusted by the user on the host, it is
|
||||
trusted by Docker for Windows.
|
||||
trusted by Docker Desktop for Windows.
|
||||
|
||||
To learn more about how to install a CA root certificate for the registry, see
|
||||
[Verify repository client with certificates](/engine/security/certificates)
|
||||
|
|
@ -200,20 +200,20 @@ in the Docker Engine topics.
|
|||
|
||||
#### How do I add client certificates?
|
||||
|
||||
Starting with Docker for Windows 17.06.0-ce, you do not need to push your
|
||||
Starting with Docker Desktop for Windows 17.06.0-ce, you do not need to push your
|
||||
certificates with `git` commands anymore. You can put your client certificates
|
||||
in `~/.docker/certs.d/<MyRegistry>:<Port>/client.cert` and
|
||||
`~/.docker/certs.d/<MyRegistry>:<Port>/client.key`.
|
||||
|
||||
When the Docker for Windows application starts up, it copies the
|
||||
When the Docker Desktop for Windows application starts up, it copies the
|
||||
`~/.docker/certs.d` folder on your Windows system to the `/etc/docker/certs.d`
|
||||
directory on Moby (the Docker for Windows virtual machine running on Hyper-V).
|
||||
directory on Moby (the Docker fDesktop or Windows virtual machine running on Hyper-V).
|
||||
|
||||
You need to restart Docker for Windows after making any changes to the keychain
|
||||
You need to restart Docker Desktop for Windows after making any changes to the keychain
|
||||
or to the `~/.docker/certs.d` directory in order for the changes to take effect.
|
||||
|
||||
The registry cannot be listed as an _insecure registry_ (see
|
||||
[Docker Daemon](/docker-for-windows#daemon)). Docker for Windows ignores
|
||||
[Docker Daemon](/docker-for-windows#daemon)). Docker Desktop for Windows ignores
|
||||
certificates listed under insecure registries, and does not send client
|
||||
certificates. Commands like `docker run` that attempt to pull from the registry
|
||||
produce error messages on the command line, as well as on the registry.
|
||||
|
|
@ -222,7 +222,7 @@ To learn more about how to set the client TLS certificate for verification, see
|
|||
[Verify repository client with certificates](/engine/security/certificates)
|
||||
in the Docker Engine topics.
|
||||
|
||||
### Why does Docker for Windows sometimes lose network connectivity, causing `push` or `pull` commands to fail?
|
||||
### Why does Docker Desktop for Windows sometimes lose network connectivity, causing `push` or `pull` commands to fail?
|
||||
|
||||
Networking is not yet fully stable across network changes and system sleep
|
||||
cycles. Exit and start Docker to restore connectivity.
|
||||
|
|
@ -235,15 +235,15 @@ Hyper-V is enabled on Windows.
|
|||
### Can I share local drives and filesystem with my Docker Machine VMs?
|
||||
|
||||
No, you cannot share local drives with Docker Machine nodes when using Docker
|
||||
for Windows with Hyper-V. Shared drives can be made available to containers, but
|
||||
Docker for Windows does not support mounts for nodes you created with
|
||||
Desktop for Windows with Hyper-V. Shared drives can be made available to containers, but
|
||||
Docker Desktop for Windows does not support mounts for nodes you created with
|
||||
`docker-machine`.
|
||||
|
||||
For more about sharing local drives with containers using Docker for Windows,
|
||||
For more about sharing local drives with containers using Docker Desktop for Windows,
|
||||
see [Shared drives](/docker-for-windows#shared-drives) in the Getting
|
||||
Started topic.
|
||||
|
||||
To learn more about using Docker for Windows and Docker Machine, see
|
||||
To learn more about using Docker Desktop for Windows and Docker Machine, see
|
||||
[What to know before you install](install#what-to-know-before-you-install) in the
|
||||
Getting Started topic. For more about Docker Machine itself, see
|
||||
[What is Docker Machine?](/machine/overview#what-is-docker-machine), and the
|
||||
|
|
@ -251,7 +251,7 @@ Getting Started topic. For more about Docker Machine itself, see
|
|||
|
||||
### Windows Requirements
|
||||
|
||||
#### How do I run Windows containers on Docker on Windows Server 2016?
|
||||
#### How do I run Windows containers on Docker Desktop on Windows Server 2016?
|
||||
|
||||
See [About Windows containers and Windows Server 2016](/install/windows/docker-ee/#about-docker-ee-containers-and-windows-server).
|
||||
|
||||
|
|
@ -260,26 +260,26 @@ A full tutorial is available in [docker/labs](https://github.com/docker/labs){:
|
|||
|
||||
#### Why is Windows 10 Home not supported?
|
||||
|
||||
Docker for Windows requires the Hyper-V Windows feature which is not
|
||||
Docker Desktop for Windows requires the Hyper-V Windows feature which is not
|
||||
available on Home-edition.
|
||||
|
||||
#### Why is Windows 10 required?
|
||||
|
||||
Docker for Windows uses Windows Hyper-V. While older Windows versions have
|
||||
Docker Desktop for Windows uses Windows Hyper-V. While older Windows versions have
|
||||
Hyper-V, their Hyper-V implementations lack features critical for Docker for
|
||||
Windows to work.
|
||||
|
||||
#### Why does Docker for Windows fail to start when firewalls or anti-virus software is installed?
|
||||
#### Why does Docker Desktop for Windows fail to start when firewalls or anti-virus software is installed?
|
||||
|
||||
Some firewalls and anti-virus software might be incompatible with Hyper-V and
|
||||
some Windows 10 builds (possibly, the Anniversary Update), which impacts Docker
|
||||
for Windows. See details and workarounds in
|
||||
Desktop for Windows. See details and workarounds in
|
||||
[Docker fails to start when firewall or anti-virus software is installed](troubleshoot#docker-fails-to-start-when-firewall-or-anti-virus-software-is-installed)
|
||||
in [Troubleshooting](troubleshoot).
|
||||
|
||||
### How do I uninstall Docker Toolbox?
|
||||
|
||||
You might decide that you do not need Toolbox now that you have Docker for
|
||||
You might decide that you do not need Toolbox now that you have Docker Desktop for
|
||||
Windows, and want to uninstall it. For details on how to perform a clean
|
||||
uninstall of Toolbox on Windows, see
|
||||
[How to uninstall Toolbox](/toolbox/toolbox_install_windows#how-to-uninstall-toolbox) in the Toolbox Windows topics.
|
||||
|
|
|
|||
Loading…
Reference in New Issue