Merge pull request #20600 from dvdksn/engine-restruct-followups

redirects: add missing engine redirects after refactor
This commit is contained in:
David Karlsson 2024-08-14 09:38:53 +02:00 committed by GitHub
commit 17b898be94
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
7 changed files with 9 additions and 0 deletions

View File

@ -8,6 +8,7 @@ aliases:
- /engine/userguide/networking/default_network/custom-docker0/
- /engine/userguide/networking/work-with-networks/
- /network/bridge/
- /network/drivers/bridge/
---
In terms of networking, a bridge network is a Link Layer device

View File

@ -4,6 +4,7 @@ description: All about exposing containers on the Docker host's network
keywords: network, host, standalone, host mode networking
aliases:
- /network/host/
- /network/drivers/host/
---
If you use the `host` network mode for a container, that container's network

View File

@ -5,6 +5,7 @@ description: All about using IPvlan to make your containers appear like physical
keywords: network, ipvlan, l2, l3, standalone
aliases:
- /network/ipvlan/
- /network/drivers/ipvlan/
---
The IPvlan driver gives users total control over both IPv4 and IPv6 addressing.

View File

@ -7,6 +7,7 @@ aliases:
- /config/containers/macvlan/
- /engine/userguide/networking/get-started-macvlan/
- /network/macvlan/
- /network/drivers/macvlan/
---
Some applications, especially legacy applications or applications which monitor

View File

@ -4,6 +4,7 @@ description: How to isolate the networking stack of a container using the none d
keywords: network, none, standalone
aliases:
- /network/none/
- /network/drivers/none/
---
If you want to completely isolate the networking stack of a container, you can

View File

@ -6,6 +6,7 @@ aliases:
- /config/containers/overlay/
- /engine/userguide/networking/overlay-security-model/
- /network/overlay/
- /network/drivers/overlay/
---
The `overlay` network driver creates a distributed network among multiple

View File

@ -107,6 +107,9 @@
# redirect for old location of dockerd reference
"/reference/cli/dockerd/":
- /engine/reference/commandline/dockerd/
# redirect updated location of the "running containers" page
"/engine/reference/run":
- /engine/containers/run/
"/engine/security/#docker-daemon-attack-surface":
# Details about the "Docker Daemon attack surface". This redirect is currently