mirror of https://github.com/docker/docs.git
Copyedit phase 4 (#6329)
This commit is contained in:
Gwendolynne Barr
GitHub
parent
52e8b27401
commit
fede3151d5
|
|
@ -24,7 +24,7 @@ Docker for Windows is the best way to get started with Docker _on Windows_.
|
|||
|
||||
1. Open a terminal window (Command Prompt or PowerShell, _but not_ PowerShell ISE).
|
||||
|
||||
2. Run `docker --version ` to ensure that you have a supported version of Docker:
|
||||
2. Run `docker --version` to ensure that you have a supported version of Docker:
|
||||
|
||||
```shell
|
||||
> docker --version
|
||||
|
|
@ -32,7 +32,7 @@ Docker for Windows is the best way to get started with Docker _on Windows_.
|
|||
Docker version 18.03.0-ce, build 0520e24
|
||||
```
|
||||
|
||||
2. Pull the [hello-world image](https://hub.docker.com/r/library/hello-world/) from Docker Hub and run a container:
|
||||
3. Pull the [hello-world image](https://hub.docker.com/r/library/hello-world/) from Docker Hub and run a container:
|
||||
|
||||
```shell
|
||||
> docker run hello-world
|
||||
|
|
@ -56,19 +56,19 @@ Docker for Windows is the best way to get started with Docker _on Windows_.
|
|||
...
|
||||
```
|
||||
|
||||
3. List the `hello-world` _image_ that was downloaded from Docker Hub:
|
||||
4. List the `hello-world` _image_ that was downloaded from Docker Hub:
|
||||
|
||||
```shell
|
||||
> docker image ls
|
||||
```
|
||||
|
||||
4. List the `hello-world` _container_ (which exited after displaying "Hello from Docker!"):
|
||||
5. List the `hello-world` _container_ (which exited after displaying "Hello from Docker!"):
|
||||
|
||||
```shell
|
||||
> docker container ls --all
|
||||
```
|
||||
|
||||
5. Explore Docker help pages by running these three help commands:
|
||||
6. Explore Docker help pages by running these three help commands:
|
||||
|
||||
```shell
|
||||
> docker --help
|
||||
|
|
@ -115,14 +115,16 @@ running more complex applications, such as an OS and a webserver.
|
|||
```
|
||||
Notice that the hostname is assigned as the container ID (and is also used in the prompt).
|
||||
|
||||
3. Exit and stop the container with the `exit` command:
|
||||
3. Exit the shell with the `exit` command (which also stops the container):
|
||||
|
||||
```shell
|
||||
root@8aea0acb7423:/# exit
|
||||
>
|
||||
```
|
||||
|
||||
4. List _all_ containers (none of which are running) and notice the randomly assigned names:
|
||||
4. List containers with the `--all` option (becasue no containers are running).
|
||||
|
||||
The `hello-world` container (randomly named, `relaxed_sammet`) stopped after displaying its message. The `ubuntu` container (randomly named, `laughing_kowalevski`) stopped when you exited the container.
|
||||
|
||||
```shell
|
||||
> docker container ls --all
|
||||
|
|
@ -132,8 +134,6 @@ running more complex applications, such as an OS and a webserver.
|
|||
45f77eb48e78 hello-world "/hello" 3 minutes ago Exited (0) 3 minutes ago relaxed_sammet
|
||||
```
|
||||
|
||||
The hello-world container stopped after displaying its message. The Ubuntu container stopped when you ran `exit`.
|
||||
|
||||
5. Pull and run a Dockerized [nginx](https://hub.docker.com/_/nginx/) web server that we name, `webserver`:
|
||||
|
||||
```shell
|
||||
|
|
|
|||
|
|
@ -227,7 +227,7 @@ script](https://github.com/moby/moby/issues/24388).
|
|||
|
||||
### Virtualization
|
||||
|
||||
#### Hyper-V
|
||||
#### Hyper-V must be enabled
|
||||
|
||||
Docker for Windows requires a Hyper-V as well as the Hyper-V Module for Windows
|
||||
Powershell to be installed and enabled. The Docker for Windows installer enables
|
||||
|
|
@ -235,8 +235,7 @@ it for you.
|
|||
|
||||
See [these instructions](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install) to install Hyper-V manually. A reboot is *required*. If you install Hyper-V without the reboot, Docker for Windows does not work correctly. On some systems, Virtualization needs to be enabled in the BIOS. The steps to do so are Vendor specific, but typically the BIOS option is called `Virtualization Technology (VTx)` or similar.
|
||||
|
||||
Once Hyper-V is enabled, it shows up as such on "Turn Windows features on or
|
||||
off".
|
||||
Once Hyper-V is enabled, it shows up as such on "Turn Windows features on or off".
|
||||
|
||||
{:width="600px"}
|
||||
|
||||
|
|
@ -256,19 +255,13 @@ Machine driver example](/machine/drivers/hyper-v.md#example).
|
|||
|
||||
#### Virtualization must be enabled
|
||||
|
||||
In addition to [Hyper-V](#hyper-v), virtualization must be enabled.
|
||||
In addition to [Hyper-V](#hyper-v), virtualization must be enabled. Check the Performance tab on the
|
||||
Task Manager:
|
||||
|
||||
{:width="700px"}
|
||||
|
||||
If, at some point, if you manually uninstall Hyper-V or disable virtualization,
|
||||
Docker for Windows cannot start.
|
||||
|
||||
Verify that virtualization is enabled by checking the Performance tab on the
|
||||
Task Manager.
|
||||
|
||||
{:width="600px"}
|
||||
|
||||
Also, see the user-reported issue [Unable to run Docker for Windows on Windows
|
||||
10 Enterprise](https://github.com/docker/for-win/issues/74).
|
||||
|
||||
Docker for Windows cannot start. See: [Unable to run Docker for Windows on Windows 10 Enterprise](https://github.com/docker/for-win/issues/74).
|
||||
|
||||
### Networking and WiFi problems upon Docker for Windows install
|
||||
|
||||
|
|
@ -282,23 +275,19 @@ is not the case. (See also, Docker for Windows issue on GitHub:
|
|||
|
||||
Here are some steps to take if you encounter similar problems:
|
||||
|
||||
1. Ensure virtualization is enabled, as described in the [Virtualization troubleshooting topic](#virtualization-must-be-enabled).
|
||||
1. Ensure **virtualization** is enabled, as described above in [Virtualization must be enabled](#virtualization-must-be-enabled).
|
||||
|
||||
2. Ensure the Hyper-V is installed and enabled, as described in the previous [Hyper-V troubleshooting topic](#hyper-v).
|
||||
2. Ensure **Hyper-V** is installed and enabled, as described above in [Hyper-V must be enabled](#hyper-v-must-be-enabled).
|
||||
|
||||
3. Check your network switches to see if `DockerNAT` is enabled.
|
||||
3. Ensure **DockerNAT** is enabled by checking the **Virtual Switch Manager** on the Actions tab of the **Hyper-V Manager**.
|
||||
|
||||
a. Open the **Hyper-V Manager** (search for `hyperv`).
|
||||
b. Select your Hyper-V manager on the left-side of the dialog.
|
||||
c. Select the Virtual Switch Manager on the right-side **Actions** panel.
|
||||
|
||||
{:width="600px"}
|
||||
|
||||
|
||||
4. Set up an external network switch. If you plan at any point to use
|
||||
[Docker Machine](/machine/overview.md) to set up multiple local VMs, you
|
||||
need this anyway, as described in the topic on the [Hyper-V driver for
|
||||
[Docker Machine](/machine/drivers/hyper-v.md#example). You can replace
|
||||
`DockerNAT` with this switch.
|
||||
need this anyway, as described in the topic on the
|
||||
[Hyper-V driver for Docker Machine](/machine/drivers/hyper-v.md#example).
|
||||
You can replace `DockerNAT` with this switch.
|
||||
|
||||
5. If previous steps fail to solve the problems, follow steps on the
|
||||
[Cleanup README](https://github.com/Microsoft/Virtualization-Documentation/blob/master/windows-server-container-tools/CleanupContainerHostNetworking/README.md).
|
||||
|
|
|
|||
Loading…
Reference in New Issue