@@ -1,10 +1,10 @@

-FROM docs/base:latest

+FROM docs/base:hugo-github-linking

 MAINTAINER Mary Anthony <mary@docker.com> (@moxiegirl)

 # To get the git info for this repo

 COPY . /src

-COPY . /docs/content/

+COPY . /docs/content/engine

 RUN svn checkout https://github.com/docker/compose/trunk/docs /docs/content/compose

 RUN svn checkout https://github.com/docker/swarm/trunk/docs /docs/content/swarm

@@ -14,16 +14,3 @@ RUN svn checkout https://github.com/kitematic/kitematic/trunk/docs /docs/content

 RUN svn checkout https://github.com/docker/tutorials/trunk/docs /docs/content/

 RUN svn checkout https://github.com/docker/opensource/trunk/docs /docs/content/opensource

-

-

-

-# Sed to process GitHub Markdown

-# 1-2 Remove comment code from metadata block

-# 3 Change ](/word to ](/project/ in links

-# 4 Change ](word.md) to ](/project/word)

-# 5 Remove .md extension from link text

-# 6 Change ](../ to ](/project/word) 

-# 7 Change ](../../ to ](/project/ --> not implemented

-# 

-# 

-RUN /src/pre-process.sh /docs

\ No newline at end of file

@@ -41,7 +41,7 @@ on other branches by special arrangement with the Docker maintainers.

 If you are a new or beginner contributor, we encourage you to read through the

 [our detailed contributors

-guide](https://docs.docker.com/project/who-written-for/). The guide explains in

+guide](who-written-for.md). The guide explains in

 detail, with examples, how to contribute. If you are an experienced contributor

 this quickstart should be enough to get you started.

@@ -89,7 +89,7 @@ own.

 6.  Check your writing for style and mechanical errors.

 	Use our [documentation style

-	guide](https://docs.docker.com/project/doc-style/) to check style. There are

+	guide](doc-style.md) to check style. There are

 	several [good grammar and spelling online

 	checkers](http://www.hemingwayapp.com/) that can check your writing

 	mechanics.

@@ -109,7 +109,7 @@ links that are referenced in the documentation—there should be none.

 ## Style guide

 If you have questions about how to write for Docker's documentation, please see

-the [style guide](project/doc-style.md). The style guide provides

+the [style guide](doc-style.md). The style guide provides

 guidance about grammar, syntax, formatting, styling, language, or tone. If

 something isn't clear in the guide, please submit an issue to let us know or

 submit a pull request to help us improve it.

@@ -10,8 +10,7 @@ parent = "smn_images"

 # Create a base image

-So you want to create your own [*Base Image*](

-/reference/glossary/#base-image)? Great!

+So you want to create your own [*Base Image*](../reference/glossary.md#base-image)? Great!

 The specific process will depend heavily on the Linux distribution you

 want to package. We have some examples below, and you are encouraged to

@@ -65,7 +64,7 @@ If you want to test it out, you can clone [the image repo](https://github.com/do

 There are lots more resources available to help you write your 'Dockerfile`.

-* There's a [complete guide to all the instructions](/reference/builder/) available for use in a `Dockerfile` in the reference section.

+* There's a [complete guide to all the instructions](../reference/builder.md) available for use in a `Dockerfile` in the reference section.

 * To help you write a clear, readable, maintainable `Dockerfile`, we've also

-written a [`Dockerfile` Best Practices guide](/articles/dockerfile_best-practices).

-* If your goal is to create a new Official Repository, be sure to read up on Docker's [Official Repositories](/docker-hub/official_repos/).

+written a [`Dockerfile` Best Practices guide](dockerfile_best-practices.md).

+* If your goal is to create a new Official Repository, be sure to read up on Docker's [Official Repositories](https://docs.docker.com/docker-hub/official_repos/).

@@ -29,7 +29,7 @@ to preface each `docker` command with `sudo`. One way to avoid having to use

 add users that will be entering `docker` commands to the 'docker' group.

 For more information about installing Docker or `sudo` configuration, refer to

-the [installation](/installation) instructions for your operating system.

+the [installation](../installation) instructions for your operating system.

 ## Download a pre-built image

@@ -38,7 +38,7 @@ the [installation](/installation) instructions for your operating system.

     $ docker pull ubuntu

 This will find the `ubuntu` image by name on

-[*Docker Hub*](/userguide/dockerrepos/#searching-for-images)

+[*Docker Hub*](../userguide/dockerrepos.md#searching-for-images)

 and download it from [Docker Hub](https://hub.docker.com) to a local

 image cache.

@@ -190,6 +190,6 @@ you already have, use the `docker images` command.

 You now have an image state from which you can create new instances.

 Read more about [*Share Images via

-Repositories*](/userguide/dockerrepos) or

+Repositories*](../userguide/dockerrepos.md) or

 continue to the complete [*Command

-Line*](/reference/commandline/cli)

+Line*](../reference/commandline/cli.md)

@@ -13,5 +13,5 @@ weight = 7

 The original content was deprecated. For information about configuring

 certificates, see  [deploying a registry

-server](http://docs.docker.com/registry/deploying/). To reach an older version

+server](http://docs.docker.com/registry/deploying). To reach an older version

 of this content, refer to an older version of the documentation. 

@@ -13,7 +13,7 @@ parent = "smn_third_party"

 > **Note**:

 > Please note this is a community contributed installation path. The only

 > `official` installation is using the

-> [*Ubuntu*](/installation/ubuntulinux) installation

+> [*Ubuntu*](../installation/ubuntulinux.md) installation

 > path. This version may sometimes be out of date.

 ## Requirements

@@ -57,7 +57,7 @@ These options :

 - Set `tls` to true with the server certificate and key specified using `--tlscert` and `--tlskey` respectively

 - Listen for connections on `tcp://192.168.59.3:2376`

-The command line reference has the [complete list of daemon flags](/reference/commandline/daemon)

+The command line reference has the [complete list of daemon flags](../reference/commandline/daemon.md)

 with explanations.

 ## Ubuntu

@@ -65,7 +65,7 @@ with explanations.

 As of `14.04`, Ubuntu uses Upstart as a process manager. By default, Upstart jobs

 are located in  `/etc/init` and the `docker` Upstart job can be found at `/etc/init/docker.conf`.

-After successfully [installing Docker for Ubuntu](/installation/ubuntulinux/),

+After successfully [installing Docker for Ubuntu](../installation/ubuntulinux.md),

 you can check the running status using Upstart in this way:

     $ sudo status docker

@@ -114,7 +114,7 @@ These options :

 - Set `tls` to true with the server certificate and key specified using `--tlscert` and `--tlskey` respectively

 - Listen for connections on `tcp://192.168.59.3:2376`

-The command line reference has the [complete list of daemon flags](/reference/commandline/daemon)

+The command line reference has the [complete list of daemon flags](../reference/commandline/daemon.md)

 with explanations.

@@ -150,8 +150,7 @@ can be located at `/var/log/upstart/docker.log`

 As of `7.x`, CentOS and RHEL use `systemd` as the process manager. As of `21`, Fedora uses

 `systemd` as its process manager.

-After successfully installing Docker for [CentOS](/installation/centos/)/[Red Hat Enterprise Linux]

-(/installation/rhel/)/[Fedora](/installation/fedora), you can check the running status in this way:

+After successfully installing Docker for [CentOS](../installation/centos.md)/[Red Hat Enterprise Linux](../installation/rhel.md)/[Fedora](../installation/fedora.md), you can check the running status in this way:

     $ sudo systemctl status docker

@@ -207,7 +206,7 @@ These options :

 - Set `tls` to true with the server certificate and key specified using `--tlscert` and `--tlskey` respectively

 - Listen for connections on `tcp://192.168.59.3:2376`

-The command line reference has the [complete list of daemon flags](/reference/commandline/daemon)

+The command line reference has the [complete list of daemon flags](../reference/commandline/daemon.md)

 with explanations.

 5. Save and close the file.

@@ -16,7 +16,7 @@ Docker can build images automatically by reading the instructions from a

 `Dockerfile`, a text file that contains all the commands, in order, needed to

 build a given image. `Dockerfile`s adhere to a specific format and use a

 specific set of instructions. You can learn the basics on the

-[Dockerfile Reference](https://docs.docker.com/reference/builder/) page. If

+[Dockerfile Reference](../reference/builder.md) page. If

 you’re new to writing `Dockerfile`s, you should start there.

 This document covers the best practices and methods recommended by Docker,

@@ -27,7 +27,7 @@ if you’re creating an Official Image, you *must* adhere to these practices).

 You can see many of these practices and recommendations in action in the [buildpack-deps `Dockerfile`](https://github.com/docker-library/buildpack-deps/blob/master/jessie/Dockerfile).

 > Note: for more detailed explanations of any of the Dockerfile commands

->mentioned here, visit the [Dockerfile Reference](https://docs.docker.com/reference/builder/) page.

+>mentioned here, visit the [Dockerfile Reference](../reference/builder.md) page.

 ## General guidelines and recommendations

@@ -45,7 +45,7 @@ add to that directory only the files needed for building the Dockerfile. To

 increase the build's performance, you can exclude files and directories by

 adding a `.dockerignore` file to that directory as well. This file supports

 exclusion patterns similar to `.gitignore` files. For information on creating one,

-see the [.dockerignore file](../../reference/builder/#dockerignore-file).

+see the [.dockerignore file](../reference/builder.md#dockerignore-file).

 ### Avoid installing unnecessary packages

@@ -59,7 +59,7 @@ in a database image.

 In almost all cases, you should only run a single process in a single

 container. Decoupling applications into multiple containers makes it much

 easier to scale horizontally and reuse containers. If that service depends on

-another service, make use of [container linking](https://docs.docker.com/userguide/dockerlinks/).

+another service, make use of [container linking](../userguide/dockerlinks.md).

 ### Minimize the number of layers

@@ -128,7 +128,7 @@ various instructions available for use in a `Dockerfile`.

 ### FROM

-[Dockerfile reference for the FROM instruction](https://docs.docker.com/reference/builder/#from)

+[Dockerfile reference for the FROM instruction](../reference/builder.md#from)

 Whenever possible, use current Official Repositories as the basis for your

 image. We recommend the [Debian image](https://registry.hub.docker.com/_/debian/)

@@ -137,7 +137,7 @@ since it’s very tightly controlled and kept extremely minimal (currently under

 ### RUN

-[Dockerfile reference for the RUN instruction](https://docs.docker.com/reference/builder/#run)

+[Dockerfile reference for the RUN instruction](../reference/builder.md#run)

 As always, to make your `Dockerfile` more readable, understandable, and

 maintainable, split long or complex `RUN` statements on multiple lines separated

@@ -233,7 +233,7 @@ keep the image size down. Since the `RUN` statement starts with

 ### CMD

-[Dockerfile reference for the CMD instruction](https://docs.docker.com/reference/builder/#cmd)

+[Dockerfile reference for the CMD instruction](../reference/builder.md#cmd)

 The `CMD` instruction should be used to run the software contained by your

 image, along with any arguments. `CMD` should almost always be used in the

@@ -247,13 +247,13 @@ perl, etc), for example, `CMD ["perl", "-de0"]`, `CMD ["python"]`, or

 `CMD [“php”, “-a”]`. Using this form means that when you execute something like

 `docker run -it python`, you’ll get dropped into a usable shell, ready to go.

 `CMD` should rarely be used in the manner of `CMD [“param”, “param”]` in

-conjunction with [`ENTRYPOINT`](https://docs.docker.com/reference/builder/#entrypoint), unless

+conjunction with [`ENTRYPOINT`](../reference/builder.md#entrypoint), unless

 you and your expected users are already quite familiar with how `ENTRYPOINT`

 works.

 ### EXPOSE

-[Dockerfile reference for the EXPOSE instruction](https://docs.docker.com/reference/builder/#expose)

+[Dockerfile reference for the EXPOSE instruction](../reference/builder.md#expose)

 The `EXPOSE` instruction indicates the ports on which a container will listen

 for connections. Consequently, you should use the common, traditional port for

@@ -268,7 +268,7 @@ the recipient container back to the source (ie, `MYSQL_PORT_3306_TCP`).

 ### ENV

-[Dockerfile reference for the ENV instruction](https://docs.docker.com/reference/builder/#env)

+[Dockerfile reference for the ENV instruction](../reference/builder.md#env)

 In order to make new software easier to run, you can use `ENV` to update the

 `PATH` environment variable for the software your container installs. For

@@ -293,8 +293,8 @@ auto-magically bump the version of the software in your container.

 ### ADD or COPY

-[Dockerfile reference for the ADD instruction](https://docs.docker.com/reference/builder/#add)<br/>

-[Dockerfile reference for the COPY instruction](https://docs.docker.com/reference/builder/#copy)

+[Dockerfile reference for the ADD instruction](../reference/builder.md#add)<br/>

+[Dockerfile reference for the COPY instruction](../reference/builder.md#copy)

 Although `ADD` and `COPY` are functionally similar, generally speaking, `COPY`

 is preferred. That’s because it’s more transparent than `ADD`. `COPY` only

@@ -339,7 +339,7 @@ auto-extraction capability, you should always use `COPY`.

 ### ENTRYPOINT

-[Dockerfile reference for the ENTRYPOINT instruction](https://docs.docker.com/reference/builder/#entrypoint)

+[Dockerfile reference for the ENTRYPOINT instruction](../reference/builder.md#entrypoint)

 The best use for `ENTRYPOINT` is to set the image's main command, allowing that

 image to be run as though it was that command (and then use `CMD` as the

@@ -389,7 +389,7 @@ exec "$@"

 > This script uses [the `exec` Bash command](http://wiki.bash-hackers.org/commands/builtin/exec)

 > so that the final running application becomes the container's PID 1. This allows

 > the application to receive any Unix signals sent to the container.

-> See the [`ENTRYPOINT`](https://docs.docker.com/reference/builder/#entrypoint)

+> See the [`ENTRYPOINT`](../reference/builder.md#entrypoint)

 > help for more details.

@@ -415,7 +415,7 @@ Lastly, it could also be used to start a totally different tool, such as Bash:

 ### VOLUME

-[Dockerfile reference for the VOLUME instruction](https://docs.docker.com/reference/builder/#volume)

+[Dockerfile reference for the VOLUME instruction](../reference/builder.md#volume)

 The `VOLUME` instruction should be used to expose any database storage area,

 configuration storage, or files/folders created by your docker container. You

@@ -424,7 +424,7 @@ parts of your image.

 ### USER

-[Dockerfile reference for the USER instruction](https://docs.docker.com/reference/builder/#user)

+[Dockerfile reference for the USER instruction](../reference/builder.md#user)

 If a service can run without privileges, use `USER` to change to a non-root

 user. Start by creating the user and group in the `Dockerfile` with something

@@ -445,7 +445,7 @@ and forth frequently.

 ### WORKDIR

-[Dockerfile reference for the WORKDIR instruction](https://docs.docker.com/reference/builder/#workdir)

+[Dockerfile reference for the WORKDIR instruction](../reference/builder.md#workdir)

 For clarity and reliability, you should always use absolute paths for your

 `WORKDIR`. Also, you should use `WORKDIR` instead of  proliferating

@@ -454,7 +454,7 @@ troubleshoot, and maintain.

 ### ONBUILD

-[Dockerfile reference for the ONBUILD instruction](https://docs.docker.com/reference/builder/#onbuild)

+[Dockerfile reference for the ONBUILD instruction](../reference/builder.md#onbuild)

 An `ONBUILD` command executes after the current `Dockerfile` build completes.

 `ONBUILD` executes in any child image derived `FROM` the current image.  Think

@@ -488,8 +488,8 @@ These Official Repositories have exemplary `Dockerfile`s:

 ## Additional resources:

-* [Dockerfile Reference](https://docs.docker.com/reference/builder/)

-* [More about Base Images](https://docs.docker.com/articles/baseimages/)

+* [Dockerfile Reference](../reference/builder.md)

+* [More about Base Images](baseimages.md)

 * [More about Automated Builds](https://docs.docker.com/docker-hub/builds/)

 * [Guidelines for Creating Official

 Repositories](https://docs.docker.com/docker-hub/official_repos/)

@@ -12,7 +12,7 @@ weight = 99

 # Automatically start containers

 As of Docker 1.2,

-[restart policies](/reference/run/#restart-policies-restart) are the

+[restart policies](../reference/run.md#restart-policies-restart) are the

 built-in Docker mechanism for restarting containers when they exit. If set,

 restart policies will be used when the Docker daemon starts up, as typically

 happens after a system boot. Restart policies will ensure that linked containers

@@ -30,7 +30,7 @@ range from `02:42:ac:11:00:00` to `02:42:ac:11:ff:ff`.

 > and options for Docker. In most cases you won't need this information.

 > If you're looking to get started with a simpler explanation of Docker

 > networking and an introduction to the concept of container linking see

-> the [Docker User Guide](/userguide/dockerlinks/).

+> the [Docker User Guide](../userguide/dockerlinks.md).

 But `docker0` is no ordinary interface.  It is a virtual *Ethernet

 bridge* that automatically forwards packets between any other network

@@ -357,7 +357,7 @@ services.  If the Docker daemon is running with both `--icc=false` and

 `ACCEPT` rules so that the new container can connect to the ports

 exposed by the other container — the ports that it mentioned in the

 `EXPOSE` lines of its `Dockerfile`.  Docker has more documentation on

-this subject — see the [linking Docker containers](/userguide/dockerlinks)

+this subject — see the [linking Docker containers](../userguide/dockerlinks.md)

 page for further details.

 > **Note**:

@@ -425,7 +425,7 @@ machine that the Docker server creates when it starts:

 But if you want containers to accept incoming connections, you will need

 to provide special options when invoking `docker run`.  These options

-are covered in more detail in the [Docker User Guide](/userguide/dockerlinks)

+are covered in more detail in the [Docker User Guide](../userguide/dockerlinks.md)

 page.  There are two approaches.

 First, you can supply `-P` or `--publish-all=true|false` to `docker run` which

@@ -489,7 +489,7 @@ connect to a local container exposed port through the commonly used loopback

 address: this alternative is preferred for performance reasons.

 Again, this topic is covered without all of these low-level networking

-details in the [Docker User Guide](/userguide/dockerlinks/) document if you

+details in the [Docker User Guide](../userguide/dockerlinks.md) document if you

 would like to use that as your port redirection reference instead.

 ## IPv6

@@ -538,7 +538,7 @@ want to configure `eth0` via Router Advertisements you should set:

     $ sysctl net.ipv6.conf.eth0.accept_ra=2

-![](/article-img/ipv6_basic_host_config.svg)

+![](../article-img/ipv6_basic_host_config.svg)

 Every new container will get an IPv6 address from the defined subnet. Further

 a default route will be added on `eth0` in the container via the address

@@ -568,7 +568,7 @@ Often servers or virtual machines get a `/64` IPv6 subnet assigned (e.g.

 Docker a `/80` subnet while using a separate `/80` subnet for other

 applications on the host:

-![](/article-img/ipv6_slash64_subnet_config.svg)

+![](../article-img/ipv6_slash64_subnet_config.svg)

 In this setup the subnet `2001:db8:23:42::/80` with a range from `2001:db8:23:42:0:0:0:0`

 to `2001:db8:23:42:0:ffff:ffff:ffff` is attached to `eth0`, with the host listening

@@ -606,7 +606,7 @@ is connected to `eth0`. This means all devices (containers) with the addresses

 from the Docker subnet are expected to be found within the router subnet.

 Therefore the router thinks it can talk to these containers directly.

-![](/article-img/ipv6_ndp_proxying.svg)

+![](../article-img/ipv6_ndp_proxying.svg)

 As soon as the router wants to send an IPv6 packet to the first container it

 will transmit a neighbor solicitation request, asking, who has

@@ -645,7 +645,7 @@ Using routable IPv6 addresses allows you to realize communication between

 containers on different hosts. Let's have a look at a simple Docker IPv6 cluster

 example:

-![](/article-img/ipv6_switched_network_example.svg)

+![](../article-img/ipv6_switched_network_example.svg)

 The Docker hosts are in the `2001:db8:0::/64` subnet. Host1 is configured

 to provide addresses from the `2001:db8:1::/64` subnet to its containers. It

@@ -695,7 +695,7 @@ routing information about the Docker subnets. When you add or remove a host to

 this environment you just have to update the routing table in the router - not

 on every host.

-![](/article-img/ipv6_routed_network_example.svg)

+![](../article-img/ipv6_routed_network_example.svg)

 In this scenario containers of the same host can communicate directly with each

 other. The traffic between containers on different hosts will be routed via

@@ -12,7 +12,7 @@ parent = "smn_third_party"

 > *Note:* Please note this is a community contributed installation path. The

 > only `official` installation is using the

-> [*Ubuntu*](/installation/ubuntulinux) installation

+> [*Ubuntu*](../installation/ubuntulinux.md) installation

 > path. This version may sometimes be out of date.

 ## Requirements

@@ -26,7 +26,7 @@ The following is a sample output from the `docker stats` command

     redis2              0.07%               2.746 MB / 64 MB      4.29%               1.266 KB / 648 B    12.4 MB / 0 B

-The [docker stats](/reference/commandline/stats/) reference page has

+The [docker stats](../reference/commandline/stats.md) reference page has

 more details about the `docker stats` command.

 ## Control groups

@@ -335,7 +335,7 @@ layer; you will also have to add traffic going through the userland

 proxy.

 Then, you will need to check those counters on a regular basis. If you

-happen to use `collectd`, there is a [nice plugin](https://collectd.org/wiki/index.php/Plugin:IPTables)

+happen to use `collectd`, there is a [nice plugin](https://collectd.org/wiki/index.php/Table_of_Plugins)

 to automate iptables counters collection.

 ### Interface-level counters

@@ -39,7 +39,7 @@ of another container. Of course, if the host system is setup

 accordingly, containers can interact with each other through their

 respective network interfaces — just like they can interact with

 external hosts. When you specify public ports for your containers or use

-[*links*](/userguide/dockerlinks)

+[*links*](../userguide/dockerlinks.md)

 then IP traffic is allowed between containers. They can ping each other,

 send/receive UDP packets, and establish TCP connections, but that can be

 restricted if necessary. From a network architecture point of view, all

@@ -115,7 +115,7 @@ However, if you do that, being aware of the above mentioned security

 implication, you should ensure that it will be reachable only from a

 trusted network or VPN; or protected with e.g., `stunnel` and client SSL

 certificates. You can also secure them with [HTTPS and

-certificates](/articles/https/).

+certificates](../articles/https/).

 The daemon is also potentially vulnerable to other inputs, such as image

 loading from either disk with 'docker load', or from the network with

@@ -10,8 +10,9 @@ parent = "smn_third_party"

 # Using Supervisor with Docker

-> **Note**: **If you don't like sudo** then see [*Giving non-root

-> access*](/installation/binaries/#giving-non-root-access)

+> **Note**:

+> - **If you don't like sudo** then see [*Giving non-root

+>   access*](../installation/binaries.md#giving-non-root-access)

 Traditionally a Docker container runs a single process when it is

 launched, for example an Apache daemon or a SSH server daemon. Often

@@ -10,10 +10,11 @@ parent = "smn_applied"

 # Dockerizing an apt-cacher-ng service

-> **Note**: **If you don't like sudo** then see [*Giving non-root

-> access*](/installation/binaries/#giving-non-root-access).

-> **If you're using OS X or Docker via TCP** then you shouldn't use

-> sudo.

+> **Note**: 

+> - **If you don't like sudo** then see [*Giving non-root

+>   access*](../installation/binaries.md#giving-non-root-access).

+> - **If you're using OS X or docker via TCP** then you shouldn't use

+>   sudo.

 When you have multiple Docker servers, or build unrelated Docker

 containers which can't make use of the Docker build cache, it can be

@@ -10,8 +10,9 @@ parent = "smn_applied"

 # Dockerizing a CouchDB service

-> **Note**: **If you don't like sudo** then see [*Giving non-root

-> access*](/installation/binaries/#giving-non-root-access)

+> **Note**: 

+> - **If you don't like sudo** then see [*Giving non-root

+>   access*](../installation/binaries.md#giving-non-root-access)

 Here's an example of using data volumes to share the same data between

 two CouchDB containers. This could be used for hot upgrades, testing

@@ -14,10 +14,10 @@ weight = 8

 This section contains the following:

-* [Dockerizing MongoDB](/examples/mongodb/)

-* [Dockerizing PostgreSQL](/examples/postgresql_service/)    

-* [Dockerizing a CouchDB service](/examples/couchdb_data_volumes/)         

-* [Dockerizing a Node.js web app](/examples/nodejs_web_app/)

-* [Dockerizing a Redis service](/examples/running_redis_service/)

-* [Dockerizing an apt-cacher-ng service](/examples/apt-cacher-ng/)

-* [Dockerizing applications: A 'Hello world'](/userguide/dockerizing)

+* [Dockerizing MongoDB](mongodb.md)

+* [Dockerizing PostgreSQL](postgresql_service.md)    

+* [Dockerizing a CouchDB service](couchdb_data_volumes.md)         

+* [Dockerizing a Node.js web app](nodejs_web_app.md)

+* [Dockerizing a Redis service](running_redis_service.md)

+* [Dockerizing an apt-cacher-ng service](apt-cacher-ng.md)

+* [Dockerizing applications: A 'Hello world'](../userguide/dockerizing.md)

@@ -29,7 +29,7 @@ instances will bring several benefits, such as:

 > **Note:**

 >

 > If you do **_not_** like `sudo`, you might want to check out:

-> [*Giving non-root access*](/installation/binaries/#giving-non-root-access).

+> [*Giving non-root access*](../installation/binaries.md#giving-non-root-access).

 ## Creating a Dockerfile for MongoDB

@@ -172,6 +172,6 @@ the exposed port to two different ports on the host

     $ mongo --port 28001

     $ mongo --port 28002

- - [Linking containers](/userguide/dockerlinks)

- - [Cross-host linking containers](/articles/ambassador_pattern_linking/)

- - [Creating an Automated Build](/docker-io/builds/#automated-builds)

+ - [Linking containers](../userguide/dockerlinks.md)

+ - [Cross-host linking containers](../articles/ambassador_pattern_linking.md)

+ - [Creating an Automated Build](https://docs.docker.com/docker-hub/builds/)

@@ -10,12 +10,14 @@ parent = "smn_applied"

 # Dockerizing a Node.js web app

-> **Note**: **If you don't like sudo** then see [*Giving non-root

-> access*](/installation/binaries/#giving-non-root-access)

-

-In this example, we are going to learn how to build a Docker image to run a

-simple Node.js "hello world" web application on CentOS. You can get the full source code at

-[https://github.com/enokd/docker-node-hello/](https://github.com/enokd/docker-node-hello/).

+> **Note**: 

+> - **If you don't like sudo** then see [*Giving non-root

+>   access*](../installation/binaries.md#giving-non-root-access)

+

+The goal of this example is to show you how you can build your own

+Docker images from a parent image using a `Dockerfile`

+. We will do that by making a simple Node.js hello world web

+application running on CentOS. You can get the full source code at[https://github.com/enokd/docker-node-hello/](https://github.com/enokd/docker-node-hello/).

 ## Create Node.js app

@@ -10,8 +10,9 @@ parent = "smn_applied"

 # Dockerizing PostgreSQL

-> **Note**: **If you don't like sudo** then see [*Giving non-root

-> access*](/installation/binaries/#giving-non-root-access)

+> **Note**: 

+> - **If you don't like sudo** then see [*Giving non-root

+>   access*](../installation/binaries.md#giving-non-root-access)

 ## Installing PostgreSQL on Docker

@@ -84,7 +85,7 @@ And run the PostgreSQL server container (in the foreground):

     $ docker run --rm -P --name pg_test eg_postgresql

 There are 2 ways to connect to the PostgreSQL server. We can use [*Link

-Containers*](/userguide/dockerlinks), or we can access it from our host

+Containers*](../userguide/dockerlinks.md), or we can access it from our host

 (or the network).

 > **Note**:

@@ -15,7 +15,7 @@ weight = 6

 Currently, you can extend Docker by adding a plugin. This section contains the following topics:

-* [Understand Docker plugins](/extend/plugins.md)

-* [Write a volume plugin](/extend/plugins_volume.md)

-* [Write a network plugin](/extend/plugins_network.md)

-* [Docker plugin API](/extend/plugin_api.md)

+* [Understand Docker plugins](plugins.md)

+* [Write a volume plugin](plugins_volume.md)

+* [Write a network plugin](plugins_network.md)

+* [Docker plugin API](plugin_api.md)

@@ -16,7 +16,7 @@ Docker Engine.

 This page is intended for people who want to develop their own Docker plugin.

 If you just want to learn about or use Docker plugins, look

-[here](/extend/plugins).

+[here](plugins.md).

 ## What plugins are

@@ -17,9 +17,9 @@ plugins.

 ## Types of plugins

 Plugins extend Docker's functionality.  They come in specific types.  For

-example, a [volume plugin](/extend/plugins_volume.md) might enable Docker

+example, a [volume plugin](plugins_volume.md) might enable Docker

 volumes to persist across multiple Docker hosts and a 

-[network plugin](/extend/plugins_network.md) might provide network plumbing

+[network plugin](plugins_network.md) might provide network plumbing

 using a favorite networking technology, such as vxlan overlay, ipvlan, EVPN, etc.

 Currently Docker supports volume and network driver plugins. In the future it

@@ -73,4 +73,4 @@ of the plugin for help. The Docker team may not be able to assist you.

 ## Writing a plugin

 If you are interested in writing a plugin for Docker, or seeing how they work

-under the hood, see the [docker plugins reference](/extend/plugin_api).

+under the hood, see the [docker plugins reference](plugin_api.md).

@@ -1,10 +1,21 @@

+<!--[metadata]>

+title = "Docker network driver plugins"

+description = "Network drive plugins."

+keywords = ["Examples, Usage, plugins, docker, documentation, user guide"]

+[menu.main]

+parent = "mn_extend"

+weight=-1

+<![end-metadata]-->

+

 # Docker network driver plugins

-Docker supports network driver plugins via 

-[LibNetwork](https://github.com/docker/libnetwork). Network driver plugins are 

-implemented as "remote drivers" for LibNetwork, which shares plugin 

-infrastructure with Docker. In effect this means that network driver plugins 

-are activated in the same way as other plugins, and use the same kind of 

+Docker supports network driver plugins via

+[LibNetwork](https://github.com/docker/libnetwork). Network driver plugins are

+implemented as "remote drivers" for LibNetwork, which shares plugin

+infrastructure with Docker. In effect this means that network driver plugins

+are activated in the same way as other plugins, and use the same kind of

 protocol.

 ## Using network driver plugins

@@ -18,7 +29,7 @@ commands. For example,

     docker network create -d weave mynet

-Some network driver plugins are listed in [plugins.md](/docs/extend/plugins.md)

+Some network driver plugins are listed in [plugins](plugins.md)

 The network thus created is owned by the plugin, so subsequent commands

 referring to that network will also be run through the plugin such as,

@@ -12,7 +12,7 @@ parent = "mn_extend"

 Docker volume plugins enable Docker deployments to be integrated with external

 storage systems, such as Amazon EBS, and enable data volumes to persist beyond

-the lifetime of a single Docker host. See the [plugin documentation](/extend/plugins)

+the lifetime of a single Docker host. See the [plugin documentation](plugins.md)

 for more information.

 # Command-line changes

@@ -91,7 +91,7 @@ flag is set to `yes` like so:

 If you need to add an HTTP Proxy, set a different directory or partition for the

 Docker runtime files, or make other customizations, read the systemd article to

-learn how to [customize your systemd Docker daemon options](/articles/systemd/).

+learn how to [customize your systemd Docker daemon options](../articles/systemd.md).

 ## Uninstallation

@@ -113,4 +113,4 @@ You can find more details about Docker on openSUSE or SUSE Linux Enterprise in

 the [Docker quick start guide](https://www.suse.com/documentation/sles-12/dockerquick/data/dockerquick.

 html) on the SUSE website. The document targets SUSE Linux Enterprise, but its contents apply also to openSUSE.

-Continue to the [User Guide](/userguide/).

+Continue to the [User Guide](../userguide/).

@@ -64,7 +64,7 @@ To start on system boot:

 If you need to add an HTTP Proxy, set a different directory or partition for the

 Docker runtime files, or make other customizations, read our systemd article to

-learn how to [customize your systemd Docker daemon options](/articles/systemd/).

+learn how to [customize your systemd Docker daemon options](../articles/systemd.md).

 ## Running Docker with a manually-defined network

@@ -24,7 +24,7 @@ machines on Azure:

 ## What next?

-Continue with the [User Guide](/userguide/).

+Continue with the [User Guide](../userguide/).

 [0]: http://azure.microsoft.com/

 [1]: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-docker-vm-extension/

@@ -37,7 +37,7 @@ runtime:

 ## Check kernel dependencies

 Docker in daemon mode has specific kernel requirements. For details,

-check your distribution in [*Installation*](../#installation-list).

+check your distribution in [*Installation*](../installation#installation-list).

 A 3.10 Linux kernel is the minimum requirement for Docker.

 Kernels older than 3.10 lack some of the features required to run Docker

@@ -192,8 +192,7 @@ need to add `sudo` to all the client commands.

 > **Warning**: 

 > The *docker* group (or the group specified with `-G`) is root-equivalent;

-> see [*Docker Daemon Attack Surface*](

-> /articles/security/#docker-daemon-attack-surface) details.

+> see [*Docker Daemon Attack Surface*](../articles/security.md#docker-daemon-attack-surface) details.

 ## Upgrades

@@ -212,4 +211,4 @@ Then follow the regular installation steps.

     # run a container and open an interactive shell in the container

     $ sudo ./docker run -i -t ubuntu /bin/bash

-Continue with the [User Guide](/userguide/).

+Continue with the [User Guide](../userguide).

@@ -134,7 +134,7 @@ makes the ownership of the Unix socket read/writable by the `docker` group.

 >**Warning**: The `docker` group is equivalent to the `root` user; For details

 >on how this impacts security in your system, see [*Docker Daemon Attack

->Surface*](/articles/security/#docker-daemon-attack-surface) for details.

+>Surface*](../articles/security.md#docker-daemon-attack-surface) for details.

 To create the `docker` group and add your user:

@@ -160,7 +160,7 @@ To ensure Docker starts when you boot your system, do the following:

 If you need to add an HTTP Proxy, set a different directory or partition for the

 Docker runtime files, or make other customizations, read our Systemd article to

-learn how to [customize your Systemd Docker daemon options](/articles/systemd/).

+learn how to [customize your Systemd Docker daemon options](../articles/systemd.md).

 ## Uninstall

@@ -123,8 +123,7 @@ use the `-G` flag to specify an alternative group.

 > **Warning**:

 > The `docker` group (or the group specified with the `-G` flag) is

-> `root`-equivalent; see [*Docker Daemon Attack Surface*](

-> /articles/security/#docker-daemon-attack-surface) details.

+> `root`-equivalent; see [*Docker Daemon Attack Surface*](../articles/security.md#docker-daemon-attack-surface) details.

 **Example:**

@@ -166,4 +165,4 @@ You must delete the user created configuration files manually.

 ## What next?

-Continue with the [User Guide](/userguide/).

+Continue with the [User Guide](../userguide/).

@@ -141,7 +141,7 @@ makes the ownership of the Unix socket read/writable by the `docker` group.

 >**Warning**: The `docker` group is equivalent to the `root` user; For details

 >on how this impacts security in your system, see [*Docker Daemon Attack

->Surface*](/articles/security/#docker-daemon-attack-surface) for details.

+>Surface*](../articles/security.md#docker-daemon-attack-surface) for details.

 To create the `docker` group and add your user:

@@ -167,7 +167,7 @@ To ensure Docker starts when you boot your system, do the following:

 If you need to add an HTTP Proxy, set a different directory or partition for the

 Docker runtime files, or make other customizations, read our Systemd article to

-learn how to [customize your Systemd Docker daemon options](/articles/systemd/).

+learn how to [customize your Systemd Docker daemon options](../articles/systemd.md).

 ## Running Docker with a manually-defined network

@@ -53,7 +53,7 @@ To start on system boot:

 If you need to add an HTTP Proxy, set a different directory or partition for the

 Docker runtime files, or make other customizations, read our systemd article to

-learn how to [customize your systemd Docker daemon options](/articles/systemd/).

+learn how to [customize your systemd Docker daemon options](../articles/systemd.md).

 ## Uninstallation

@@ -100,7 +100,7 @@ To start on system boot:

 If you need to add an HTTP Proxy, set a different directory or partition for the

 Docker runtime files, or make other customizations, read our systemd article to

-learn how to [customize your systemd Docker daemon options](/articles/systemd/).

+learn how to [customize your systemd Docker daemon options](../articles/systemd.md).

 ## Uninstallation

@@ -11,31 +11,31 @@ keywords = ["Docker install "]

 Docker Engine is supported on Linux, Cloud, Windows, and OS X. Installation instructions are available for the following: 

 ## On Linux

-* [Arch Linux](archlinux)

-* [CentOS](centos)

-* [CRUX Linux](cruxlinux)

-* [Debian](debian)

-* [Fedora](fedora)

-* [FrugalWare](frugalware)

-* [Gentoo](gentoolinux)

-* [Oracle Linux](oracle)

-* [Red Hat Enterprise Linux](rhel)

-* [openSUSE and SUSE Linux Enterprise](SUSE)

-* [Ubuntu](ubuntulinux)

-

-If your linux distribution is not listed above, don't give up yet. To try out Docker on a distribution that is not listed above, go here: [Installation from binaries](binaries).

+* [Arch Linux](archlinux.md)

+* [CentOS](centos.md)

+* [CRUX Linux](cruxlinux.md)

+* [Debian](debian.md)