mirror of https://github.com/docker/docs.git
docker-hub: use relative markdown links
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
parent
087e391397
commit
cef68d3fa5
|
@ -86,7 +86,7 @@ In the following example, we define a build hook that uses `docker build` argume
|
||||||
docker build --build-arg CUSTOM=$VAR -f $DOCKERFILE_PATH -t $IMAGE_NAME .
|
docker build --build-arg CUSTOM=$VAR -f $DOCKERFILE_PATH -t $IMAGE_NAME .
|
||||||
```
|
```
|
||||||
|
|
||||||
> **Caution**: A `hooks/build` file overrides the basic [docker build](/engine/reference/commandline/build.md) command
|
> **Caution**: A `hooks/build` file overrides the basic [docker build](/engine/reference/commandline/build/) command
|
||||||
used by the builder, so you must include a similar build command in the hook or
|
used by the builder, so you must include a similar build command in the hook or
|
||||||
the automated build fails.
|
the automated build fails.
|
||||||
|
|
||||||
|
|
|
@ -36,9 +36,6 @@ image. Automated tests do not push images to the registry on their own. [Learn m
|
||||||
|
|
||||||
## Configure automated build settings
|
## Configure automated build settings
|
||||||
|
|
||||||
> **Note**: Automated builds created with the old Docker Hub are
|
|
||||||
now Classic Automated Builds. [Learn more](classic.md)
|
|
||||||
|
|
||||||
You can configure repositories in Docker Hub so that they automatically
|
You can configure repositories in Docker Hub so that they automatically
|
||||||
build an image each time you push new code to your source provider. If you have
|
build an image each time you push new code to your source provider. If you have
|
||||||
[automated tests](automated-testing.md) configured, the new image is only pushed
|
[automated tests](automated-testing.md) configured, the new image is only pushed
|
||||||
|
@ -85,7 +82,7 @@ You might redirected to the settings page to [link](link-source.md) the code rep
|
||||||
|
|
||||||
8. For each branch or tag, enable or disable the **Build Caching** toggle.
|
8. For each branch or tag, enable or disable the **Build Caching** toggle.
|
||||||
|
|
||||||
[Build caching](/develop/develop-images/dockerfile_best-practices.md#leverage-build-cache) can save time if you are building a large image frequently or have
|
[Build caching](../../develop/develop-images/dockerfile_best-practices.md#leverage-build-cache) can save time if you are building a large image frequently or have
|
||||||
many dependencies. You might want to leave build caching disabled to
|
many dependencies. You might want to leave build caching disabled to
|
||||||
make sure all of your dependencies are resolved at build time, or if
|
make sure all of your dependencies are resolved at build time, or if
|
||||||
you have a large layer that is quicker to build locally.
|
you have a large layer that is quicker to build locally.
|
||||||
|
|
|
@ -14,7 +14,7 @@ repositories. You can configure this link for user accounts or
|
||||||
organizations.
|
organizations.
|
||||||
|
|
||||||
|
|
||||||
> **Note**: If you are linking a source code provider to create autobuilds for a team, follow the instructions to [create a service account](/docker-hub/builds.md#service-users-for-team-autobuilds) for the team before linking the account as described below.
|
> **Note**: If you are linking a source code provider to create autobuilds for a team, follow the instructions to [create a service account](index.md#service-users-for-team-autobuilds) for the team before linking the account as described below.
|
||||||
|
|
||||||
## Link to a GitHub user account
|
## Link to a GitHub user account
|
||||||
|
|
||||||
|
|
|
@ -80,17 +80,17 @@ redirect_from:
|
||||||
[Docker Hub](https://hub.docker.com) is a service provided by Docker for
|
[Docker Hub](https://hub.docker.com) is a service provided by Docker for
|
||||||
finding and sharing container images with your team. It provides the following
|
finding and sharing container images with your team. It provides the following
|
||||||
major features:
|
major features:
|
||||||
* [Repositories](/docker-hub/repos.md): Push and pull container images.
|
* [Repositories](repos.md): Push and pull container images.
|
||||||
* [Teams & Organizations](/docker-hub/orgs.md): Manage access to private
|
* [Teams & Organizations](orgs.md): Manage access to private
|
||||||
repositories of container images.
|
repositories of container images.
|
||||||
* [Official Images](/docker-hub/official_images.md): Pull and use high-quality
|
* [Official Images](official_images.md): Pull and use high-quality
|
||||||
container images provided by Docker.
|
container images provided by Docker.
|
||||||
* [Publisher Images](/docker-hub/publish/customer_faq.md): Pull and use high-
|
* [Publisher Images](publish/customer_faq.md): Pull and use high-
|
||||||
quality container images provided by external vendors. Certified images also
|
quality container images provided by external vendors. Certified images also
|
||||||
include support and guarantee compatibility with Docker Enterprise.
|
include support and guarantee compatibility with Docker Enterprise.
|
||||||
* [Builds](/docker-hub/builds.md): Automatically build container images from
|
* [Builds](builds/index.md): Automatically build container images from
|
||||||
GitHub and Bitbucket and push them to Docker Hub.
|
GitHub and Bitbucket and push them to Docker Hub.
|
||||||
* [Webhooks](/docker-hub/webhooks.md): Trigger actions after a successful push
|
* [Webhooks](webhooks.md): Trigger actions after a successful push
|
||||||
to a repository to integrate Docker Hub with other services.
|
to a repository to integrate Docker Hub with other services.
|
||||||
|
|
||||||
|
|
||||||
|
|
|
@ -29,7 +29,7 @@ Docker Hub.
|
||||||
You've created an organization. You'll see you have a team, the **owners** team
|
You've created an organization. You'll see you have a team, the **owners** team
|
||||||
with a single member (you!).
|
with a single member (you!).
|
||||||
|
|
||||||
In some situations, you can also create an organization by [converting a user account](/convert-account.md).
|
In some situations, you can also create an organization by [converting a user account](convert-account.md).
|
||||||
|
|
||||||
#### The owners team
|
#### The owners team
|
||||||
|
|
||||||
|
|
|
@ -12,7 +12,7 @@ Content that qualifies as **Docker Certified** must conform to best practices an
|
||||||
|
|
||||||
Docker Hub lets you publish certified images as well as plugins for logging, volumes, and networks. You must certify your own _images and logging plugins_ with the `inspect` tools as explained in these docs. Currently, Docker Hub certifies your volume and networking plugins for you upon submission.
|
Docker Hub lets you publish certified images as well as plugins for logging, volumes, and networks. You must certify your own _images and logging plugins_ with the `inspect` tools as explained in these docs. Currently, Docker Hub certifies your volume and networking plugins for you upon submission.
|
||||||
|
|
||||||
This page explains how publishers can successfully test their **Docker images**. Also available: [Certify your Docker logging plugins](certify-plugins-logging).
|
This page explains how publishers can successfully test their **Docker images**. Also available: [Certify your Docker logging plugins](certify-plugins-logging.md).
|
||||||
|
|
||||||
> Content that requires a non-certified infrastructure environment cannot be published as certified.
|
> Content that requires a non-certified infrastructure environment cannot be published as certified.
|
||||||
|
|
||||||
|
|
|
@ -21,8 +21,8 @@ To create a repository, sign into Docker Hub, click on **Repositories** then
|
||||||
When creating a new repository:
|
When creating a new repository:
|
||||||
|
|
||||||
* You can choose to put it in your Docker ID
|
* You can choose to put it in your Docker ID
|
||||||
namespace, or in any [organization](/docker-hub/orgs.md) where you are an
|
namespace, or in any [organization](orgs.md) where you are an
|
||||||
[_owner_](/orgs/#the-owners-team).
|
[_owner_](orgs.md#the-owners-team).
|
||||||
|
|
||||||
* The repository name needs to be unique in that namespace, can be two
|
* The repository name needs to be unique in that namespace, can be two
|
||||||
to 255 characters, and can only contain lowercase letters, numbers or `-` and
|
to 255 characters, and can only contain lowercase letters, numbers or `-` and
|
||||||
|
@ -112,7 +112,7 @@ changing its status from private to public.
|
||||||
|
|
||||||
You can also assign more granular collaborator rights ("Read", "Write", or
|
You can also assign more granular collaborator rights ("Read", "Write", or
|
||||||
"Admin") on Docker Hub by using organizations and teams. For more information
|
"Admin") on Docker Hub by using organizations and teams. For more information
|
||||||
see the [organizations documentation](/docker-hub/orgs.md).
|
see the [organizations documentation](orgs.md).
|
||||||
|
|
||||||
|
|
||||||
## Viewing repository tags
|
## Viewing repository tags
|
||||||
|
@ -156,7 +156,7 @@ There you can see two example results: `centos` and `ansible/centos7-ansible`.
|
||||||
The second result shows that it comes from the public repository of a user,
|
The second result shows that it comes from the public repository of a user,
|
||||||
named `ansible/`, while the first result, `centos`, doesn't explicitly list a
|
named `ansible/`, while the first result, `centos`, doesn't explicitly list a
|
||||||
repository which means that it comes from the top-level namespace for
|
repository which means that it comes from the top-level namespace for
|
||||||
[official images](/docker-hub/official_images.md). The `/` character separates
|
[official images](official_images.md). The `/` character separates
|
||||||
a user's repository from the image name.
|
a user's repository from the image name.
|
||||||
|
|
||||||
Once you've found the image you want, you can download it with `docker pull <imagename>`:
|
Once you've found the image you want, you can download it with `docker pull <imagename>`:
|
||||||
|
|
Loading…
Reference in New Issue