Kaynağa Gözat

Merge pull request #42076 from thaJeztah/update_docs_links

Update documentation links
Sebastiaan van Stijn 4 yıl önce
ebeveyn
işleme
2ae2ddf51d

+ 1 - 1
client/client.go

@@ -2,7 +2,7 @@
 Package client is a Go client for the Docker Engine API.
 Package client is a Go client for the Docker Engine API.
 
 
 For more information about the Engine API, see the documentation:
 For more information about the Engine API, see the documentation:
-https://docs.docker.com/engine/reference/api/
+https://docs.docker.com/engine/api/
 
 
 Usage
 Usage
 
 

+ 3 - 3
contrib/dockerd-rootless-setuptool.sh

@@ -4,7 +4,7 @@
 #
 #
 # Typical usage: dockerd-rootless-setuptool.sh install --force
 # Typical usage: dockerd-rootless-setuptool.sh install --force
 #
 #
-# Documentation: https://docs.docker.com/engine/security/rootless/
+# Documentation: https://docs.docker.com/go/rootless/
 set -eu
 set -eu
 
 
 # utility functions
 # utility functions
@@ -290,7 +290,7 @@ install_systemd() {
 		cat <<- EOT > "${unit_file}"
 		cat <<- EOT > "${unit_file}"
 			[Unit]
 			[Unit]
 			Description=Docker Application Container Engine (Rootless)
 			Description=Docker Application Container Engine (Rootless)
-			Documentation=https://docs.docker.com/engine/security/rootless/
+			Documentation=https://docs.docker.com/go/rootless/
 
 
 			[Service]
 			[Service]
 			Environment=PATH=$BIN:/sbin:/usr/sbin:$PATH
 			Environment=PATH=$BIN:/sbin:/usr/sbin:$PATH
@@ -400,7 +400,7 @@ usage() {
 	echo
 	echo
 	echo "A setup tool for Rootless Docker (${DOCKERD_ROOTLESS_SH})."
 	echo "A setup tool for Rootless Docker (${DOCKERD_ROOTLESS_SH})."
 	echo
 	echo
-	echo "Documentation: https://docs.docker.com/engine/security/rootless/"
+	echo "Documentation: https://docs.docker.com/go/rootless/"
 	echo
 	echo
 	echo "Options:"
 	echo "Options:"
 	echo "  -f, --force                Ignore rootful Docker (/var/run/docker.sock)"
 	echo "  -f, --force                Ignore rootful Docker (/var/run/docker.sock)"

+ 1 - 1
contrib/dockerd-rootless.sh

@@ -15,7 +15,7 @@
 # * DOCKERD_ROOTLESS_ROOTLESSKIT_SLIRP4NETNS_SANDBOX=(auto|true|false): whether to protect slirp4netns with a dedicated mount namespace. Defaults to "auto".
 # * DOCKERD_ROOTLESS_ROOTLESSKIT_SLIRP4NETNS_SANDBOX=(auto|true|false): whether to protect slirp4netns with a dedicated mount namespace. Defaults to "auto".
 # * DOCKERD_ROOTLESS_ROOTLESSKIT_SLIRP4NETNS_SECCOMP=(auto|true|false): whether to protect slirp4netns with seccomp. Defaults to "auto".
 # * DOCKERD_ROOTLESS_ROOTLESSKIT_SLIRP4NETNS_SECCOMP=(auto|true|false): whether to protect slirp4netns with seccomp. Defaults to "auto".
 #
 #
-# See the documentation for the further information: https://docs.docker.com/engine/security/rootless/
+# See the documentation for the further information: https://docs.docker.com/go/rootless/
 
 
 set -e -x
 set -e -x
 case "$1" in
 case "$1" in

+ 1 - 1
daemon/info.go

@@ -209,7 +209,7 @@ func (daemon *Daemon) fillAPIInfo(v *types.Info) {
 	const warn string = `
 	const warn string = `
          Access to the remote API is equivalent to root access on the host. Refer
          Access to the remote API is equivalent to root access on the host. Refer
          to the 'Docker daemon attack surface' section in the documentation for
          to the 'Docker daemon attack surface' section in the documentation for
-         more information: https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface`
+         more information: https://docs.docker.com/go/attack-surface/`
 
 
 	cfg := daemon.configStore
 	cfg := daemon.configStore
 	for _, host := range cfg.Hosts {
 	for _, host := range cfg.Hosts {

+ 1 - 1
docs/api/v1.25.yaml

@@ -105,7 +105,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.26.yaml

@@ -106,7 +106,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.27.yaml

@@ -107,7 +107,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.28.yaml

@@ -108,7 +108,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.29.yaml

@@ -109,7 +109,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.30.yaml

@@ -110,7 +110,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.31.yaml

@@ -111,7 +111,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.32.yaml

@@ -112,7 +112,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.33.yaml

@@ -113,7 +113,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.34.yaml

@@ -116,7 +116,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.35.yaml

@@ -104,7 +104,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.36.yaml

@@ -104,7 +104,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.37.yaml

@@ -104,7 +104,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/api/v1.38.yaml

@@ -104,7 +104,7 @@ tags:
   - name: "Network"
   - name: "Network"
     x-displayName: "Networks"
     x-displayName: "Networks"
     description: |
     description: |
-      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/engine/userguide/networking/) for more information.
+      Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
   - name: "Volume"
   - name: "Volume"
     x-displayName: "Volumes"
     x-displayName: "Volumes"
     description: |
     description: |

+ 1 - 1
docs/rootless.md

@@ -1,3 +1,3 @@
-Moved to https://docs.docker.com/engine/security/rootless/
+Moved to https://docs.docker.com/go/rootless/
 
 
 <!-- do not remove this file, as there is a lot of links to https://github.com/moby/moby/blob/master/docs/rootless.md -->
 <!-- do not remove this file, as there is a lot of links to https://github.com/moby/moby/blob/master/docs/rootless.md -->

+ 1 - 1
pkg/authorization/authz.go

@@ -21,7 +21,7 @@ const maxBodySize = 1048576 // 1MB
 // Authenticate Request:
 // Authenticate Request:
 // Call authZ plugins with current REST request and AuthN response
 // Call authZ plugins with current REST request and AuthN response
 // Request contains full HTTP packet sent to the docker daemon
 // Request contains full HTTP packet sent to the docker daemon
-// https://docs.docker.com/engine/reference/api/
+// https://docs.docker.com/engine/api/
 //
 //
 // Authenticate Response:
 // Authenticate Response:
 // Call authZ plugins with full info about current REST request, REST response and AuthN response
 // Call authZ plugins with full info about current REST request, REST response and AuthN response