From 9eb371e320335ca77f3286692b6a45078ff4065d Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Wed, 14 Aug 2024 09:12:29 +0200
Subject: [PATCH] redirects: add missing engine redirects after refactor

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
---
 content/engine/network/drivers/bridge.md  | 1 +
 content/engine/network/drivers/host.md    | 1 +
 content/engine/network/drivers/ipvlan.md  | 1 +
 content/engine/network/drivers/macvlan.md | 1 +
 content/engine/network/drivers/none.md    | 1 +
 content/engine/network/drivers/overlay.md | 1 +
 data/redirects.yml                        | 3 +++
 7 files changed, 9 insertions(+)

diff --git a/content/engine/network/drivers/bridge.md b/content/engine/network/drivers/bridge.md
index 2e9020a144..8bdac7aaeb 100644
--- a/content/engine/network/drivers/bridge.md
+++ b/content/engine/network/drivers/bridge.md
@@ -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
diff --git a/content/engine/network/drivers/host.md b/content/engine/network/drivers/host.md
index 0d5da6952d..2541f0aa05 100644
--- a/content/engine/network/drivers/host.md
+++ b/content/engine/network/drivers/host.md
@@ -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
diff --git a/content/engine/network/drivers/ipvlan.md b/content/engine/network/drivers/ipvlan.md
index e61f02e2ac..673c5b7347 100644
--- a/content/engine/network/drivers/ipvlan.md
+++ b/content/engine/network/drivers/ipvlan.md
@@ -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.
diff --git a/content/engine/network/drivers/macvlan.md b/content/engine/network/drivers/macvlan.md
index 9da1fce46d..7d0023e69f 100644
--- a/content/engine/network/drivers/macvlan.md
+++ b/content/engine/network/drivers/macvlan.md
@@ -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
diff --git a/content/engine/network/drivers/none.md b/content/engine/network/drivers/none.md
index 68c0ed60a1..65d058cecb 100644
--- a/content/engine/network/drivers/none.md
+++ b/content/engine/network/drivers/none.md
@@ -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
diff --git a/content/engine/network/drivers/overlay.md b/content/engine/network/drivers/overlay.md
index d91ba51f81..f65c1a9a82 100644
--- a/content/engine/network/drivers/overlay.md
+++ b/content/engine/network/drivers/overlay.md
@@ -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
diff --git a/data/redirects.yml b/data/redirects.yml
index 52e0243e0a..d38bf5773a 100644
--- a/data/redirects.yml
+++ b/data/redirects.yml
@@ -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