mirror of https://github.com/docker/docs.git
Merge pull request #1088 from sanscontext/fix-cloud-links
url fixes for #1068
This commit is contained in:
commit
ae80059160
|
@ -8,7 +8,7 @@ title: Publish and expose service or container ports
|
||||||
|
|
||||||
In Docker Cloud you can **publish** or **expose** ports in services and
|
In Docker Cloud you can **publish** or **expose** ports in services and
|
||||||
containers, just like you can in Docker Engine (as documented
|
containers, just like you can in Docker Engine (as documented
|
||||||
[here](/reference/run/#expose-incoming-ports) ).
|
[here](/engine/reference/run/#expose-incoming-ports) ).
|
||||||
|
|
||||||
* **Exposed ports** are ports that a container or service is using either to
|
* **Exposed ports** are ports that a container or service is using either to
|
||||||
provide a service, or listen on. By default, exposed ports in Docker Cloud are
|
provide a service, or listen on. By default, exposed ports in Docker Cloud are
|
||||||
|
|
|
@ -16,7 +16,7 @@ redeployment, or shared with other services.
|
||||||
## Add a data volume to a service
|
## Add a data volume to a service
|
||||||
|
|
||||||
Data volumes can be either specified in the image's `Dockerfile` using the
|
Data volumes can be either specified in the image's `Dockerfile` using the
|
||||||
[VOLUME instruction](/reference/builder/#volume), or when
|
[VOLUME instruction](/engine/reference/builder/#volume), or when
|
||||||
creating a service.
|
creating a service.
|
||||||
|
|
||||||
To define a data volume in a service, specify the **container path** where it
|
To define a data volume in a service, specify the **container path** where it
|
||||||
|
@ -66,4 +66,4 @@ You might find it helpful to download or back up the data from volumes that are
|
||||||
|
|
||||||
```
|
```
|
||||||
$ scp -r -P 2222 root@downloader-1.uuid.cont.dockerapp.io:/var/lib/mysql .
|
$ scp -r -P 2222 root@downloader-1.uuid.cont.dockerapp.io:/var/lib/mysql .
|
||||||
```
|
```
|
||||||
|
|
|
@ -15,7 +15,7 @@ Images pushed to Docker Hub automatically appear for you in the **Launch new
|
||||||
service** wizard.
|
service** wizard.
|
||||||
|
|
||||||
> **Note**: You must use Docker Engine 1.6 or later to push to Docker Hub.
|
> **Note**: You must use Docker Engine 1.6 or later to push to Docker Hub.
|
||||||
Follow the <a href="/installation/" target="_blank">official installation instructions</a> depending on your system.
|
Follow the <a href="/engine/installation/" target="_blank">official installation instructions</a> depending on your system.
|
||||||
|
|
||||||
1. In a terminal window, set the environment variable **DOCKER_ID_USER** as *your username* in Docker Cloud.
|
1. In a terminal window, set the environment variable **DOCKER_ID_USER** as *your username* in Docker Cloud.
|
||||||
|
|
||||||
|
@ -55,4 +55,4 @@ Follow the <a href="/installation/" target="_blank">official installation instr
|
||||||
> Cloud, you might need to select the organization name or your username from
|
> Cloud, you might need to select the organization name or your username from
|
||||||
> the dropdown menu see other repositories.
|
> the dropdown menu see other repositories.
|
||||||
|
|
||||||

|

|
||||||
|
|
|
@ -16,7 +16,7 @@ This tutorial assumes that you have:
|
||||||
|
|
||||||
- a free <a href="https://hub.docker.com/" target="_blank">Docker ID account</a>.
|
- a free <a href="https://hub.docker.com/" target="_blank">Docker ID account</a>.
|
||||||
- at least one node running. If you don't have any nodes set up in Docker Cloud yet, [start here](../../getting-started/your_first_node.md) to set these up.
|
- at least one node running. If you don't have any nodes set up in Docker Cloud yet, [start here](../../getting-started/your_first_node.md) to set these up.
|
||||||
- (optional) Docker Engine installed - see the installation guides for <a href="/installation/#installation" target="_blank">macOS, Windows and Linux</a>.
|
- (optional) Docker Engine installed - see the installation guides for <a href="/engine/installation/" target="_blank">macOS, Windows and Linux</a>.
|
||||||
|
|
||||||
Let's get started!
|
Let's get started!
|
||||||
|
|
||||||
|
|
|
@ -15,7 +15,7 @@ workflow automation throughout the development pipeline.
|
||||||
|
|
||||||
Log in to Docker Hub and Docker Cloud using [your free Docker ID](accounts.md).
|
Log in to Docker Hub and Docker Cloud using [your free Docker ID](accounts.md).
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
Docker Hub provides the following major features:
|
Docker Hub provides the following major features:
|
||||||
|
|
||||||
|
@ -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](/userguide/dockerimages/).
|
[Docker userguide](/engine/userguide/dockerimages/).
|
||||||
|
|
||||||
### Use Official Repositories
|
### Use Official Repositories
|
||||||
|
|
||||||
|
@ -88,5 +88,5 @@ or you can create private repositories with limited access you control.
|
||||||
|
|
||||||
### Docker commands and Docker Hub
|
### Docker commands and Docker Hub
|
||||||
|
|
||||||
Docker itself provides access to Docker Hub services via the [`docker search`](/reference/commandline/search),
|
Docker itself provides access to Docker Hub services via the [`docker search`](/engine/reference/commandline/search),
|
||||||
[`pull`](/reference/commandline/pull), [`login`](/reference/commandline/login), and [`push`](/reference/commandline/push) commands.
|
[`pull`](/engine/reference/commandline/pull), [`login`](/engine/reference/commandline/login), and [`push`](/engine/reference/commandline/push) commands.
|
||||||
|
|
|
@ -17,7 +17,7 @@ designed to:
|
||||||
stores, and other services, similar to what a Platform-as-a-Service (PAAS)
|
stores, and other services, similar to what a Platform-as-a-Service (PAAS)
|
||||||
would offer.
|
would offer.
|
||||||
|
|
||||||
* Exemplify [`Dockerfile` best practices](/articles/dockerfile_best-practices)
|
* Exemplify [`Dockerfile` best practices](/engine/userguide/eng-image/dockerfile_best-practices/)
|
||||||
and provide clear documentation to serve as a reference for other `Dockerfile`
|
and provide clear documentation to serve as a reference for other `Dockerfile`
|
||||||
authors.
|
authors.
|
||||||
|
|
||||||
|
@ -119,4 +119,4 @@ Repositories team becomes responsible for publishing the images and
|
||||||
documentation on Docker Hub. Updates to the Official Repository follow the same
|
documentation on Docker Hub. Updates to the Official Repository follow the same
|
||||||
pull request process, though with less review. The Official Repositories team
|
pull request process, though with less review. The Official Repositories team
|
||||||
ultimately acts as a gatekeeper for all changes, which helps mitigate the risk
|
ultimately acts as a gatekeeper for all changes, which helps mitigate the risk
|
||||||
of quality and security issues from being introduced.
|
of quality and security issues from being introduced.
|
||||||
|
|
|
@ -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](/userguide/dockerimages) for a detailed description.
|
See [Working with Docker images](/engine/userguide/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.
|
||||||
|
|
||||||
|
@ -139,8 +139,7 @@ want to keep private, either to your own account or within an organization or
|
||||||
team.
|
team.
|
||||||
|
|
||||||
To work with a private repository on [Docker Hub](https://hub.docker.com), you
|
To work with a private repository on [Docker Hub](https://hub.docker.com), you
|
||||||
will need to add one via the [Add
|
will need to add one using the [Add Repository](https://hub.docker.com/add/repository/) button. You get one private
|
||||||
Repository](https://hub.docker.com/add/repository/) button. You get one private
|
|
||||||
repository for free with your Docker Hub user account (not usable for
|
repository for free with your Docker Hub user account (not usable for
|
||||||
organizations you're a member of). If you need more accounts you can upgrade
|
organizations you're a member of). If you need more accounts you can upgrade
|
||||||
your [Docker Hub](https://hub.docker.com/account/billing-plans/) plan.
|
your [Docker Hub](https://hub.docker.com/account/billing-plans/) plan.
|
||||||
|
@ -258,4 +257,4 @@ The following parameters are recognized in callback data:
|
||||||
"description": "387 tests PASSED",
|
"description": "387 tests PASSED",
|
||||||
"context": "Continuous integration by Acme CI",
|
"context": "Continuous integration by Acme CI",
|
||||||
"target_url": "http://ci.acme.com/results/afd339c1c3d27"
|
"target_url": "http://ci.acme.com/results/afd339c1c3d27"
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue