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

fix broken links

This commit is contained in:
Allie Sadler 2022-06-30 15:57:25 +01:00
parent 5683f6b747
commit cd79acca5d
4 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
desktop/faqs/general.md
View File

@ -96,8 +96,7 @@ For details, see [Docker Engine API](../../engine/api/index.md).
Mac, Linux, and Windows have a changing IP address (or none if you have no network access). On both Mac and Windows, we recommend that you connect to the special DNS name `host.docker.internal`, which resolves to the internal IP address used by the host. This is for development purposes and does not work in a production environment outside of Docker Desktop.
For more information and examples, see how to connect from a container to a service on the host
[on Mac](../mac/networking.md#i-want-to-connect-from-a-container-to-a-service-on-the-host) and [on Windows](../windows/networking.md#i-want-to-connect-from-a-container-to-a-service-on-the-host) or [on Linux](../linux/networking.md#i-want-to-connect-from-a-container-to-a-service-on-the-host).
For more information and examples, see [how to connect from a container to a service on the host](../networking.md#i-want-to-connect-from-a-container-to-a-service-on-the-host).
### Can I pass through a USB device to a container?

2
desktop/previous-versions/2.x-windows.md
View File

@ -381,7 +381,7 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
### Known issues
- DockerNAT has been removed from Docker Desktop 2.2.0.0 as using an IP address to communicate from the host to a container is not a supported feature. To communicate from a container to the host, you must use the special DNS name `host.docker.internal`. We also recommend using ports to communicate from the host to a container. For more information, see [Networking](../windows/networking.md#use-cases-and-workarounds).
- DockerNAT has been removed from Docker Desktop 2.2.0.0 as using an IP address to communicate from the host to a container is not a supported feature. To communicate from a container to the host, you must use the special DNS name `host.docker.internal`. We also recommend using ports to communicate from the host to a container. For more information, see [Networking](../networking.md#use-cases-and-workarounds-for-all-platforms).
However, if your current setup relies on IP addresses for communication, you can use a temporary workaround to reinstate DockerNAT. To do this, open
`C:\Program Files\Docker\Docker\resources\MobyLinux.ps1` and add `$SwitchName = "DockerNAT"` between line 175 and 176. Note that the temporary workaround to reinstate DockerNAT may be removed from future releases.

2
desktop/windows/index.md
View File

@ -304,7 +304,7 @@ For more information on Windows containers, refer to the following documentation
[forked here to use containers](https://github.com/friism/MusicStore), is a good example of a multi-container application.
- To understand how to connect to Windows containers from the local host, see
[I want to connect to a container from Windows](networking.md#i-want-to-connect-to-a-container-from-windows)
[I want to connect to a container from Windows](../etworking.md#i-want-to-connect-to-a-container-from-the-host)
> Settings dialog changes with Windows containers
>

2
desktop/windows/networking.md
View File

@ -125,5 +125,5 @@ container to random ports on the host.
$ docker run -d -P --name webserver nginx
```
See the [run command](../../engine/reference/commandline/run.md) for more details on
See the [run command](../engine/reference/commandline/run.md) for more details on
publish options used with `docker run`.