Merge pull request #1092 from sanscontext/fix-cloud-links

more link fixes
This commit is contained in:
LRubin 2017-01-11 15:13:44 -08:00 committed by GitHub
commit 32f0406945
11 changed files with 14 additions and 14 deletions

View File

@ -503,7 +503,7 @@ Logging configuration for the service.
The `driver` name specifies a logging driver for the service's The `driver` name specifies a logging driver for the service's
containers, as with the ``--log-driver`` option for docker run containers, as with the ``--log-driver`` option for docker run
([documented here](/engine/reference/logging/overview.md)). ([documented here](/engine/admin/logging/overview.md)).
The default value is json-file. The default value is json-file.
@ -787,7 +787,7 @@ use the specified driver.
> Note: No path expansion will be done if you have also specified a > Note: No path expansion will be done if you have also specified a
> `volume_driver`. > `volume_driver`.
See [Docker Volumes](/engine/userguide/dockervolumes.md) and See [Docker Volumes](/engine/tutorials/dockervolumes.md) and
[Volume Plugins](/engine/extend/plugins_volume.md) for more [Volume Plugins](/engine/extend/plugins_volume.md) for more
### volumes_from ### volumes_from

View File

@ -14,7 +14,7 @@ To install Compose, do the following:
* <a href="/engine/installation/windows/" target="_blank">Windows installation</a> * <a href="/engine/installation/windows/" target="_blank">Windows installation</a>
* <a href="/engine/installation/ubuntulinux/" target="_blank">Ubuntu installation</a> * <a href="/engine/installation/linux/ubuntulinux/" target="_blank">Ubuntu installation</a>
* <a href="/engine/installation/" target="_blank">other system installations</a> * <a href="/engine/installation/" target="_blank">other system installations</a>

View File

@ -21,7 +21,7 @@ format](compose-file.md#versioning) you are using:
- subject to the [limitations](swarm.md#limitations) described below, - subject to the [limitations](swarm.md#limitations) described below,
- as long as the Swarm cluster is configured to use the [overlay driver](/engine/userguide/networking/dockernetworks/#an-overlay-network), - as long as the Swarm cluster is configured to use the [overlay driver](/engine/userguide/networking/#an-overlay-network-with-docker-engine-swarm-mode),
or a custom driver which supports multi-host networking. or a custom driver which supports multi-host networking.
Read [Get started with multi-host networking](/engine/userguide/networking/get-started-overlay/) to see how to Read [Get started with multi-host networking](/engine/userguide/networking/get-started-overlay/) to see how to

View File

@ -506,7 +506,7 @@ In that topic, see also:
* [Linux configuration file](/engine/reference/commandline/dockerd/#/linux-configuration-file) * [Linux configuration file](/engine/reference/commandline/dockerd/#/linux-configuration-file)
* [Windows configuration file](/reference/commandline/dockerd/#/windows-configuration-file) * [Windows configuration file](/engine/reference/commandline/dockerd/#/windows-configuration-file)
Note that updating these settings requires a reconfiguration and reboot of the Linux VM. Note that updating these settings requires a reconfiguration and reboot of the Linux VM.

View File

@ -57,7 +57,7 @@ the repositories you can access and their status, view your "Dashboard" page on
[Docker Hub](https://hub.docker.com). [Docker Hub](https://hub.docker.com).
You can find more information on working with Docker images in the You can find more information on working with Docker images in the
[Docker userguide](/engine/userguide/dockerimages/). [Docker userguide](/engine/tutorials/dockerimages/).
### Use Official Repositories ### Use Official Repositories

View File

@ -95,7 +95,7 @@ You can name your local images either when you build it, using
by re-tagging an existing local image `docker tag <existing-image> <hub-user>/<repo-name>[:<tag>]`, by re-tagging an existing local image `docker tag <existing-image> <hub-user>/<repo-name>[:<tag>]`,
or by using `docker commit <exiting-container> <hub-user>/<repo-name>[:<tag>]` to commit or by using `docker commit <exiting-container> <hub-user>/<repo-name>[:<tag>]` to commit
changes. changes.
See [Working with Docker images](/engine/userguide/dockerimages) for a detailed description. See [Working with Docker images](/engine/tutorials/dockerimages/) for a detailed description.
Now you can push this repository to the registry designated by its name or tag. Now you can push this repository to the registry designated by its name or tag.

View File

@ -155,7 +155,7 @@ Linux:
- Any distribution running version 3.10+ of the Linux kernel - Any distribution running version 3.10+ of the Linux kernel
- Specific instructions are available for most Linux distributions, including - Specific instructions are available for most Linux distributions, including
[RHEL](installation/linux/rhel.md), [Ubuntu](installation/linux/ubuntulinux.md), [RHEL](installation/linux/rhel.md), [Ubuntu](installation/linux/ubuntulinux.md),
[SuSE](installation/linux/suse.md), and many others. [SuSE](installation/linux/SUSE.md), and many others.
Microsoft Windows: Microsoft Windows:
- Windows Server 2016 - Windows Server 2016

View File

@ -373,8 +373,8 @@ If you run into repeated problems with thin pool, you can use the
`dm.min_free_space` option to tune the Engine behavior. This value ensures that `dm.min_free_space` option to tune the Engine behavior. This value ensures that
operations fail with a warning when the free space is at or near the minimum. operations fail with a warning when the free space is at or near the minimum.
For information, see <a For information, see <a
href="/../../reference/commandline/dockerd/#storage-driver-options" href="/engine/reference/commandline/dockerd/#storage-driver-options"
target="_blank">the storage driver options in the Engine daemon reference</a>.<!-- fix_--> target="_blank">the storage driver options in the Engine daemon reference</a>.
### Examine devicemapper structures on the host ### Examine devicemapper structures on the host

View File

@ -17,7 +17,7 @@ docker/machine release page</a> on GitHub.
## Installing Machine Directly ## Installing Machine Directly
1. Install <a href="/installation/" 1. Install <a href="/engine/installation/"
target="_blank">the Docker binary</a>. target="_blank">the Docker binary</a>.
2. Download the Docker Machine binary and extract it to your PATH. 2. Download the Docker Machine binary and extract it to your PATH.

View File

@ -29,7 +29,7 @@ Testing documentation is relatively easy:
## Step 1. Find a page in <a href="/" target="_blank">Docker's documentation</a> that contains a procedure or example you want to test. ## Step 1. Find a page in <a href="/" target="_blank">Docker's documentation</a> that contains a procedure or example you want to test.
You should choose something that _should work_ on your machine. For example, You should choose something that _should work_ on your machine. For example,
<a href="/articles/baseimages/" target="_blank">creating <a href="/engine/userguide/eng-image/baseimages/" target="_blank">creating
a base image</a> is something anyone with Docker can do. While <a a base image</a> is something anyone with Docker can do. While <a
href="https://kitematic.com/docs/managing-volumes/" target="_blank">changing href="https://kitematic.com/docs/managing-volumes/" target="_blank">changing
volume directories in Kitematic</a> requires a Mac and Docker's Kitematic volume directories in Kitematic</a> requires a Mac and Docker's Kitematic

View File

@ -75,4 +75,4 @@ like-minded individuals, we have a number of open channels for communication.
* To contribute code or documentation changes: please submit a [pull request on Github](https://github.com/docker/swarm/pulls). * To contribute code or documentation changes: please submit a [pull request on Github](https://github.com/docker/swarm/pulls).
For more information and resources, please visit the [Getting Help project page](/project/get-help/). For more information and resources, please visit the [Getting Help project page](/opensource/get-help/).