Skip to content
This repository was archived by the owner on Oct 13, 2023. It is now read-only.

Commit 4e553fe

Browse files
committed
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 <github@gone.nl> (cherry picked from commit bc58d655c0016a0794616bc42bb50929aa61b3eb) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: c150ba2b85be687e7252539338013bbb1278b64c Component: cli
1 parent 13f10d4 commit 4e553fe

1 file changed

Lines changed: 6 additions & 7 deletions

File tree

components/cli/docs/reference/builder.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -941,13 +941,12 @@ the `-p` flag. For example
941941
docker run -p 80:80/tcp -p 80:80/udp ...
942942
```
943943
944-
To set up port redirection on the host system, see [using the -P
945-
flag](run.md#expose-incoming-ports). The `docker network` command supports
946-
creating networks for communication among containers without the need to
947-
expose or publish specific ports, because the containers connected to the
948-
network can communicate with each other over any port. For detailed information,
949-
see the
950-
[overview of this feature](https://docs.docker.com/engine/userguide/networking/)).
944+
To set up port redirection on the host system, see [using the -P flag](run.md#expose-incoming-ports).
945+
The `docker network` command supports creating networks for communication among
946+
containers without the need to expose or publish specific ports, because the
947+
containers connected to the network can communicate with each other over any
948+
port. For detailed information, see the
949+
[overview of this feature](https://docs.docker.com/engine/userguide/networking/).
951950
952951
## ENV
953952

0 commit comments

Comments
 (0)