Skip to content

redirects: add missing engine redirects after refactor #20600

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dvdksn merged 1 commit into from
Aug 14, 2024
Merged

redirects: add missing engine redirects after refactor #20600

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions content/engine/network/drivers/bridge.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
1 change: 1 addition & 0 deletions content/engine/network/drivers/host.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
1 change: 1 addition & 0 deletions content/engine/network/drivers/ipvlan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
1 change: 1 addition & 0 deletions content/engine/network/drivers/macvlan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
1 change: 1 addition & 0 deletions content/engine/network/drivers/none.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
1 change: 1 addition & 0 deletions content/engine/network/drivers/overlay.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
3 changes: 3 additions & 0 deletions data/redirects.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down