From c150ba2b85be687e7252539338013bbb1278b64c Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Thu, 30 Apr 2020 21:46:11 +0200 Subject: [PATCH] builder: fix broken link This link was broken when generating the documentation (due to a bug in Jekyll not converting wrapped internal links) Signed-off-by: Sebastiaan van Stijn (cherry picked from commit bc58d655c0016a0794616bc42bb50929aa61b3eb) Signed-off-by: Sebastiaan van Stijn --- docs/reference/builder.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/docs/reference/builder.md b/docs/reference/builder.md index b998ea3a71..c7364748cb 100644 --- a/docs/reference/builder.md +++ b/docs/reference/builder.md @@ -941,13 +941,12 @@ the `-p` flag. For example docker run -p 80:80/tcp -p 80:80/udp ... ``` -To set up port redirection on the host system, see [using the -P -flag](run.md#expose-incoming-ports). The `docker network` command supports -creating networks for communication among containers without the need to -expose or publish specific ports, because the containers connected to the -network can communicate with each other over any port. For detailed information, -see the -[overview of this feature](https://docs.docker.com/engine/userguide/networking/)). +To set up port redirection on the host system, see [using the -P flag](run.md#expose-incoming-ports). +The `docker network` command supports creating networks for communication among +containers without the need to expose or publish specific ports, because the +containers connected to the network can communicate with each other over any +port. For detailed information, see the +[overview of this feature](https://docs.docker.com/engine/userguide/networking/). ## ENV