404s

Author: roboparker

os/v1.0/en/configuration/custom-rancheros-iso/index.md

@@ -45,7 +45,7 @@ First, create `gce-qemu.json`:
    {
      "type": "qemu",
      "name": "qemu-googlecompute",
-     "iso_url": "https://github.com/rancherio/os/releases/download/<RancherOS-Version>/rancheros.iso",
+     "iso_url": "https://github.com/rancher/os/releases/download/<RancherOS-Version>/rancheros.iso",
      "iso_checksum": "<rancheros.iso-MD5-hash>",
      "iso_checksum_type": "md5",
      "ssh_wait_timeout": "360s",

os/v1.0/en/configuration/switching-docker-versions/index.md

@@ -88,7 +88,7 @@ FROM scratch
 COPY engine /engine
 ```
 
-Once the image is built a [system service]({{page.osbaseurl}}/system-services/adding-system-services/) configuration file must be created. An [example file](https://github.com/rancher/os-services/blob/master/d/docker-1.12.3.yml) can be found in the rancher/os-services repo. Change the `image` field to point to the Docker engine image you've built.
+Once the image is built a [system service]({{page.osbaseurl}}/system-services/adding-system-services/) configuration file must be created. An [example file](https://github.com/rancher/os-services/blob/master/d/docker-1.12.6.yml) can be found in the rancher/os-services repo. Change the `image` field to point to the Docker engine image you've built.
 
 All of the previously mentioned methods of switching Docker engines are now available. For example, if your service file is located at `https://myservicefile` then the following cloud-config file could be used to use your custom Docker engine.
 

os/v1.0/en/custom-builds/custom-rancheros-iso/index.md

@@ -45,7 +45,7 @@ First, create `gce-qemu.json`:
    {
      "type": "qemu",
      "name": "qemu-googlecompute",
-     "iso_url": "https://github.com/rancherio/os/releases/download/<RancherOS-Version>/rancheros.iso",
+     "iso_url": "https://github.com/rancher/os/releases/download/<RancherOS-Version>/rancheros.iso",
      "iso_checksum": "<rancheros.iso-MD5-hash>",
      "iso_checksum_type": "md5",
      "ssh_wait_timeout": "360s",

os/v1.0/en/running-rancheros/index.md

@@ -26,11 +26,11 @@ RancherOS runs on virtualization platforms, cloud providers and bare metal serve
 
 [DigitalOcean]({{page.osbaseurl}}/running-rancheros/cloud/do)
 
-[Azure]({{page.osbaseurl}}/running-rancheros/cloud/azure)
+Azure
 
 #### Bare Metal & Virtual Servers
 
-[iPXE]({{page.osbaseurl}}/running-rancheros/server/ipxe)
+iPXE
 
 [PXE]({{page.osbaseurl}}/running-rancheros/server/pxe)
 

os/v1.0/en/system-services/environment/index.md

@@ -7,7 +7,7 @@ title: Environment
 # Environment
 ---
 
-The [environment key](https://docs.docker.com/compose/yml/#environment) can be used to customize system services. When a value is not assigned, RancherOS looks up the value from the `rancher.environment` key.
+The [environment key](https://docs.docker.com/compose/compose-file/#environment) can be used to customize system services. When a value is not assigned, RancherOS looks up the value from the `rancher.environment` key.
 
 In the example below, `ETCD_DISCOVERY` will be set to `https://discovery.etcd.io/d1cd18f5ee1c1e2223aed6a1734719f7` for the `etcd` service.
 

os/v1.1/en/configuration/custom-rancheros-iso/index.md

@@ -45,7 +45,7 @@ First, create `gce-qemu.json`:
    {
      "type": "qemu",
      "name": "qemu-googlecompute",
-     "iso_url": "https://github.com/rancherio/os/releases/download/<RancherOS-Version>/rancheros.iso",
+     "iso_url": "https://github.com/rancher/os/releases/download/<RancherOS-Version>/rancheros.iso",
      "iso_checksum": "<rancheros.iso-MD5-hash>",
      "iso_checksum_type": "md5",
      "ssh_wait_timeout": "360s",

os/v1.1/en/configuration/index.md

@@ -39,7 +39,7 @@ In our example above, we have our `#cloud-config` line to indicate it's a cloud-
 ### Manually Changing Configuration
 
 To update RancherOS configuration after booting, the `ros config set <key> <value>` command can be used.
-For more complicated settings, like the [sysctl settings]({{page.osbaseurl}}/sysctl/), you can also create a small YAML file and then run `sudo ros config merge -i <your yaml file>`.
+For more complicated settings, like the sysctl settings, you can also create a small YAML file and then run `sudo ros config merge -i <your yaml file>`.
 
 #### Getting Values
 

os/v1.1/en/configuration/switching-docker-versions/index.md

@@ -88,7 +88,7 @@ FROM scratch
 COPY engine /engine
 ```
 
-Once the image is built a [system service]({{page.osbaseurl}}/system-services/adding-system-services/) configuration file must be created. An [example file](https://github.com/rancher/os-services/blob/master/d/docker-1.12.3.yml) can be found in the rancher/os-services repo. Change the `image` field to point to the Docker engine image you've built.
+Once the image is built a [system service]({{page.osbaseurl}}/system-services/adding-system-services/) configuration file must be created. An [example file](https://github.com/rancher/os-services/blob/master/d/docker-1.12.6.yml) can be found in the rancher/os-services repo. Change the `image` field to point to the Docker engine image you've built.
 
 All of the previously mentioned methods of switching Docker engines are now available. For example, if your service file is located at `https://myservicefile` then the following cloud-config file could be used to use your custom Docker engine.
 

os/v1.1/en/custom-builds/custom-rancheros-iso/index.md

@@ -45,7 +45,7 @@ First, create `gce-qemu.json`:
    {
      "type": "qemu",
      "name": "qemu-googlecompute",
-     "iso_url": "https://github.com/rancherio/os/releases/download/<RancherOS-Version>/rancheros.iso",
+     "iso_url": "https://github.com/rancher/os/releases/download/<RancherOS-Version>/rancheros.iso",
      "iso_checksum": "<rancheros.iso-MD5-hash>",
      "iso_checksum_type": "md5",
      "ssh_wait_timeout": "360s",

os/v1.1/en/running-rancheros/cloud/gce/index.md

@@ -6,7 +6,7 @@ title: Running RancherOS on GCE
 # Running RancherOS on Google Compute Engine (GCE)
 ----
 
-> **Note:** Due to the maximum transmission unit (MTU) of [1460 bytes on GCE](https://cloud.google.com/compute/docs/troubleshooting#packetfragmentation), you will need to configure your [network interfaces]({{page.osbaseurl}}/os/networking/interfaces/) and both the [Docker and System Docker]({{page.osbaseurl}}/os/configuration/docker/) to use a MTU of 1460 bytes or you will encounter weird networking related errors.
+> **Note:** Due to the maximum transmission unit (MTU) of [1460 bytes on GCE](https://cloud.google.com/compute/docs/troubleshooting#packetfragmentation), you will need to configure your network interfaces and both the Docker and System Docker to use a MTU of 1460 bytes or you will encounter weird networking related errors.
 
 ### Adding the RancherOS Image into GCE
 

os/v1.1/en/running-rancheros/index.md

@@ -30,7 +30,7 @@ RancherOS runs on virtualization platforms, cloud providers and bare metal serve
 
 #### Bare Metal & Virtual Servers
 
-[iPXE]({{page.osbaseurl}}/running-rancheros/server/ipxe)
+iPXE
 
 [PXE]({{page.osbaseurl}}/running-rancheros/server/pxe)
 

os/v1.1/en/running-rancheros/server/pxe/index.md

@@ -62,7 +62,7 @@ Valid cloud-init datasources for RancherOS.
 | gce |  |  |
 | packet | DefaultAddress |  |
 | url | url |  |
-| vmware |  | set `guestinfo` cloud-init or interface data as per [VMware ESXi]({{page.osbaseurl}}/cloud/vmware-esxi) |
+| vmware |  | set `guestinfo` cloud-init or interface data as per VMware ESXi |
 | * | This will add ["configdrive", "vmware", "ec2", "digitalocean", "packet", "gce"] into the list of datasources to try |  |
 
 ### Cloud-Config

os/v1.1/en/security/index.md

@@ -16,7 +16,7 @@ title: RancherOS security
 </td>
 <td width="30%" style="border: none;">
 <h4>Reporting process</h4>
-<p style="padding: 8px">Please submit possible security issues by emailing <a href="[email protected]">[email protected]</a></p>
+<p style="padding: 8px">Please submit possible security issues by emailing <a href="mailto:[email protected]">[email protected]</a></p>
 </td>
 <td width="30%" style="border: none;">
 <h4>Announcments</h4>

os/v1.1/en/system-services/environment/index.md

@@ -7,7 +7,7 @@ title: Environment
 # Environment
 ---
 
-The [environment key](https://docs.docker.com/compose/yml/#environment) can be used to customize system services. When a value is not assigned, RancherOS looks up the value from the `rancher.environment` key.
+The [environment key](https://docs.docker.com/compose/compose-file/#environment) can be used to customize system services. When a value is not assigned, RancherOS looks up the value from the `rancher.environment` key.
 
 In the example below, `ETCD_DISCOVERY` will be set to `https://discovery.etcd.io/d1cd18f5ee1c1e2223aed6a1734719f7` for the `etcd` service.
 

os/v1.2/en/configuration/custom-rancheros-iso/index.md

@@ -45,7 +45,7 @@ First, create `gce-qemu.json`:
    {
      "type": "qemu",
      "name": "qemu-googlecompute",
-     "iso_url": "https://github.com/rancherio/os/releases/download/<RancherOS-Version>/rancheros.iso",
+     "iso_url": "https://github.com/rancher/os/releases/download/<RancherOS-Version>/rancheros.iso",
      "iso_checksum": "<rancheros.iso-MD5-hash>",
      "iso_checksum_type": "md5",
      "ssh_wait_timeout": "360s",

os/v1.2/en/configuration/switching-docker-versions/index.md

@@ -88,7 +88,7 @@ FROM scratch
 COPY engine /engine
 ```
 
-Once the image is built a [system service]({{page.osbaseurl}}/system-services/adding-system-services/) configuration file must be created. An [example file](https://github.com/rancher/os-services/blob/master/d/docker-1.12.3.yml) can be found in the rancher/os-services repo. Change the `image` field to point to the Docker engine image you've built.
+Once the image is built a [system service]({{page.osbaseurl}}/system-services/adding-system-services/) configuration file must be created. An [example file](https://github.com/rancher/os-services/blob/master/d/docker-1.12.6.yml) can be found in the rancher/os-services repo. Change the `image` field to point to the Docker engine image you've built.
 
 All of the previously mentioned methods of switching Docker engines are now available. For example, if your service file is located at `https://myservicefile` then the following cloud-config file could be used to use your custom Docker engine.
 

os/v1.2/en/custom-builds/custom-rancheros-iso/index.md

@@ -45,7 +45,7 @@ First, create `gce-qemu.json`:
    {
      "type": "qemu",
      "name": "qemu-googlecompute",
-     "iso_url": "https://github.com/rancherio/os/releases/download/<RancherOS-Version>/rancheros.iso",
+     "iso_url": "https://github.com/rancher/os/releases/download/<RancherOS-Version>/rancheros.iso",
      "iso_checksum": "<rancheros.iso-MD5-hash>",
      "iso_checksum_type": "md5",
      "ssh_wait_timeout": "360s",

os/v1.2/en/running-rancheros/index.md

@@ -30,7 +30,7 @@ RancherOS runs on virtualization platforms, cloud providers and bare metal serve
 
 #### Bare Metal & Virtual Servers
 
-[iPXE]({{page.osbaseurl}}/running-rancheros/server/ipxe)
+iPXE
 
 [PXE]({{page.osbaseurl}}/running-rancheros/server/pxe)
 

os/v1.2/en/running-rancheros/server/pxe/index.md

@@ -62,7 +62,7 @@ Valid cloud-init datasources for RancherOS.
 | gce |  |  |
 | packet | DefaultAddress |  |
 | url | url |  |
-| vmware |  | set `guestinfo` cloud-init or interface data as per [VMware ESXi]({{page.osbaseurl}}/cloud/vmware-esxi) |
+| vmware |  | set `guestinfo` cloud-init or interface data as per VMware ESXi |
 | * | This will add ["configdrive", "vmware", "ec2", "digitalocean", "packet", "gce"] into the list of datasources to try |  |
 
 ### Cloud-Config

os/v1.2/en/system-services/environment/index.md

@@ -7,7 +7,7 @@ title: Environment
 ## Environment
 ---
 
-The [environment key](https://docs.docker.com/compose/yml/#environment) can be used to customize system services. When a value is not assigned, RancherOS looks up the value from the `rancher.environment` key.
+The [environment key](https://docs.docker.com/compose/compose-file/#environment) can be used to customize system services. When a value is not assigned, RancherOS looks up the value from the `rancher.environment` key.
 
 In the example below, `ETCD_DISCOVERY` will be set to `https://discovery.etcd.io/d1cd18f5ee1c1e2223aed6a1734719f7` for the `etcd` service.
 

os/v1.x/en/configuration/switching-docker-versions/index.md

@@ -90,7 +90,7 @@ FROM scratch
 COPY engine /engine
 ```
 
-Once the image is built a [system service]({{page.osbaseurl}}/system-services/adding-system-services/) configuration file must be created. An [example file](https://github.com/rancher/os-services/blob/master/d/docker-1.12.3.yml) can be found in the rancher/os-services repo. Change the `image` field to point to the Docker engine image you've built.
+Once the image is built a [system service]({{page.osbaseurl}}/system-services/adding-system-services/) configuration file must be created. An [example file](https://github.com/rancher/os-services/blob/master/d/docker-1.12.6.yml) can be found in the rancher/os-services repo. Change the `image` field to point to the Docker engine image you've built.
 
 All of the previously mentioned methods of switching Docker engines are now available. For example, if your service file is located at `https://myservicefile` then the following cloud-config file could be used to use your custom Docker engine.
 

os/v1.x/en/custom-builds/custom-rancheros-iso/index.md

@@ -47,7 +47,7 @@ First, create `gce-qemu.json`:
    {
      "type": "qemu",
      "name": "qemu-googlecompute",
-     "iso_url": "https://github.com/rancherio/os/releases/download/<RancherOS-Version>/rancheros.iso",
+     "iso_url": "https://github.com/rancher/os/releases/download/<RancherOS-Version>/rancheros.iso",
      "iso_checksum": "<rancheros.iso-MD5-hash>",
      "iso_checksum_type": "md5",
      "ssh_wait_timeout": "360s",

os/v1.x/en/running-rancheros/cloud/gce/index.md

@@ -6,7 +6,7 @@ title: Running RancherOS on GCE
 ## Running RancherOS on Google Compute Engine (GCE)
 ----
 
-> **Note:** Due to the maximum transmission unit (MTU) of [1460 bytes on GCE](https://cloud.google.com/compute/docs/troubleshooting#packetfragmentation), you will need to configure your [network interfaces]({{site.baseurl}}/os/networking/interfaces/) and both the [Docker and System Docker]({{site.baseurl}}/os/configuration/docker/) to use a MTU of 1460 bytes or you will encounter weird networking related errors.
+> **Note:** Due to the maximum transmission unit (MTU) of [1460 bytes on GCE](https://cloud.google.com/compute/docs/troubleshooting#packetfragmentation), you will need to configure your network interfaces and both the [Docker and System Docker]({{site.baseurl}}/os/configuration/docker/) to use a MTU of 1460 bytes or you will encounter weird networking related errors.
 
 ### Adding the RancherOS Image into GCE
 

os/v1.x/en/running-rancheros/index.md

@@ -30,7 +30,7 @@ RancherOS runs on virtualization platforms, cloud providers and bare metal serve
 
 #### Bare Metal & Virtual Servers
 
-[iPXE]({{page.osbaseurl}}/running-rancheros/server/ipxe)
+iPXE
 
 [PXE]({{page.osbaseurl}}/running-rancheros/server/pxe)
 

os/v1.x/en/system-services/environment/index.md

@@ -7,7 +7,7 @@ title: Environment
 ## Environment
 ---
 
-The [environment key](https://docs.docker.com/compose/yml/#environment) can be used to customize system services. When a value is not assigned, RancherOS looks up the value from the `rancher.environment` key.
+The [environment key](https://docs.docker.com/compose/compose-file/#environment) can be used to customize system services. When a value is not assigned, RancherOS looks up the value from the `rancher.environment` key.
 
 In the example below, `ETCD_DISCOVERY` will be set to `https://discovery.etcd.io/d1cd18f5ee1c1e2223aed6a1734719f7` for the `etcd` service.
 

rancher/v1.3/en/api/v1/common/index.md

@@ -16,7 +16,7 @@ In the API, the resource fields that are the most common and read only on a reso
 
 Field | Type |  Notes
 ---|---|---|---|---|---
-accountId | [account]({{site.baseurl}}/rancher/{{page.version}}/{{page.lang}}/api/api-resources/account/) | The unique identifier for the associated account
+accountId | account | The unique identifier for the associated account
 created[TS] | date | The date/time when the resource was initially created.
 id | string | The unique identifier for the resource.
 kind | string | A more specific sub-type for the resource.

rancher/v1.3/en/api/v1/index.md

@@ -26,7 +26,7 @@ In the documentation, we have used the UI term in descriptions and have provided
 
 ### Authentication
 
-API requests must include authentication information if [Access Control]({{site.baseurl}}/rancher/{{page.version}}/{{page.lang}}/configuration/access-control/) is enabled.  Authentication is done with HTTP basic authentication using [API Keys]({{site.baseurl}}/rancher/{{page.version}}/{{page.lang}}/api/api-resources/apikey).  API keys can either belong to a single (UI) Environment / (API) [Project]({{site.baseurl}}/rancher/{{page.version}}/{{page.lang}}/api/api-resources/project/) with access to just that Environment, or to a [Account]({{site.baseurl}}/rancher/{{page.version}}/{{page.lang}}/api/api-resources/account) with access to all Environments the account belongs to, and the ability to create new ones.  There is also a separate JSON Web Token interface primarily for the UI.
+API requests must include authentication information if [Access Control]({{site.baseurl}}/rancher/{{page.version}}/{{page.lang}}/configuration/access-control/) is enabled.  Authentication is done with HTTP basic authentication using API Keys.  API keys can either belong to a single (UI) Environment / (API) Project with access to just that Environment, or to a Account with access to all Environments the account belongs to, and the ability to create new ones.  There is also a separate JSON Web Token interface primarily for the UI.
 
 > **Note:** In our examples, we've assumed that the `${RANCHER_ACCESS_KEY}:${RANCHER_SECRET_KEY}` are Account API Keys, but if you were to use an Environment API Key, you could omit the `projects/${PROJECT_ID}` from the URL.
 

rancher/v1.3/en/windows/index.md

@@ -42,7 +42,7 @@ As part of adding a host into Rancher, the Rancher agent is installed and regist
 
 ### Networking in Windows
 
-By default, we support NAT and transparent [networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-networking).
+By default, we support NAT and transparent [networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture).
 
 Currently, the default **Windows** environment template supports a transparent network named `transparent`, which is created by running `docker network create -d transparent transparent`.
 

rancher/v1.4/en/windows/index.md

@@ -40,7 +40,7 @@ As part of adding a host into Rancher, the Rancher agent is installed and regist
 
 ### Networking in Windows
 
-By default, we support NAT and transparent [networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-networking).
+By default, we support NAT and transparent [networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture).
 
 Currently, the default **Windows** environment template supports a transparent network named `transparent`, which is created by running `docker network create -d transparent transparent`.
 

rancher/v1.5/en/windows/index.md

@@ -40,7 +40,7 @@ As part of adding a host into Rancher, the Rancher agent is installed and regist
 
 ### Networking in Windows
 
-By default, we support NAT and transparent [networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-networking).
+By default, we support NAT and transparent [networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture).
 
 Currently, the default **Windows** environment template supports a transparent network named `transparent`, which is created by running `docker network create -d transparent transparent`.
 

rancher/v1.6/en/windows/index.md

@@ -164,7 +164,7 @@ As part of adding a host into Rancher, the Rancher agent is installed and regist
 
 ### Networking in Windows
 
-By default, we support NAT and transparent [networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-networking).
+By default, we support NAT and transparent [networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture).
 
 Currently, the default **Windows** environment template supports a transparent network named `transparent`, which is created by running `docker network create -d transparent transparent`.
 

rancher/v1.6/zh/windows/index.md

@@ -37,7 +37,7 @@ lang: zh
 ```
 
 ### Windows 中的网络
-我们默认支持NAT和[透明网络](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-networking).
+我们默认支持NAT和[透明网络](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture).
 
 目前，默认的 **Windows** 环境模版支持名为transparent的透明网络
 这个透明网络是在运行 `docker network create -d transparent transparent`时创建的。