docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update networking.md

This commit is contained in:
paigehargrave 2019-01-11 13:21:55 -05:00 committed by GitHub
parent 62edcf746d
commit 39b11d4185
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docker-for-windows/networking.md
View File

@ -1,19 +1,19 @@
---
description: Networking
keywords: windows, networking
title: Networking features in Docker for Windows
title: Networking features in Docker Desktop for Windows
---
{% assign Arch = 'Windows' %}
Docker for {{Arch}} provides several networking features to make it easier to
Docker Desktop for {{Arch}} provides several networking features to make it easier to
use.
## Features
### VPN Passthrough
Docker for {{Arch}}'s networking can work when attached to a VPN. To do this,
Docker for {{Arch}} intercepts traffic from the containers and injects it into
Docker Desktop for {{Arch}}'s networking can work when attached to a VPN. To do this,
Docker Desktop for {{Arch}} intercepts traffic from the containers and injects it into
{{Arch}} as if it originated from the Docker application.
### Port Mapping
@ -24,7 +24,7 @@ When you run a container with the `-p` argument, for example:
$ docker run -p 80:80 -d nginx
```
Docker for {{Arch}} makes whatever is running on port 80 in the container (in
Docker Desktop for {{Arch}} makes whatever is running on port 80 in the container (in
this case, `nginx`) available on port 80 of `localhost`. In this example, the
host and container ports are the same. What if you need to specify a different
host port? If, for example, you already have something running on port 80 of
@ -43,18 +43,18 @@ See [Proxies](index#Proxies).
## Known limitations, use cases, and workarounds
Following is a summary of current limitations on the Docker for {{Arch}}
Following is a summary of current limitations on the Docker Desktop for {{Arch}}
networking stack, along with some ideas for workarounds.
### There is no docker0 bridge on {{Arch}}
Because of the way networking is implemented in Docker for {{Arch}}, you cannot
Because of the way networking is implemented in Docker Desktop for {{Arch}}, you cannot
see a `docker0` interface on the host. This interface is actually within the
virtual machine.
### I cannot ping my containers
Docker for Windows can't route traffic to Linux containers. However, you can
Docker Desktop for Windows can't route traffic to Linux containers. However, you can
ping the Windows containers.
### Per-container IP addressing is not possible
@ -72,7 +72,7 @@ The host has a changing IP address (or none if you have no network access). From
18.03 onwards our recommendation is to connect to the special DNS name
`host.docker.internal`, which resolves to the internal IP address used by the
host.
This is for development purpose and will not work in a production environment outside of Docker for Windows.
This is for development purpose and will not work in a production environment outside of Docker Desktop for Windows.
The gateway is also reachable as `gateway.docker.internal`.