-
diff --git a/docker-for-mac/examples.md b/docker-for-mac/examples.md
index 0eee11e3e0..cdf5b7a6be 100644
--- a/docker-for-mac/examples.md
+++ b/docker-for-mac/examples.md
@@ -26,13 +26,3 @@ For now, if you want get started experimenting with the Beta apps and Docker Com
See also [learn by example](/engine/tutorials/index.md) tutorials on building images, runnning containers, networking, managing data, and storing images on Docker Hub.
-
-
- 
Help improve the documentation
-
- Email us at feedback@docker.com -
--
-
-
-
A blob is any kind of content that is stored by a Registry under a content-addressable identifier (a "digest").
- Layers are a good example of "blobs". + Layers are a good example of "blobs".
@@ -19,9 +19,9 @@ This page contains definitions for distribution related terms.
-
An image is a named set of immutable data from which a Docker container can be created.
- An image is represented by a json file called a manifest, and is conceptually a set of layers. + An image is represented by a json file called a manifest, and is conceptually a set of layers. - Image names indicate the location where they can be pulled from and pushed to, as they usually start with a registry domain name and port. + Image names indicate the location where they can be pulled from and pushed to, as they usually start with a registry domain name and port.
@@ -30,7 +30,7 @@ This page contains definitions for distribution related terms.
-
A layer is a tar archive bundling partial content from a filesystem.
- Layers from an image are usually extracted in order on top of each other to make up a root filesystem from which containers run out. + Layers from an image are usually extracted in order on top of each other to make up a root filesystem from which containers run out.
@@ -45,7 +45,7 @@ This page contains definitions for distribution related terms.
Registry
- A registry is a service that let you store and deliver images.
+A registry is a service that let you store and deliver images.
Repository
@@ -57,12 +57,12 @@ This page contains definitions for distribution related terms.
A scope is the portion of a namespace onto which a given authorization token is granted.
Tag
- A tag is conceptually a "version" of a named image.
+A tag is conceptually a "version" of a named image.
Example: `docker pull myimage:latest` instructs docker to pull the image "myimage" in version "latest".
- +
-
diff --git a/docker-for-mac/faqs.md b/docker-for-mac/faqs.md
index 371783fe90..5db9027983 100644
--- a/docker-for-mac/faqs.md
+++ b/docker-for-mac/faqs.md
@@ -109,7 +109,7 @@ For a full explanation and examples, see [I want to connect to a container from
Note that you need a Mac that supports hardware virtualization, which is most non ancient ones; i.e., use OS X `10.10.3+` or `10.11` (OS X Yosemite or OS X El Capitan). See also "What to know before you install" in [Getting Started](index.md).
-
+
### Do I need to uninstall Docker Toolbox to use Docker for Mac?
No, you can use these side by side. Docker Toolbox leverages a Docker daemon installed using `docker-machine` in a machine called `default`. Running `eval $(docker-machine env default)` in a shell sets DOCKER environment variables locally to connect to the default machine using Engine from Toolbox. To check whether Toolbox DOCKER environment variables are set, run `env | grep DOCKER`.
@@ -142,14 +142,3 @@ consume any resources unless Docker.app connects to it, so it's safe to ignore.
### Can I pass through a USB device to a container?
Unfortunately it is not possible to pass through a USB device (or a serial port) to a container. For use cases requiring this, we recommend the use of [Docker Toolbox](/toolbox/overview.md).
-
-
-
- Help improve the documentation
-
- Email us at feedback@docker.com -
--
-
-
-
diff --git a/docker-for-mac/index.md b/docker-for-mac/index.md
index 4c5b9122ea..e8a84496ab 100644
--- a/docker-for-mac/index.md
+++ b/docker-for-mac/index.md
@@ -24,7 +24,6 @@ Please read through these topics on how to get started. To **give us feedback**
>**Already have Docker for Mac?** If you already have Docker for Mac installed, and are ready to get started, skip over to the [Getting Started with Docker](/engine/getstarted/index.md) tutorial.
-
## Download Docker for Mac
If you have not already done so, please install Docker for Mac. You can download installers from the stable or beta channel.
@@ -44,24 +43,24 @@ For more about stable and beta channels, see the [FAQs](faqs.md#stable-and-beta-
-
- Help improve the documentation
-
- Email us at feedback@docker.com -
-- Download checksum: Docker.dmg SHA256 + Download checksum: Docker.dmg SHA256
- Download checksum: Docker.dmg SHA256 + Download checksum: Docker.dmg SHA256
-
-
-
-
diff --git a/docker-for-mac/multi-arch.md b/docker-for-mac/multi-arch.md
index 44b7c5852c..d9f72a6b11 100644
--- a/docker-for-mac/multi-arch.md
+++ b/docker-for-mac/multi-arch.md
@@ -35,13 +35,3 @@ Running containers pre-configured with `qemu` has the advantage that you can use
Alternatively, you can bind mount in the `qemu` static binaries to any cross-architecture package, such as the semi-official ones using a script like this one https://github.com/justincormack/cross-docker. (See the README at the given link for details on how to use the script.)
-
-
- 
Help improve the documentation
-
- Email us at feedback@docker.com -
--
-
-
-
diff --git a/docker-for-mac/networking.md b/docker-for-mac/networking.md
index 77a2333b98..bc03cedfb0 100644
--- a/docker-for-mac/networking.md
+++ b/docker-for-mac/networking.md
@@ -108,13 +108,3 @@ See the [run commmand](/engine/reference/commandline/run.md) for more details on
We understand that these workarounds are not ideal, but there are several problems. In particular, there is a bug in OSX that is only fixed in 10.12 and is not being backported as far as we can tell, which means that we could not support this in all supported OSX versions. In addition, this network setup would require root access which we are trying to avoid entirely in Docker for Mac (we currently have a very small root helper that we are trying to remove).
-
-
- Help improve the documentation
-
- Email us at feedback@docker.com -
--
-
-
-
diff --git a/docker-for-mac/opensource.md b/docker-for-mac/opensource.md
index e162d815ed..99a0ad1065 100644
--- a/docker-for-mac/opensource.md
+++ b/docker-for-mac/opensource.md
@@ -22,13 +22,3 @@ Docker Desktop Editions distribute some components that are licensed under the G
The sources for `qemu-img` can be obtained [here](http://wiki.qemu-project.org/download/qemu-2.4.1.tar.bz2).
The sources for the `gettext` and `glib` libraries that `qemu-img` requires were obtained from [Homebrew](https://brew.sh) and may be retrieved using `brew install --build-from-source gettext glib`.
-
-
- Help improve the documentation
-
- Email us at feedback@docker.com -
--
-
-
-
diff --git a/docker-for-mac/osxfs.md b/docker-for-mac/osxfs.md
index ea51fcaa45..d0dc9e5a1b 100644
--- a/docker-for-mac/osxfs.md
+++ b/docker-for-mac/osxfs.md
@@ -20,16 +20,16 @@ user experience for bind mounting OS X file system trees into Docker
containers. To this end, `osxfs` features a number of unique
capabilities as well as differences from a classical Linux file system.
-- [Case sensitivity](#case-sensitivity)
-- [Access control](#access-control)
-- [Namespaces](#namespaces)
-- [Ownership](#ownership)
-- [File system events](#file-system-events)
-- [Mounts](#mounts)
-- [Symlinks](#symlinks)
-- [File types](#file-types)
-- [Extended attributes](#extended-attributes)
-- [Technology](#technology)
+- [Case sensitivity](osxfs.md#case-sensitivity)
+- [Access control](osxfs.md#access-control)
+- [Namespaces](osxfs.md#namespaces)
+- [Ownership](osxfs.md#ownership)
+- [File system events](osxfs.md#file-system-events)
+- [Mounts](osxfs.md#mounts)
+- [Symlinks](osxfs.md#symlinks)
+- [File types](osxfs.md#file-types)
+- [Extended attributes](osxfs.md#extended-attributes)
+- [Technology](osxfs.md#technology)
### Case sensitivity
@@ -44,7 +44,7 @@ case-sensitivity or reformat your OS root partition with HFS+ with
case-sensitivity. We do not recommend reformatting your root partition
as some Mac software dubiously relies on case-insensitivity to function.
-
+
### Access control
`osxfs`, and therefore Docker, can access only those file system
@@ -114,13 +114,13 @@ The following are **unsupported file system events**:
* Open
* Access
* Close events
-* Unmount events (see Mounts)
+* Unmount events (see Mounts)
Some events may be delivered multiple times. Events are not delivered for bind mounts from symlinks (notably `/tmp` will not deliver inotify events but
`/private/tmp` will). These limitations do not apply to events between
containers, only to those events originating in OS X.
-
+
### Mounts
The OS X mount structure is not visible in the shared volume, but volume
@@ -152,14 +152,3 @@ Extended attributes are not yet supported.
`osxfs` does not use OSXFUSE. `osxfs` does not run under, inside, or
between OS X userspace processes and the OS X kernel.
-
-
-
- Help improve the documentation
-
- Email us at feedback@docker.com -
--
-
-
-
diff --git a/docker-for-mac/release-notes.md b/docker-for-mac/release-notes.md
index c1827ed4e5..99e05d3da6 100644
--- a/docker-for-mac/release-notes.md
+++ b/docker-for-mac/release-notes.md
@@ -20,8 +20,8 @@ For system requirements, please see the Getting Started topic on [What to know b
Release notes for _stable_ and _beta_ releases are listed below. You can learn about both kinds of releases, and download stable and beta product installers at [Download Docker for Mac](index.md#download-docker-for-mac).
-* [Stable Release Notes](#stable-release-notes)
-* [Beta Release Notes](#beta-release-notes)
+* [Stable Release Notes](release-notes.md#stable-release-notes)
+* [Beta Release Notes](release-notes.md#beta-release-notes)
## Stable Release Notes
@@ -1145,14 +1145,3 @@ lead to `Docker.app` not starting on reboot
-
- 
Help improve the documentation
-
- Email us at feedback@docker.com -
--
-
-
-
diff --git a/docker-for-mac/troubleshoot.md b/docker-for-mac/troubleshoot.md
index e7a6e513e2..056ea69fad 100644
--- a/docker-for-mac/troubleshoot.md
+++ b/docker-for-mac/troubleshoot.md
@@ -105,7 +105,7 @@ You may get the following error when you try to start a container created with p
Error response from daemon: Unknown runtime specified default
-You can fix this by either [recreating](#recreate-your-containers) or [updating](#update-your-containers) your containers.
+You can fix this by either [recreating](troubleshoot.md#recreate-your-containers) or [updating](troubleshoot.md#update-your-containers) your containers.
If you get the error message shown above, we recommend recreating them.
@@ -242,7 +242,7 @@ environments, see [Docker for Mac vs. Docker Toolbox](docker-toolbox.md).
decide whether to shut the other process down, or to use a different port in
your docker app.
-See also [Known Issues](#known-issues) on this page, and the [FAQs](faqs.md) topic.
+See also [Known Issues](troubleshoot.md#known-issues) on this page, and the [FAQs](faqs.md) topic.
## Known issues
@@ -251,7 +251,7 @@ See also [Known Issues](#known-issues) on this page, and the [FAQs](faqs.md) top
timeout when you run `docker` commands that need access to external network
servers. The aforementioned releases include a workaround for this because
Docker for Mac does not yet support IPv6. See "IPv6 workaround to auto-filter DNS addresses" in
-[Workarounds for common problems](#workarounds-for-common-problems).
+[Workarounds for common problems](troubleshoot.md#workarounds-for-common-problems).
* You might encounter errors when using `docker-compose up` with Docker for Mac (`ValueError: Extra Data`). We've identified this is likely related to data and/or events being passed all at once rather than one by one, so sometimes the data comes back as 2+ objects concatenated and causes an error.
diff --git a/docker-for-windows/examples.md b/docker-for-windows/examples.md
index a6a3665130..ed6e29039b 100644
--- a/docker-for-windows/examples.md
+++ b/docker-for-windows/examples.md
@@ -26,13 +26,3 @@ For now, if you want get started experimenting with the Beta apps and Docker Com
See also [learn by example](/engine/tutorials/index.md) tutorials on building images, runnning containers, networking, managing data, and storing images on Docker Hub.
-
-
- Help improve the documentation
-
- Email us at feedback@docker.com -
--
-
-
-
diff --git a/docker-for-windows/faqs.md b/docker-for-windows/faqs.md
index e44dd4bc0a..ea930955c5 100644
--- a/docker-for-windows/faqs.md
+++ b/docker-for-windows/faqs.md
@@ -141,13 +141,3 @@ details on how to perform a clean uninstall of Toolbox on Windows, see [How to
uninstall Toolbox](/toolbox/toolbox_install_windows.md#how-to-uninstall-toolbox)
in the Toolbox Windows topics.
-
-
- Help improve the documentation
-
- Email us at feedback@docker.com -
--
-
-
-
diff --git a/docker-for-windows/index.md b/docker-for-windows/index.md
index d3d6bd2d7f..c074957781 100644
--- a/docker-for-windows/index.md
+++ b/docker-for-windows/index.md
@@ -42,18 +42,18 @@ If you have not already done so, please install Docker for Windows. You can down
-
- Help improve the documentation
-
- Email us at feedback@docker.com -
-- Download checksum: InstallDocker.msi SHA256 + Download checksum: InstallDocker.msi SHA256
- Download checksum: InstallDocker.msi SHA256 + Download checksum: InstallDocker.msi SHA256
-
-
-
-
diff --git a/docker-for-windows/opensource.md b/docker-for-windows/opensource.md
index b660fc376e..b44d8074dd 100644
--- a/docker-for-windows/opensource.md
+++ b/docker-for-windows/opensource.md
@@ -16,13 +16,3 @@ Docker Desktop Editions are built using open source software software. For detai
Docker Desktop Editions distribute some components that are licensed under the GNU General Public License. You can download the source for these components [here](https://download.docker.com/opensource/License.tar.gz).
-
-
- Help improve the documentation
-
- Email us at feedback@docker.com -
--
-
-
-
diff --git a/docker-for-windows/release-notes.md b/docker-for-windows/release-notes.md
index d41c850571..3b0d850119 100644
--- a/docker-for-windows/release-notes.md
+++ b/docker-for-windows/release-notes.md
@@ -20,9 +20,9 @@ For system requirements, please see the Getting Started topic on [What to know b
Release notes for _stable_ and _beta_ releases are listed below. You can learn about both kinds of releases, and download stable and beta product installers at [Download Docker for Windows](index.md#download-docker-for-windows).
-* [Stable Release Notes](#stable-release-notes)
-* [Beta Release Notes](#beta-release-notes)
-* [Alpha Release Notes](#alpha-release-notes)
+* [Stable Release Notes](release-notes.md#stable-release-notes)
+* [Beta Release Notes](release-notes.md#beta-release-notes)
+* [Alpha Release Notes](release-notes.md#alpha-release-notes)
## Stable Release Notes
diff --git a/docker-for-windows/troubleshoot.md b/docker-for-windows/troubleshoot.md
index f714e2f5a6..58b356596f 100644
--- a/docker-for-windows/troubleshoot.md
+++ b/docker-for-windows/troubleshoot.md
@@ -106,7 +106,7 @@ You may get the following error when you try to start a container created with p
Error response from daemon: Unknown runtime specified default
-You can fix this by either [recreating](#recreate-your-containers) or [updating](#update-your-containers) your containers.
+You can fix this by either [recreating](troubleshoot.md#recreate-your-containers) or [updating](troubleshoot.md#update-your-containers) your containers.
If you get the error message shown above, we recommend recreating them.
@@ -286,14 +286,3 @@ relates to Docker: [Docker fails to start on Windows
For a temporary workaround, uninstall the Comodo Firewall, or explore other
workarounds suggested on the forum.
-
-
-
- Help improve the documentation
-
- Email us at feedback@docker.com -
--
-
-
-
diff --git a/docker-hub/bitbucket.md b/docker-hub/bitbucket.md
index 8240458583..b192c0c4dc 100644
--- a/docker-hub/bitbucket.md
+++ b/docker-hub/bitbucket.md
@@ -13,7 +13,7 @@ title: Automated Builds with Bitbucket
# Automated Builds with Bitbucket
If you've previously linked Docker Hub to your Bitbucket account,
-you'll be able to skip to [Creating an Automated Build](#creating-an-automated-build).
+you'll be able to skip to [Creating an Automated Build](bitbucket.md#creating-an-automated-build).
## Linking to your Bitbucket account
diff --git a/docker-hub/github.md b/docker-hub/github.md
index 48f7be0aa7..e4801f4254 100644
--- a/docker-hub/github.md
+++ b/docker-hub/github.md
@@ -13,7 +13,7 @@ title: Automated Builds from GitHub
# Automated Builds from GitHub
If you've previously linked Docker Hub to your GitHub account,
-you'll be able to skip to [Creating an Automated Build](#creating-an-automated-build).
+you'll be able to skip to [Creating an Automated Build](github.md#creating-an-automated-build).
## Linking Docker Hub to a GitHub account
@@ -62,7 +62,7 @@ You will be able to review and revoke Docker Hub's access by visiting the
If you selected to link your GitHub account with only a "Limited Access" link, then
after creating your automated build, you will need to either manually trigger a
Docker Hub build using the "Start a Build" button, or add the GitHub webhook
-manually, as described in [GitHub Service Hooks](#github-service-hooks).
+manually, as described in [GitHub Service Hooks](github.md#github-service-hooks).
## Changing the GitHub user link
diff --git a/docker-trusted-registry/configure/config-security.md b/docker-trusted-registry/configure/config-security.md
index 9e52c17e3c..f4c7c753c5 100644
--- a/docker-trusted-registry/configure/config-security.md
+++ b/docker-trusted-registry/configure/config-security.md
@@ -23,18 +23,18 @@ SSL Certificate (as a standard x509 key pair).
In order to run, the Trusted Registry requires encrypted communications through HTTPS/SSL between (a) the Trusted Registry and your Docker Engine(s), and (b) between your web browser and the Trusted Registry admin server. There are a few options for setting this up:
1. You can use the self-signed certificate Docker Trusted Registry generates by default.
-2. You can generate your own certificates using a public service or your enterprise's infrastructure. See the [Generating SSL certificates](#generating-ssl-certificates) section for the options available.
+2. You can generate your own certificates using a public service or your enterprise's infrastructure. See the [Generating SSL certificates](config-security.md#generating-ssl-certificates) section for the options available.
If you are generating your own certificates, you can install them by following the instructions for
-[Adding your own registry certificates to Docker Trusted Registry](#adding-your-own-registry-certificates-to-dtr).
+[Adding your own registry certificates to Docker Trusted Registry](config-security.md#adding-your-own-registry-certificates-to-dtr).
However, if you choose to use the Trusted Registry-generated certificates, or
the certificates you generate yourself are not trusted by your client Docker
hosts, you will need to do one of the following:
-* [Install](#installing-registry-certificates-on-client-docker-daemons) a registry certificate on all of your client Docker daemons, or
+* [Install](config-security.md#installing-registry-certificates-on-client-docker-daemons) a registry certificate on all of your client Docker daemons, or
-* Set your [client Docker daemons](#if-you-can-t-install-the-certificates) to run with an unconfirmed connection to the registry.
+* Set your [client Docker daemons](config-security.md#if-you-can-t-install-the-certificates) to run with an unconfirmed connection to the registry.
### Generate SSL certificates
diff --git a/docker-trusted-registry/release-notes/prior-release-notes.md b/docker-trusted-registry/release-notes/prior-release-notes.md
index 50b509246c..5e9e4d8b10 100644
--- a/docker-trusted-registry/release-notes/prior-release-notes.md
+++ b/docker-trusted-registry/release-notes/prior-release-notes.md
@@ -63,7 +63,7 @@ Release notes contain the following sections:
**Additional storage backend**
-This release introduces using Openstack Swift as a storage backend. Refer to the [configuration documentation](../configure/config-storage.md) for details on the Swift driver.
+This release introduces using Openstack Swift as a storage backend. Refer to the [configuration documentation](../configure/config-storage.md) for details on the Swift driver.
**Fixed or updated with this release**
This release addresses the following issues in Docker Trusted Registry 1.4.1.
@@ -292,7 +292,7 @@ Trusted Registry. See below for specifics.
* New, more granular, [roles for users](../user-management/index.md). Docker Trusted Registry users can now be assigned different levels of access
(admin, r/w, r/o) to the repositories. **Important:** Existing Docker Trusted
-Registry users should make sure to see the note [below](#dhe-1-0-upgrade-warning) regarding migrating users before upgrading.
+Registry users should make sure to see the note [below](prior-release-notes.md#dhe-1-0-upgrade-warning) regarding migrating users before upgrading.
* A new storage status indicator for storage space. The dashboard now shows used and available storage space for supported storage drivers.
* A new diagnostics tool gathers and bundles Docker Trusted Registry logs, system information, container
information, and other configuration settings for use by Docker support or as a
diff --git a/engine/admin/runmetrics.md b/engine/admin/runmetrics.md
index 09d77f0300..a5e466bd14 100644
--- a/engine/admin/runmetrics.md
+++ b/engine/admin/runmetrics.md
@@ -314,7 +314,7 @@ container, we need to:
- Create a symlink from `/var/run/netns/
-
- Help improve the documentation
-
- Email us at feedback@docker.com -
-{
- "trust_dir" : "~/.docker/trust",
- "remote_server": {
+ "trust_dir" : "~/.docker/trust",
+ "remote_server": {
"url": "https://my-notary-server.my-private-registry.com",
"root-ca": "./fixtures/root-ca.crt",
"tls_client_cert": "./fixtures/secure.example.com.crt",
"tls_client_key": "./fixtures/secure.example.com.crt"
}
- "trust_pinning": {
+ "trust_pinning": {
"certs": {
"docker.com/notary": ["49cf5c6404a35fa41d5a5aa2ce539dfee0d7a2176d0da488914a38603b1f4292"]
}
diff --git a/notary/reference/server-config.md b/notary/reference/server-config.md
index 1abedac726..0565d682de 100644
--- a/notary/reference/server-config.md
+++ b/notary/reference/server-config.md
@@ -26,12 +26,12 @@ Here is a full server configuration file example; please click on the top level
learn more about the configuration section corresponding to that key:
{
- "server": {
+ "server": {
"http_addr": ":4443",
"tls_key_file": "./fixtures/notary-server.key",
"tls_cert_file": "./fixtures/notary-server.crt"
},
- "trust_service": {
+ "trust_service": {
"type": "remote",
"hostname": "notarysigner",
"port": "7899",
@@ -40,11 +40,11 @@ learn more about the configuration section corresponding to that key:
"tls_client_cert": "./fixtures/notary-server.crt",
"tls_client_key": "./fixtures/notary-server.key"
},
- "storage": {
+ "storage": {
"backend": "mysql",
"db_url": "user:pass@tcp(notarymysql:3306)/databasename?parseTime=true"
},
- "auth": {
+ "auth": {
"type": "token",
"options": {
"realm": "https://auth.docker.io/token",
@@ -62,13 +62,13 @@ learn more about the configuration section corresponding to that key:
"release_stage": "production"
}
},
- "caching": {
+ "caching": {
"max_age": {
"current_metadata": 300,
"consistent_metadata": 31536000,
}
},
- "repositories": {
+ "repositories": {
"gun_prefixes": ["docker.io/", "my-own-registry.com/"]
}
}
diff --git a/notary/reference/signer-config.md b/notary/reference/signer-config.md
index 3d2975308d..85509a40b5 100644
--- a/notary/reference/signer-config.md
+++ b/notary/reference/signer-config.md
@@ -16,7 +16,7 @@ want to specify custom options.
## Overview
-Notary signer [requires environment variables](#environment-variables-required-if-using-mysql)
+Notary signer [requires environment variables](signer-config.md#environment-variables-required-if-using-mysql)
to encrypt private keys at rest. It also requires a configuration file, the path to which is
specified on the command line using the `-config` flag.
@@ -24,7 +24,7 @@ Here is a full signer configuration file example; please click on the top level
learn more about the configuration section corresponding to that key:
{
- "server": {
+ "server": {
"http_addr": ":4444",
"grpc_addr": ":7899",
"tls_cert_file": "./fixtures/notary-signer.crt",
@@ -34,7 +34,7 @@ learn more about the configuration section corresponding to that key:
"logging": {
"level": 2
},
- "storage": {
+ "storage": {
"backend": "mysql",
"db_url": "user:pass@tcp(notarymysql:3306)/databasename?parseTime=true",
"default_alias": "passwordalias1"
@@ -173,7 +173,7 @@ Example:
private keys will be encrypted using this password, which
must also be provided as the environment variable
NOTARY_SIGNER_<DEFAULT_ALIAS_VALUE>.
- Please see the environment variable
+ Please see the environment variable
section for more information.
diff --git a/notary/running_a_service.md b/notary/running_a_service.md
index 8b09e056a3..31873a79fb 100644
--- a/notary/running_a_service.md
+++ b/notary/running_a_service.md
@@ -63,7 +63,7 @@ the IP address of your Docker host.
Both the Notary server and the Notary signer take
[JSON configuration files](reference/index.md). Pre-built images, such as
-the [development images above](#run-a-service-for-testing-or-development)
+the [development images above](running_a_service.md#run-a-service-for-testing-or-development)
provide these configuration files for you with some sane defaults.
However, for running in production, or if you just want to change those defaults
diff --git a/opensource/FAQ.md b/opensource/FAQ.md
index a4db207d1a..4baeb4c8fb 100644
--- a/opensource/FAQ.md
+++ b/opensource/FAQ.md
@@ -14,12 +14,12 @@ title: FAQ for contributors
This section contains some frequently asked questions and tips for
troubleshooting problems in your code contribution.
-- [How do I set my signature?](#how-do-i-set-my-signature:cb7f612e17aad7eb26c06709ef92a867)
-- [How do I track changes from the docker repo upstream?](#how-do-i-track-changes-from-the-docker-repo-upstream:cb7f612e17aad7eb26c06709ef92a867)
-- [How do I format my Go code?](#how-do-i-format-my-go-code:cb7f612e17aad7eb26c06709ef92a867)
-- [What is the pre-pull request checklist?](#what-is-the-pre-pull-request-checklist:cb7f612e17aad7eb26c06709ef92a867)
-- [How should I comment my code?](#how-should-i-comment-my-code:cb7f612e17aad7eb26c06709ef92a867)
-- [How do I rebase my feature branch?](#how-do-i-rebase-my-feature-branch:cb7f612e17aad7eb26c06709ef92a867)
+- [How do I set my signature?](FAQ.md#how-do-i-set-my-signature:cb7f612e17aad7eb26c06709ef92a867)
+- [How do I track changes from the docker repo upstream?](FAQ.md#how-do-i-track-changes-from-the-docker-repo-upstream:cb7f612e17aad7eb26c06709ef92a867)
+- [How do I format my Go code?](FAQ.md#how-do-i-format-my-go-code:cb7f612e17aad7eb26c06709ef92a867)
+- [What is the pre-pull request checklist?](FAQ.md#what-is-the-pre-pull-request-checklist:cb7f612e17aad7eb26c06709ef92a867)
+- [How should I comment my code?](FAQ.md#how-should-i-comment-my-code:cb7f612e17aad7eb26c06709ef92a867)
+- [How do I rebase my feature branch?](FAQ.md#how-do-i-rebase-my-feature-branch:cb7f612e17aad7eb26c06709ef92a867)
## How do I set my signature {#how-do-i-set-my-signature}
diff --git a/opensource/code.md b/opensource/code.md
index 1920f77b60..82ccb574f3 100644
--- a/opensource/code.md
+++ b/opensource/code.md
@@ -78,7 +78,7 @@ pull request.
We have also have checklist that describes [what each pull request
- needs](#what-is-the-pre-pull-request-checklist).
+ needs](code.md#what-is-the-pre-pull-request-checklist).
7. **DEPRECATED:** Please use [log](#log) instead.
+> **DEPRECATED:** Please use [log](configuration.md#log) instead.
loglevel: debug
@@ -1251,7 +1251,7 @@ Declare parameters for constructing the redis connections. Registry instances
may use the Redis instance for several applications. The current purpose is
caching information about immutable blobs. Most of the options below control
how the registry connects to redis. You can control the pool's behavior
-with the [pool](#pool) subsection.
+with the [pool](configuration.md#pool) subsection.
It's advisable to configure Redis itself with the **allkeys-lru** eviction policy
as the registry does not set an expire value on keys.
diff --git a/registry/deploying.md b/registry/deploying.md
index 1ac2509346..1aa42aa0ab 100644
--- a/registry/deploying.md
+++ b/registry/deploying.md
@@ -154,7 +154,7 @@ Except for registries running on secure local networks, registries should always
The simplest way to achieve access restriction is through basic authentication (this is very similar to other web servers' basic authentication mechanism).
-> **Warning**: You **cannot** use authentication with an insecure registry. You have to [configure TLS first](#running-a-domain-registry) for this to work.
+> **Warning**: You **cannot** use authentication with an insecure registry. You have to [configure TLS first](deploying.md#running-a-domain-registry) for this to work.
First create a password file with one entry for the user "testuser", with password "testpassword":
diff --git a/registry/glossary.md b/registry/glossary.md
index 00be147fdb..61c8d1dc3f 100644
--- a/registry/glossary.md
+++ b/registry/glossary.md
@@ -11,7 +11,7 @@ This page contains definitions for distribution related terms.