docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Revert "Merge pull request #437 from gdevillele/fix_keywords_format" 

This reverts commit 13ddc1350e, reversing
changes made to 7a11f05943.
This commit is contained in:
Misty Stanley-Jones 2016-11-04 13:33:29 -07:00
parent 2424da414f
commit 1a193d749b
439 changed files with 1517 additions and 941 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_data/staging-container/Dockerfile
View File

@ -4,4 +4,4 @@ VOLUME /usr/src/app
EXPOSE 4000
CMD jekyll clean && jekyll serve -d /_site --watch -H 0.0.0.0 -P 4000
CMD jekyll serve -d /_site --watch -H 0.0.0.0 -P 4000

4
_data/toc.yaml
View File

@ -1075,8 +1075,6 @@ toc:
title: Amazon Web Services
- path: /machine/drivers/digital-ocean/
title: Digital Ocean
- path: /machine/drivers/exoscale/
title: Exoscale
- path: /machine/drivers/generic/
title: Generic
- path: /machine/drivers/gce/
@ -1099,6 +1097,8 @@ toc:
title: VMware vCloud Air
- path: /machine/drivers/vsphere/
title: VMware vSphere
- path: /machine/drivers/exoscale/
title: exoscale
- path: /machine/completion/
title: Command-line Completion
- sectiontitle: Docker Store

5
compose/bundles.md
View File

@ -2,7 +2,8 @@
advisory: experimental
description: Description of Docker and Compose's experimental support for application
bundles
keywords: documentation, docs, docker, compose, bundles, stacks
keywords:
- documentation, docs, docker, compose, bundles, stacks
menu:
main:
parent: workw_compose
@ -205,4 +206,4 @@ A service has the following fields:
</dl>
> **Note:** Some configuration options are not yet supported in the DAB format,
> including volume mounts.
> including volume mounts.

5
compose/completion.md
View File

@ -1,6 +1,7 @@
---
description: Compose CLI reference
keywords: fig, composition, compose, docker, orchestration, cli, reference
keywords:
- fig, composition, compose, docker, orchestration, cli, reference
menu:
main:
parent: workw_compose
@ -64,4 +65,4 @@ Enjoy working with Compose faster and with less typos!
- [Get started with Rails](rails.md)
- [Get started with WordPress](wordpress.md)
- [Command line reference](./reference/index.md)
- [Compose file reference](compose-file.md)
- [Compose file reference](compose-file.md)

5
compose/compose-file.md
View File

@ -2,7 +2,8 @@
aliases:
- /compose/yml
description: Compose file reference
keywords: fig, composition, compose, docker
keywords:
- fig, composition, compose, docker
menu:
main:
parent: workw_compose
@ -1168,4 +1169,4 @@ If you forget and use a single dollar sign (`$`), Compose interprets the value a
- [Get started with Django](django.md)
- [Get started with Rails](rails.md)
- [Get started with WordPress](wordpress.md)
- [Command line reference](./reference/index.md)
- [Command line reference](./reference/index.md)

5
compose/django.md
View File

@ -1,6 +1,7 @@
---
description: Getting started with Docker Compose and Django
keywords: documentation, docs, docker, compose, orchestration, containers
keywords:
- documentation, docs, docker, compose, orchestration, containers
menu:
main:
parent: workw_compose
@ -189,4 +190,4 @@ In this section, you set up the database connection for Django.
- [Get started with Rails](rails.md)
- [Get started with WordPress](wordpress.md)
- [Command line reference](./reference/index.md)
- [Compose file reference](compose-file.md)
- [Compose file reference](compose-file.md)

5
compose/env-file.md
View File

@ -1,6 +1,7 @@
---
description: Declaring default environment variables in file
keywords: fig, composition, compose, docker, orchestration, environment, env file
keywords:
- fig, composition, compose, docker, orchestration, environment, env file
menu:
main:
parent: workw_compose
@ -38,4 +39,4 @@ file, but can also be used to define the following
- [User guide](index.md)
- [Command line reference](./reference/index.md)
- [Compose file reference](compose-file.md)
- [Compose file reference](compose-file.md)

5
compose/environment-variables.md
View File

@ -1,6 +1,7 @@
---
description: How to set, use and manage environment variables in Compose
keywords: fig, composition, compose, docker, orchestration, environment, variables, env file
keywords:
- fig, composition, compose, docker, orchestration, environment, variables, env file
menu:
main:
parent: workw_compose
@ -103,4 +104,4 @@ Several environment variables are available for you to configure the Docker Comp
## Environment variables created by links
When using the ['links' option](compose-file.md#links) in a [v1 Compose file](compose-file.md#version-1), environment variables will be created for each link. They are documented in the [Link environment variables reference](link-env-deprecated.md). Please note, however, that these variables are deprecated - you should just use the link alias as a hostname instead.
When using the ['links' option](compose-file.md#links) in a [v1 Compose file](compose-file.md#version-1), environment variables will be created for each link. They are documented in the [Link environment variables reference](link-env-deprecated.md). Please note, however, that these variables are deprecated - you should just use the link alias as a hostname instead.

5
compose/extends.md
View File

@ -1,7 +1,8 @@
---
description: How to use Docker Compose's extends keyword to share configuration between
files and projects
keywords: fig, composition, compose, docker, orchestration, documentation, docs
keywords:
- fig, composition, compose, docker, orchestration, documentation, docs
menu:
main:
parent: workw_compose
@ -350,4 +351,4 @@ In the case of `environment`, `labels`, `volumes` and `devices`, Compose
- [Get started with Rails](rails.md)
- [Get started with WordPress](wordpress.md)
- [Command line reference](./reference/index.md)
- [Compose file reference](compose-file.md)
- [Compose file reference](compose-file.md)

5
compose/gettingstarted.md
View File

@ -1,6 +1,7 @@
---
description: Getting started with Docker Compose
keywords: documentation, docs, docker, compose, orchestration, containers
keywords:
- documentation, docs, docker, compose, orchestration, containers
menu:
main:
parent: workw_compose
@ -186,4 +187,4 @@ At this point, you have seen the basics of how Compose works.
- Next, try the quick start guide for [Django](django.md),
[Rails](rails.md), or [WordPress](wordpress.md).
- [Explore the full list of Compose commands](./reference/index.md)
- [Compose configuration file reference](compose-file.md)
- [Compose configuration file reference](compose-file.md)

5
compose/index.md
View File

@ -1,6 +1,7 @@
---
description: Introduction and Overview of Compose
keywords: documentation, docs, docker, compose, orchestration, containers
keywords:
- documentation, docs, docker, compose, orchestration, containers
menu:
main:
identifier: workw_compose
@ -25,4 +26,4 @@ Compose is a tool for defining and running multi-container Docker applications.
To see a detailed list of changes for past and current releases of Docker
Compose, please refer to the
[CHANGELOG](https://github.com/docker/compose/blob/master/CHANGELOG.md).
[CHANGELOG](https://github.com/docker/compose/blob/master/CHANGELOG.md).

5
compose/install.md
View File

@ -1,6 +1,7 @@
---
description: How to install Docker Compose
keywords: compose, orchestration, install, installation, docker, documentation
keywords:
- compose, orchestration, install, installation, docker, documentation
menu:
main:
parent: workw_compose
@ -131,4 +132,4 @@ To uninstall Docker Compose if you installed using `pip`:
- [Get started with Rails](rails.md)
- [Get started with WordPress](wordpress.md)
- [Command line reference](./reference/index.md)
- [Compose file reference](compose-file.md)
- [Compose file reference](compose-file.md)

5
compose/link-env-deprecated.md
View File

@ -2,7 +2,8 @@
aliases:
- /compose/env
description: Compose CLI reference
keywords: fig, composition, compose, docker, orchestration, cli, reference
keywords:
- fig, composition, compose, docker, orchestration, cli, reference
menu:
main:
parent: workw_compose
@ -45,4 +46,4 @@ Fully qualified container name, e.g. `DB_1_NAME=/myapp_web_1/myapp_db_1`
- [User guide](index.md)
- [Installing Compose](install.md)
- [Command line reference](./reference/index.md)
- [Compose file reference](compose-file.md)
- [Compose file reference](compose-file.md)

5
compose/networking.md
View File

@ -1,6 +1,7 @@
---
description: How Compose sets up networking between containers
keywords: documentation, docs, docker, compose, orchestration, containers, networking
keywords:
- documentation, docs, docker, compose, orchestration, containers, networking
menu:
main:
parent: workw_compose
@ -149,4 +150,4 @@ If you want your containers to join a pre-existing network, use the [`external`
external:
name: my-pre-existing-network
Instead of attempting to create a network called `[projectname]_default`, Compose will look for a network called `my-pre-existing-network` and connect your app's containers to it.
Instead of attempting to create a network called `[projectname]_default`, Compose will look for a network called `my-pre-existing-network` and connect your app's containers to it.

5
compose/overview.md
View File

@ -1,6 +1,7 @@
---
description: Introduction and Overview of Compose
keywords: documentation, docs, docker, compose, orchestration, containers
keywords:
- documentation, docs, docker, compose, orchestration, containers
menu:
main:
parent: workw_compose
@ -183,4 +184,4 @@ 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/compose/pulls).
For more information and resources, please visit the [Getting Help project page](/opensource/get-help/).
For more information and resources, please visit the [Getting Help project page](/opensource/get-help/).

5
compose/production.md
View File

@ -1,6 +1,7 @@
---
description: Guide to using Docker Compose in production
keywords: documentation, docs, docker, compose, orchestration, containers, production
keywords:
- documentation, docs, docker, compose, orchestration, containers, production
menu:
main:
parent: workw_compose
@ -83,4 +84,4 @@ Read more about the Compose/Swarm integration in the
- [Installing Compose](install.md)
- [Command line reference](./reference/index.md)
- [Compose file reference](compose-file.md)
- [Compose file reference](compose-file.md)

5
compose/rails.md
View File

@ -1,6 +1,7 @@
---
description: Getting started with Docker Compose and Rails
keywords: documentation, docs, docker, compose, orchestration, containers
keywords:
- documentation, docs, docker, compose, orchestration, containers
menu:
main:
parent: workw_compose
@ -170,4 +171,4 @@ up`.
- [Get started with Django](django.md)
- [Get started with WordPress](wordpress.md)
- [Command line reference](./reference/index.md)
- [Compose file reference](compose-file.md)
- [Compose file reference](compose-file.md)

5
compose/swarm.md
View File

@ -1,6 +1,7 @@
---
description: How to use Compose and Swarm together to deploy apps to multi-host clusters
keywords: documentation, docs, docker, compose, orchestration, containers, swarm
keywords:
- documentation, docs, docker, compose, orchestration, containers, swarm
menu:
main:
parent: workw_compose
@ -176,4 +177,4 @@ them.
- "affinity:image==redis"
For the full set of available filters and expressions, see the [Swarm
documentation](/swarm/scheduler/filter.md).
documentation](/swarm/scheduler/filter.md).

5
compose/wordpress.md
View File

@ -1,6 +1,7 @@
---
description: Getting started with Compose and WordPress
keywords: documentation, docs, docker, compose, orchestration, containers
keywords:
- documentation, docs, docker, compose, orchestration, containers
menu:
main:
parent: workw_compose
@ -112,4 +113,4 @@ At this point, WordPress should be running on port `8000` of your Docker Host, a
- [Get started with Django](django.md)
- [Get started with Rails](rails.md)
- [Command line reference](./reference/index.md)
- [Compose file reference](compose-file.md)
- [Compose file reference](compose-file.md)

5
cs-engine/index.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-trusted-registry/cs-engine/
description: Learn more about the Commercially Supported Docker Engine.
keywords: docker, engine, documentation
keywords:
- docker, engine, documentation
menu:
main:
identifier: menu_csengine
@ -16,4 +17,4 @@ This section includes the following topics:
* [Install CS Docker Engine](install.md)
* [Upgrade](upgrade.md)
* [Release notes](release-notes/release-notes.md)
* [Release notes](release-notes/release-notes.md)

5
cs-engine/install.md
View File

@ -4,7 +4,8 @@ aliases:
- /docker-trusted-registry/install/install-csengine/
- /docker-trusted-registry/cs-engine/install/
description: Learn how to install the commercially supported version of Docker Engine.
keywords: docker, engine, dtr, install
keywords:
- docker, engine, dtr, install
menu:
main:
identifier: csengine_install
@ -197,4 +198,4 @@ to the `docker` group.
$ sudo usermod -a -G docker $USER
```
8. Log out and log back in to have your new permissions take effect.
8. Log out and log back in to have your new permissions take effect.

5
cs-engine/release-notes/index.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-trusted-registry/cs-engine/release-notes/
description: The release notes for CS Docker Engine.
keywords: docker, engine, release notes
keywords:
- docker, engine, release notes
menu:
main:
identifier: menu_csengine_release_notes
@ -14,4 +15,4 @@ title: Release notes
# Docker CS Engine release notes
* [Release notes](release-notes.md)
* [Prior release notes](prior-release-notes.md)
* [Prior release notes](prior-release-notes.md)

6
cs-engine/release-notes/prior-release-notes.md
View File

@ -3,7 +3,9 @@ aliases:
- /docker-trusted-registry/cse-prior-release-notes/
- /docker-trusted-registry/cs-engine/release-notes/prior-release-notes/
description: Archived release notes for commercially supported Docker Engine
keywords: docker, documentation, about, technology, understanding, enterprise, hub, registry, release, commercially supported Docker Engine
keywords:
- docker, documentation, about, technology, understanding, enterprise, hub, registry,release,
commercially supported Docker Engine
menu:
main:
identifier: csengine_prior_release_notes
@ -339,4 +341,4 @@ Because this addition is preventative, no CVE-ID is requested.
(23 Apr 2015)
First release, see the [Docker Engine 1.6.0 Release notes](/v1.6/release-notes/)
for more details.
for more details.

7
cs-engine/release-notes/release-notes.md
View File

@ -3,8 +3,9 @@ aliases:
- /docker-trusted-registry/cse-release-notes/
- /docker-trusted-registry/cs-engine/release-notes/release-notes/
description: Commercially supported Docker Engine release notes
keywords: docker, documentation, about, technology, understanding, enterprise, hub,
registry, Commercially Supported Docker Engine, release notes
keywords:
- docker, documentation, about, technology, understanding, enterprise, hub, registry,
Commercially Supported Docker Engine, release notes
menu:
main:
identifier: csengine_release_notes
@ -111,4 +112,4 @@ https://github.com/docker/docker/issues/22486
## CS Engine 1.11.1-cs1
(27 April 2016)
In this release the CS Engine is supported on RHEL 7.2 OS
In this release the CS Engine is supported on RHEL 7.2 OS

5
cs-engine/upgrade.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-trusted-registry/cs-engine/upgrade/
description: Learn how to install the commercially supported version of Docker Engine.
keywords: docker, engine, dtr, upgrade
keywords:
- docker, engine, dtr, upgrade
menu:
main:
identifier: csengine_upgrade
@ -269,4 +270,4 @@ Use these instructions to update APT-based systems.
```bash
$ sudo apt-get upgrade docker-engine
```
```

5
docker-cloud/apps/api-roles.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/api-roles/
description: API Roles
keywords: API, Services, roles
keywords:
- API, Services, roles
menu:
main:
parent: apps
@ -36,4 +37,4 @@ $ curl -H "Authorization: $DOCKERCLOUD_AUTH" -H "Accept: application/json" $WEB_
For example, you can use information retrieved using the API to read the linked
endpoints, and use them to reconfigure a proxy container.
See the [API documentation](/apidocs/docker-cloud.md) for more information on the different API operations available.
See the [API documentation](/apidocs/docker-cloud.md) for more information on the different API operations available.

5
docker-cloud/apps/auto-destroy.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/auto-destroy/
description: Autodestroy
keywords: Autodestroy, service, terminate, container
keywords:
- Autodestroy, service, terminate, container
menu:
main:
parent: apps
@ -79,4 +80,4 @@ PATCH /api/app/v1/service/(uuid)/ HTTP/1.1
#### Enabling autodestroy using the CLI
```
$ docker-cloud service set --autodestroy ALWAYS (name or uuid)
```
```

5
docker-cloud/apps/auto-redeploy.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/auto-redeploy/
description: Autoredeploy
keywords: Autoredeploy, image, store, service
keywords:
- Autoredeploy, image, store, service
menu:
main:
parent: apps
@ -80,4 +81,4 @@ PATCH /api/app/v1/service/(uuid)/ HTTP/1.1
{
"autoredeploy": true
}
```
```

5
docker-cloud/apps/autorestart.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/autorestart/
description: Automatically restart a container in Docker Cloud
keywords: container, restart, automated
keywords:
- container, restart, automated
menu:
main:
parent: apps
@ -90,4 +91,4 @@ PATCH /api/app/v1/service/(uuid)/ HTTP/1.1
$ docker-cloud service set --autorestart ALWAYS (name or uuid)
```
See the [API documentation](/apidocs/docker-cloud.md) for more information.
See the [API documentation](/apidocs/docker-cloud.md) for more information.

5
docker-cloud/apps/deploy-tags.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/deploy-tags/
description: Deployment tags
keywords: Deployment, tags, services
keywords:
- Deployment, tags, services
menu:
main:
parent: apps
@ -120,4 +121,4 @@ be deployed to the nodes that match the new tags.
## Using deployment tags in the API and CLI
See the [tags API and CLI documentation](/apidocs/docker-cloud.md#tags) for more information on how to use tags with our API and CLI.
See the [tags API and CLI documentation](/apidocs/docker-cloud.md#tags) for more information on how to use tags with our API and CLI.

5
docker-cloud/apps/deploy-to-cloud-btn.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/feature-reference/deploy-to-cloud/
- /docker-cloud/tutorials/deploy-to-cloud/
description: Deploy to Docker Cloud
keywords: deploy, docker, cloud
keywords:
- deploy, docker, cloud
menu:
main:
parent: apps
@ -65,4 +66,4 @@ where `<repo_url>` is the path to your GitHub repository. For example:
You can use your own image for the link (or no image). Our **Deploy to Docker Cloud** image is available at the following URL:
* `https://files.cloud.docker.com/images/deploy-to-dockercloud.svg`
* `https://files.cloud.docker.com/images/deploy-to-dockercloud.svg`

5
docker-cloud/apps/index.md
View File

@ -1,6 +1,7 @@
---
description: Manage your Docker Cloud Applications
keywords: applications, reference, Cloud
keywords:
- applications, reference, Cloud
menu:
main:
parent: apps
@ -38,4 +39,4 @@ Use the following features to automate specific actions on your Docker Cloud app
* [Automatic container destroy](auto-destroy.md)
* [Automatic container restart](autorestart.md)
* [Autoredeploy](auto-redeploy.md)
* [Use triggers](triggers.md)
* [Use triggers](triggers.md)

5
docker-cloud/apps/load-balance-hello-world.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/intermediate/load-balance-hello-world/
- /docker-cloud/tutorials/load-balance-hello-world/
description: Create a proxy or load balancer
keywords: proxy, load, balancer
keywords:
- proxy, load, balancer
menu:
main:
parent: apps
@ -201,4 +202,4 @@ links](service-links.md).
You can try this by pointing your web browser to
*servicename.username.svc.dockerapp.io* or using *dig* or *nslookup* to see how
the service endpoint resolves.
the service endpoint resolves.

5
docker-cloud/apps/ports.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/ports/
description: Publish and expose service or container ports
keywords: publish, expose, ports, containers, services
keywords:
- publish, expose, ports, containers, services
menu:
main:
parent: apps
@ -124,4 +125,4 @@ not dynamic) is assigned a DNS endpoint in the format
running, in a [round-robin
fashion](https://en.wikipedia.org/wiki/Round-robin_DNS).
You can see a list of service endpoints on the stack and service detail views, under the **Endpoints** tab.
You can see a list of service endpoints on the stack and service detail views, under the **Endpoints** tab.

5
docker-cloud/apps/service-links.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/service-links/
description: Service discovery
keywords: service, discover, links
keywords:
- service, discover, links
menu:
main:
parent: apps
@ -166,4 +167,4 @@ Where:
These environment variables are also copied to linked containers with the `NAME_ENV_` prefix.
If you provide API access to your service, you can use the generated token (stored in `DOCKERCLOUD_AUTH`) to access these API URLs to gather information or automate operations, such as scaling.
If you provide API access to your service, you can use the generated token (stored in `DOCKERCLOUD_AUTH`) to access these API URLs to gather information or automate operations, such as scaling.

5
docker-cloud/apps/service-redeploy.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/service-redeploy/
description: Redeploy running services
keywords: redeploy, running, services
keywords:
- redeploy, running, services
menu:
main:
parent: apps
@ -77,4 +78,4 @@ whenever a new image is pushed. See the [Autoredeploy documentation](auto-redepl
## Redeploy a service using webhooks
You can also use **triggers** to redeploy a service, for example when its image
is pushed or rebuilt in a third-party registry. See the [Triggers documentation](triggers.md) to learn more.
is pushed or rebuilt in a third-party registry. See the [Triggers documentation](triggers.md) to learn more.

5
docker-cloud/apps/service-scaling.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/service-scaling/
description: Scale your service, spawn new containers
keywords: spawn, container, service, deploy
keywords:
- spawn, container, service, deploy
menu:
main:
parent: apps
@ -159,4 +160,4 @@ application through the CLI: 
```bash
$ docker-cloud service run --sequential [...] 
```
```

5
docker-cloud/apps/stack-yaml-reference.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/stack-yaml-reference/
description: Stack YAML reference
keywords: YAML, stack, reference
keywords:
- YAML, stack, reference
menu:
main:
parent: apps
@ -325,4 +326,4 @@ Stack files (`docker-cloud.yml`) were designed with `docker-compose.yml` in mind
build
external_links
env_file
```
```

5
docker-cloud/apps/stacks.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/stacks/
description: Manage service stacks
keywords: service, stack, yaml
keywords:
- service, stack, yaml
menu:
main:
parent: apps
@ -130,4 +131,4 @@ You can update a stack from a YAML file by executing:
docker-cloud stack update -f docker-cloud.yml (uuid or name)
```
Check our [CLI documentation](/apidocs/docker-cloud.md#stacks) for more information.
Check our [CLI documentation](/apidocs/docker-cloud.md#stacks) for more information.

5
docker-cloud/apps/triggers.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/triggers/
description: Use triggers
keywords: API, triggers, endpoints
keywords:
- API, triggers, endpoints
menu:
main:
parent: apps
@ -60,4 +61,4 @@ Once the trigger is revoked, it stops accepting requests.
## Using triggers in the API and CLI
See our [API and CLI documentation](/apidocs/docker-cloud.md#triggers) to learn how to use triggers with our API and the CLI.
See our [API and CLI documentation](/apidocs/docker-cloud.md#triggers) to learn how to use triggers with our API and the CLI.

5
docker-cloud/apps/volumes.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/tutorials/download-volume-data/
- /docker-cloud/feature-reference/volumes/
description: Work with data volumes
keywords: data, volumes, create, reuse
keywords:
- data, volumes, create, reuse
menu:
main:
parent: apps
@ -71,4 +72,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 .
```
```

5
docker-cloud/builds/advanced.md
View File

@ -1,6 +1,7 @@
---
description: Automated builds
keywords: automated, build, images
keywords:
- automated, build, images
menu:
main:
parent: builds
@ -116,4 +117,4 @@ If you needed to give the resulting image multiple tags, or push the same image
```none
docker tag $IMAGE_NAME $DOCKER_REPO:$SOURCE_COMMIT
docker push $DOCKER_REPO:$SOURCE_COMMIT
```
```

5
docker-cloud/builds/automated-build.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/automated-build/
description: Automated builds
keywords: automated, build, images
keywords:
- automated, build, images
menu:
main:
parent: builds
@ -299,4 +300,4 @@ Docker Cloud's [Autotest](automated-testing.md) feature which
integrates seamlessly with autobuild and autoredeploy.
> **Note**: While the Autotest feature builds an image for testing purposes, it
does not push the resulting image to Docker Cloud or the external registry.
does not push the resulting image to Docker Cloud or the external registry.

9
docker-cloud/builds/automated-testing.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/automated-testing/
description: Automated tests
keywords: Automated, testing, repository
keywords:
- Automated, testing, repository
menu:
main:
parent: builds
@ -79,8 +80,8 @@ Docker repository, regardless of the Autotest settings.
The following options are available:
* `Off`: No additional test builds. Tests only run if they're configured as part of an automated build.
* `Internal pull requests`: Run a test build for any pull requests to branches that match a build rule, but only when the pull request comes from the same source repository.
* `Internal and external pull requests`: Run a test build for any pull requests to branches that match a build rule, including when the pull request originated in an external source repository.
* `Source repository`: Run a test build for any pull requests to branches that match a build rule, but only when the pull request comes from the same source repository.
* `Source repository & external pull requests`: Run a test build for any pull requests to branches that match a build rule, including when the pull request originated in an external source repository.
> **Note**: For security purposes, autotest on _external pull requests_ is
disabled on public repositories. If you select this option on a public
@ -97,4 +98,4 @@ From the repository's details page, click **Timeline**.
From this tab you can see any pending, in-progress, successful, and failed
builds and test runs for the repository.
You can click any timeline entry to view the logs for each test run.
You can click any timeline entry to view the logs for each test run.

6
docker-cloud/builds/image-scan.md
View File

@ -1,6 +1,8 @@
---
description: 'Docker Security Scanning: automatic image scanning'
keywords: Docker, docker, scan, scanning, security, registry, plans, Docker Cloud, docs, documentation, trusted, builds, trusted builds, automated builds
keywords:
- Docker, docker, scan, scanning, security, registry, plans, Docker Cloud, docs, documentation,
trusted, builds, trusted builds, automated builds
menu:
main:
parent: builds
@ -186,4 +188,4 @@ components.
## Related information
* [Learn about CVE and how it compiles data](https://cve.mitre.org/about/index.html).
* [How to create a Docker Official image](/docker-hub/official_repos/)
* [How to create a Docker Official image](/docker-hub/official_repos/)

5
docker-cloud/builds/index.md
View File

@ -1,6 +1,7 @@
---
description: Manage Builds and Images in Docker Cloud
keywords: builds, images, Cloud
keywords:
- builds, images, Cloud
menu:
main:
parent: builds
@ -29,4 +30,4 @@ running services when a build passes its tests.
* [Automated repository tests](automated-testing.md)
* [Advanced options for Autobuild and Autotest](advanced.md)
![a Docker Cloud repository's General view](images/repo-general.png)
![a Docker Cloud repository's General view](images/repo-general.png)

5
docker-cloud/builds/link-source.md
View File

@ -1,7 +1,8 @@
---
aliases: /docker-cloud/tutorials/link-source/
description: Link to your source code repository
keywords: sourcecode, github, bitbucket, Cloud
keywords:
- sourcecode, github, bitbucket, Cloud
menu:
main:
parent: builds
@ -156,4 +157,4 @@ unlink it both from Docker Cloud, *and* from your Bitbucket account.
> **Note**: Each repository that is configured as an automated build source
contains a webhook that notifies Docker Cloud of changes in the repository. This
webhook is not automatically removed when you revoke access to a source code
provider.
provider.

5
docker-cloud/builds/push-images.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/intermediate/pushing-images-to-dockercloud/
- /docker-cloud/tutorials/pushing-images-to-dockercloud/
description: Push images to Docker Cloud
keywords: images, private, registry
keywords:
- images, private, registry
menu:
main:
parent: builds
@ -61,4 +62,4 @@ Follow the <a href="http://docs.docker.com/installation/" target="_blank">offic
> Cloud, you might need to select the organization name or your username from
> the dropdown menu see other repositories.
![](images/private_image.png)
![](images/private_image.png)

5
docker-cloud/builds/repos.md
View File

@ -1,6 +1,7 @@
---
description: Create and edit Docker Cloud repositories
keywords: Docker Cloud repositories, automated, build, images
keywords:
- Docker Cloud repositories, automated, build, images
menu:
main:
parent: builds
@ -93,4 +94,4 @@ You can link to repositories hosted on a third party registry. This allows you t
## What's next?
Once you create or link to a repository in Docker Cloud, you can set up [automated testing](automated-testing.md) and [automated builds](automated-build.md).
Once you create or link to a repository in Docker Cloud, you can set up [automated testing](automated-testing.md) and [automated builds](automated-build.md).

5
docker-cloud/docker-errors-faq.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/faq/docker-errors-faq/
description: Known Docker Engine issues in Docker Cloud
keywords: Engine, issues, troubleshoot
keywords:
- Engine, issues, troubleshoot
menu:
main:
parent: docker-cloud
@ -107,4 +108,4 @@ Timeouts occur when pulling the image takes more than 10 minutes. This can somet
#### Workaround
Restart the `dockercloud-agent` service (`sudo service dockercloud-agent restart`) on the node, or restart the node.
Restart the `dockercloud-agent` service (`sudo service dockercloud-agent restart`) on the node, or restart the node.

5
docker-cloud/dockerid.md
View File

@ -1,6 +1,7 @@
---
description: Using your DockerID to log in to Docker Cloud
keywords: one, two, three
keywords:
- one, two, three
menu:
main:
parent: docker-cloud
@ -58,4 +59,4 @@ Like free Docker Hub accounts, free Docker Cloud accounts come with one free
private repository.
If you require more private repositories, visit your **Cloud settings** and
select **Plan** to see the available paid accounts.
select **Plan** to see the available paid accounts.

5
docker-cloud/getting-started/connect-infra.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/use-hosted/
description: How to link Docker Cloud to a hosted cloud services provider or your
own hosts
keywords: node, create, understand
keywords:
- node, create, understand
menu:
main:
aliases:
@ -37,4 +38,4 @@ Then, use the one of the detailed tutorials below to link your account. You shou
If you are not using a cloud services provider and are using your own hosts, you'll need to install the Docker Cloud Agent on those hosts so that Docker Cloud can communicate with them. Follow the directions at [Bring Your Own Node instructions](../infrastructure/byoh.md). Open these instructions in a new window or tab so you can return to this tutorial once you're done linking your hosts.
## Ready to go?
Once you've linked to your cloud services provider or to your own hosts, [continue the tutorial and deploy your first node](your_first_node.md).
Once you've linked to your cloud services provider or to your own hosts, [continue the tutorial and deploy your first node](your_first_node.md).

5
docker-cloud/getting-started/deploy-app/10_provision_a_data_backend_for_your_service.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/python/10_provision_a_data_backend_for_your_service/
- /docker-cloud/getting-started/golang/10_provision_a_data_backend_for_your_service/
description: Provision a data backend for the service
keywords: provision, Python, service
keywords:
- provision, Python, service
menu:
main:
parent: deploy-app
@ -69,4 +70,4 @@ $ curl lb-1.$DOCKER_ID_USER.cont.dockerapp.io
Hello World</br>Hostname: web-3</br>Counter: 5%
```
Next, we'll look at [Stackfiles for your service](11_service_stacks.md)
Next, we'll look at [Stackfiles for your service](11_service_stacks.md)

5
docker-cloud/getting-started/deploy-app/11_service_stacks.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/getting-started/python/11_service_stacks/
description: Stackfiles for your service
keywords: Python, service, stack
keywords:
- Python, service, stack
menu:
main:
parent: deploy-app
@ -72,4 +73,4 @@ Or you can specify the YML file to use and its location:
$ docker-cloud up -f /usr/dockercloud/quickstart-python/docker-cloud.yml
```
Next, we'll do some [Data management with Volumes](12_data_management_with_volumes.md)
Next, we'll do some [Data management with Volumes](12_data_management_with_volumes.md)

5
docker-cloud/getting-started/deploy-app/12_data_management_with_volumes.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/getting-started/python/12_data_management_with_volumes/
description: Data management with Volumes
keywords: Python, data, management
keywords:
- Python, data, management
menu:
main:
parent: deploy-app
@ -140,4 +141,4 @@ set up a volume to save the data.
There's lots more to learn about Docker Cloud, so check out [the rest of our documentation](/docker-cloud/), the [API and CLI Documentation](../../../apidocs/docker-cloud.md), and our [Knowledge Hub](https://success.docker.com/Cloud) and [Docker Cloud Forums](https://forums.docker.com/c/docker-cloud).
Happy Docking!
Happy Docking!

5
docker-cloud/getting-started/deploy-app/1_introduction.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/python/1_introduction/
- /docker-cloud/getting-started/golang/1_introduction/
description: Deploy an app to Docker Cloud
keywords: deploy, Python, application
keywords:
- deploy, Python, application
menu:
main:
parent: deploy-app
@ -26,4 +27,4 @@ This tutorial assumes that you have:
Let's get started!
[Set up your environment](2_set_up.md).
[Set up your environment](2_set_up.md).

5
docker-cloud/getting-started/deploy-app/2_set_up.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/python/2_set_up/
- /docker-cloud/getting-started/golang/2_set_up/
description: Set up the application
keywords: Python, application, setup
keywords:
- Python, application, setup
menu:
main:
parent: deploy-app
@ -83,4 +84,4 @@ If you don't want to do this, make sure you substitute your username for $DOCKER
$ export DOCKER_ID_USER=my-username
```
Next up, we'll [Prepare the app](3_prepare_the_app.md).
Next up, we'll [Prepare the app](3_prepare_the_app.md).

5
docker-cloud/getting-started/deploy-app/3_prepare_the_app.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/python/3_prepare_the_app/
- /docker-cloud/getting-started/golang/3_prepare_the_app/
description: Prepare the application
keywords: Python, prepare, application
keywords:
- Python, prepare, application
menu:
main:
parent: deploy-app
@ -50,4 +51,4 @@ $ docker build --tag quickstart-python .
$ docker build --tag quickstart-go .
```
Next, we [Push the Docker image to Docker Cloud's Registry](4_push_to_cloud_registry.md).
Next, we [Push the Docker image to Docker Cloud's Registry](4_push_to_cloud_registry.md).

5
docker-cloud/getting-started/deploy-app/4_push_to_cloud_registry.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/python/4_push_to_cloud_registry/
- /docker-cloud/getting-started/golang/4_push_to_cloud_registry/
description: Push the Docker image to Docker Cloud's Registry
keywords: image, Docker, cloud
keywords:
- image, Docker, cloud
menu:
main:
parent: deploy-app
@ -52,4 +53,4 @@ my-username/quickstart-python
my-username/quickstart-go
```
Next: [Deploy the app as a Docker Cloud service](5_deploy_the_app_as_a_service.md).
Next: [Deploy the app as a Docker Cloud service](5_deploy_the_app_as_a_service.md).

5
docker-cloud/getting-started/deploy-app/5_deploy_the_app_as_a_service.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/python/5_deploy_the_app_as_a_service/
- /docker-cloud/getting-started/golang/5_deploy_the_app_as_a_service/
description: Deploy the app as a Docker Cloud service
keywords: Python, deploy, Cloud
keywords:
- Python, deploy, Cloud
menu:
main:
parent: deploy-app
@ -90,4 +91,4 @@ Hello World!</br>Hostname: web-1</br>Counter: Redis Cache not found, counter dis
**CONGRATULATIONS!** You've deployed your first service using Docker Cloud.
Next: [Define environment variables](6_define_environment_variables.md).
Next: [Define environment variables](6_define_environment_variables.md).

5
docker-cloud/getting-started/deploy-app/6_define_environment_variables.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/python/6_define_environment_variables/
- /docker-cloud/getting-started/golang/6_define_environment_variables/
description: Define environment variables
keywords: Python, service, environment, service
keywords:
- Python, service, environment, service
menu:
main:
parent: deploy-app
@ -77,4 +78,4 @@ Wondering where the default value for the **NAME** environment variable is set?
ENV NAME World
```
Next, we'll try [Scaling the service](7_scale_the_service.md).
Next, we'll try [Scaling the service](7_scale_the_service.md).

5
docker-cloud/getting-started/deploy-app/7_scale_the_service.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/python/7_scale_the_service/
- /docker-cloud/getting-started/golang/7_scale_the_service/
description: Scale the service
keywords: scale, Python, service
keywords:
- scale, Python, service
menu:
main:
parent: deploy-app
@ -72,4 +73,4 @@ Hello Python Users!</br>Hostname: web-2</br>Counter: Redis Cache not found, coun
Congratulations! You now have *two* containers running in your **web** service.
Next: [View service logs](8_view_logs.md)
Next: [View service logs](8_view_logs.md)

5
docker-cloud/getting-started/deploy-app/8_view_logs.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/python/8_view_logs/
- /docker-cloud/getting-started/golang/8_view_logs/
description: View service logs
keywords: View, logs, Python
keywords:
- View, logs, Python
menu:
main:
parent: deploy-app
@ -42,4 +43,4 @@ $ docker-cloud container logs web-1
Visit your application using curl or your browser again. Run the `service logs web` command again, and you will see another log message for your visit.
Next, let's explore how to [Load balance the service](9_load-balance_the_service.md).
Next, let's explore how to [Load balance the service](9_load-balance_the_service.md).

5
docker-cloud/getting-started/deploy-app/9_load-balance_the_service.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/python/9_load-balance_the_service/
- /docker-cloud/getting-started/golang/9_load-balance_the_service/
description: Load-balance the service
keywords: load, balance, Python
keywords:
- load, balance, Python
menu:
main:
parent: deploy-app
@ -77,4 +78,4 @@ Hello Friendly Users!</br>Hostname: web-2</br>Counter: Redis Cache not found, co
You can learn more about *dockercloud/haproxy*, our free open source HAProxy image <a href="https://github.com/docker/dockercloud-haproxy" target="_blank">here</a>.
Next: [Provision a data backend for your service](10_provision_a_data_backend_for_your_service.md)
Next: [Provision a data backend for your service](10_provision_a_data_backend_for_your_service.md)

5
docker-cloud/getting-started/deploy-app/index.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/python/
- /docker-cloud/getting-started/golang/
description: Go or Python and Docker Cloud
keywords: Python, Go, Docker, Cloud, application
keywords:
- Python, Go, Docker, Cloud, application
menu:
main:
identifier: deploy-app
@ -25,4 +26,4 @@ title: Deploy an application
* [Load-balance the service](9_load-balance_the_service.md)
* [Provision a data backend for the service](10_provision_a_data_backend_for_your_service.md)
* [Stackfiles for your service](11_service_stacks.md)
* [Data management with Volumes](12_data_management_with_volumes.md)
* [Data management with Volumes](12_data_management_with_volumes.md)

5
docker-cloud/getting-started/index.md
View File

@ -1,7 +1,8 @@
---
description: 'Getting Started with Docker Cloud: Setting up a node using a hosted
cloud provider or your own nodes, deploying a service and clustering.'
keywords: one, two, three
keywords:
- one, two, three
menu:
main:
identifier: getting-started
@ -25,4 +26,4 @@ If you're completely new to Docker Cloud, start here!
* [Deploy your first node](your_first_node.md) Then, deploy your first nodes,
* [Create your first service](your_first_service.md) ...And finish by deploying your first service.
Ready to deploy your first web service? [Deploy a web application in Docker Cloud](deploy-app/index.md)
Ready to deploy your first web service? [Deploy a web application in Docker Cloud](deploy-app/index.md)

5
docker-cloud/getting-started/intro_cloud.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/getting-started/beginner/intro_cloud/
description: Introducing Docker Cloud concepts and terminology
keywords: node, create, understand
keywords:
- node, create, understand
menu:
main:
parent: getting-started
@ -40,4 +41,4 @@ Services are logical groups of containers from the same image. Services make it
## Let's get started!
Log in to <a href="https://cloud.docker.com" target="_blank">Docker Cloud</a> using your Docker ID. (These are the same credentials you used for Docker Hub if you had an account there.)
Start here [by linking your infrastructure to Docker Cloud](connect-infra.md).
Start here [by linking your infrastructure to Docker Cloud](connect-infra.md).

5
docker-cloud/getting-started/your_first_node.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/beginner/your_first_node/
- /docker-cloud/getting-started/beginner/deploy_first_node/
description: Deploy your first node on Docker Cloud
keywords: node, create, understand
keywords:
- node, create, understand
menu:
main:
parent: getting-started
@ -47,4 +48,4 @@ Now that you've got at least one **node** deployed, it's time to deploy your fir
Remember that a service is a group of containers from the same container image. Services make it simple to scale your application across a number of nodes. They can also be linked one to another even if they are deployed on different nodes, regions, or even on different cloud providers.
[Continue the tutorial and deploy your first service](your_first_service.md).
[Continue the tutorial and deploy your first service](your_first_service.md).

5
docker-cloud/getting-started/your_first_service.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/beginner/your_first_service/
- /docker-cloud/getting-started/beginner/deploy_first_service/
description: Deploy your first service on Docker Cloud
keywords: service, Cloud, three
keywords:
- service, Cloud, three
menu:
main:
parent: getting-started
@ -124,4 +125,4 @@ Click the links icon to the right of the endpoint. This opens a new tab and show
### What's next?
Learn more about [scaling your service](../apps/service-scaling.md), or check out some of our other [Deploy an app tutorial](deploy-app/index.md).
Learn more about [scaling your service](../apps/service-scaling.md), or check out some of our other [Deploy an app tutorial](deploy-app/index.md).

5
docker-cloud/index.md
View File

@ -1,6 +1,7 @@
---
description: Docker Cloud
keywords: Docker, cloud
keywords:
- Docker, cloud
menu:
main:
identifier: docker-cloud
@ -46,4 +47,4 @@ title: Docker Cloud
<tr>
<td class="sherbet" colspan="2"> <a href="https://docs.docker.com/apidocs/docker-cloud/">API Docs</a> || <a href="docker-errors-faq.md">Frequently Asked Questions</a> || <a href="release-notes.md">Release Notes</a></td>
</tr>
</table>
</table>

5
docker-cloud/infrastructure/byoh.md
View File

@ -4,7 +4,8 @@ aliases:
- /docker-cloud/tutorials/byoh/
- /docker-cloud/getting-started/use-byon/
description: Use the Docker Cloud Agent
keywords: agent, Cloud, install
keywords:
- agent, Cloud, install
menu:
main:
parent: infrastructure
@ -132,4 +133,4 @@ script also tries to install the kernel headers required for `AUFS` support.
> **Note**: If you remove, upgrade, or install over the version of Docker Engine bundled with the Docker Cloud Agent, your nodes may not maintain a connection with Docker Cloud correctly. You will have to reinstall a compatible Engine version (currently version 1.11.2-cs5). Contact Docker Support for more information.
* If you were already using the `AUFS` storage driver before installing `dockercloud-agent`, your existing containers and images appear automatically once installation finishes.
* If you were using `devicemapper` or any other storage driver, and the `AUFS` driver installs successfully you will not be able to use your existing containers and images. You can check if the installation succeeded by running `docker info | grep Storage`.
* If you were using `devicemapper` or any other storage driver, and the `AUFS` driver installs successfully you will not be able to use your existing containers and images. You can check if the installation succeeded by running `docker info | grep Storage`.

5
docker-cloud/infrastructure/cloud-on-aws-faq.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/faq/cloud-on-aws-faq/
description: Docker Cloud on AWS
keywords: Cloud, AWS, faq
keywords:
- Cloud, AWS, faq
menu:
main:
parent: infrastructure
@ -158,4 +159,4 @@ Use the <a href="https://hub.docker.com/r/dockercloud/dockup/"
target="_blank">dockercloud/dockup</a> utility image to back up your volumes.
You only need to run it taking the volumes of the container you want to back up
with `volumes-from` and pass it the environment configuration of the container.
You can find more information in its Github repository.
You can find more information in its Github repository.

5
docker-cloud/infrastructure/cloud-on-packet.net-faq.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/faq/cloud-on-packet.net-faq/
description: Docker Cloud and Packet.net
keywords: Packet.net, Cloud, drives
keywords:
- Packet.net, Cloud, drives
menu:
main:
parent: infrastructure
@ -58,4 +59,4 @@ Packet.net copies SSH keys into the created device. This means you can upload yo
Here is a list of known errors thrown by Packet.net API:
- **You have reached the maximum number of projects you can create (number)**. Please contact `help@packet.net` -> Packet.net limits the number of projects that an account can create. Delete projects in the account or contact [Packet.net](https://www.packet.net/) support to increase the limit.
- **There is an error with your Packet.net account**. Please contact `help@packet.net` -> There is something else wrong with your Packet.net account. Contact [Packet.net](https://www.packet.net/) for more details.
- **There is an error with your Packet.net account**. Please contact `help@packet.net` -> There is something else wrong with your Packet.net account. Contact [Packet.net](https://www.packet.net/) for more details.

5
docker-cloud/infrastructure/deployment-strategies.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/feature-reference/deployment-strategies/
description: Schedule a deployment
keywords: schedule, deployment, container
keywords:
- schedule, deployment, container
menu:
main:
parent: infrastructure
@ -56,4 +57,4 @@ When a service uses the `EVERY_NODE` strategy:
> **Note**: Because of how links are configured when using the **every node**
> strategy, you cannot currently switch from **every node** to **high
> availability** or **emptiest node** and vice versa.
> availability** or **emptiest node** and vice versa.

5
docker-cloud/infrastructure/docker-upgrade.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/feature-reference/docker-upgrade/
- /docker-cloud/tutorials/docker-upgrade/
description: Upgrade Docker Engine on a node
keywords: upgrade, engine, node
keywords:
- upgrade, engine, node
menu:
main:
parent: infrastructure
@ -37,4 +38,4 @@ restarted.
# Upgrading nodes using the API and CLI
See our [API and CLI documentation](/apidocs/docker-cloud.md#upgrade-docker-daemon34) for more information on how to upgrade nodes with our API, SDKs and the CLI.
See our [API and CLI documentation](/apidocs/docker-cloud.md#upgrade-docker-daemon34) for more information on how to upgrade nodes with our API, SDKs and the CLI.

5
docker-cloud/infrastructure/index.md
View File

@ -1,6 +1,7 @@
---
description: Manage network in Docker Cloud
keywords: nodes, hosts, infrastructure, Cloud
keywords:
- nodes, hosts, infrastructure, Cloud
menu:
main:
parent: infrastructure
@ -77,4 +78,4 @@ The pages in this section explain how to link Docker Cloud to your infrastructur
* [Link to Microsoft Azure hosts](link-azure.md)
* [Link to Packet hosts](link-packet.md)
* [Using Docker Cloud and Packet FAQ](cloud-on-packet.net-faq.md)
* [Link to SoftLayer hosts](link-softlayer.md)
* [Link to SoftLayer hosts](link-softlayer.md)

5
docker-cloud/infrastructure/link-aws.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/beginner/link-aws/
- /docker-cloud/getting-started/link-aws/
description: Link your Amazon Web Services account
keywords: AWS, Cloud, link
keywords:
- AWS, Cloud, link
menu:
main:
parent: infrastructure
@ -127,4 +128,4 @@ Once you've created the a `dockercloud-policy`, attached it to a
## What's next?
You're ready to start using AWS as the infrastructure provider
for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).
for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).

5
docker-cloud/infrastructure/link-azure.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/beginner/link-azure/
- /docker-cloud/getting-started/link-azure/
description: Link your Microsoft Azure account
keywords: Microsoft, Azure, account
keywords:
- Microsoft, Azure, account
menu:
main:
parent: infrastructure
@ -44,4 +45,4 @@ Go back to Docker Cloud and enter the subscription ID in the **Azure credentials
## What's next?
You're ready to start using Microsoft Azure as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).
You're ready to start using Microsoft Azure as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).

5
docker-cloud/infrastructure/link-do.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/beginner/link-do/
- /docker-cloud/getting-started/link-do/
description: Link your DigitalOcean account
keywords: link, DigitalOcean, account
keywords:
- link, DigitalOcean, account
menu:
main:
parent: infrastructure
@ -33,4 +34,4 @@ Once you log in, a message appears prompting you to confirm the link.
## What's next?
You're ready to start using using DigitalOcean as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).
You're ready to start using using DigitalOcean as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).

5
docker-cloud/infrastructure/link-packet.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/beginner/link-packet/
- /docker-cloud/getting-started/link-packet/
description: Link your Packet account
keywords: Packet, link, Cloud
keywords:
- Packet, link, Cloud
menu:
main:
parent: infrastructure
@ -30,4 +31,4 @@ Go back to the Docker Cloud tab and paste the new API key in the `Authentication
## What's next?
You're ready to start using Packet as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).
You're ready to start using Packet as the infrastructure provider for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).

5
docker-cloud/infrastructure/link-softlayer.md
View File

@ -3,7 +3,8 @@ aliases:
- /docker-cloud/getting-started/beginner/link-softlayer/
- /docker-cloud/getting-started/link-softlayer/
description: Link your SoftLayer account
keywords: SoftLayer, link, cloud
keywords:
- SoftLayer, link, cloud
menu:
main:
parent: infrastructure
@ -74,4 +75,4 @@ Copy and paste the `username` and the `API Key` you received from SoftLayer into
## What's next?
You're ready to start using SoftLayer as the infrastructure provider
for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).
for Docker Cloud! If you came here from the tutorial, click here to [continue the tutorial and deploy your first node](../getting-started/your_first_node.md).

5
docker-cloud/infrastructure/ssh-into-a-node.md
View File

@ -4,7 +4,8 @@ aliases:
- /docker-cloud/tutorials/ssh-into-a-node/
- /docker-cloud/faq/how-ssh-nodes/
description: SSHing into a Docker Cloud-managed node
keywords: ssh, Cloud, node
keywords:
- ssh, Cloud, node
menu:
main:
parent: infrastructure
@ -106,4 +107,4 @@ Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-40-generic x86_64)
https://landscape.canonical.com/
Last login: Mon Feb 2 23:29:54 2015 from pool-108-30-19-181.nycmny.fios.verizon.net
root@13e9d739-admin:~#
```
```

5
docker-cloud/installing-cli.md
View File

@ -5,7 +5,8 @@ aliases:
- /docker-cloud/tutorials/installing-cli/
description: Using the Docker Cloud CLI on Linux, Windows, and macOS, installing,
updating, uninstall
keywords: cloud, command-line, CLI
keywords:
- cloud, command-line, CLI
menu:
main:
parent: docker-cloud
@ -116,4 +117,4 @@ Open your Terminal application and execute the following command:
```
$ brew uninstall docker-cloud
```
```

5
docker-cloud/orgs.md
View File

@ -1,6 +1,7 @@
---
description: Docker Cloud for Organizations and Teams
keywords: organizations, teams, Docker Cloud, resources, permissions
keywords:
- organizations, teams, Docker Cloud, resources, permissions
menu:
main:
parent: docker-cloud
@ -231,4 +232,4 @@ keys.
To create resources for an Organization, log in to Docker Cloud and switch to the
Organization account. Create the repositories, services, stacks, or node
clusters as you would for any other account.
clusters as you would for any other account.

5
docker-cloud/overview.md
View File

@ -1,6 +1,7 @@
---
description: Docker Cloud Overview
keywords: Docker, cloud, three
keywords:
- Docker, cloud, three
menu:
main:
parent: docker-cloud
@ -47,4 +48,4 @@ image, you can use it to produce containers, which make up a service, or use
Docker Cloud's stackfiles to combine it with other services and microservices,
to form a full application.
![](images/cloud-stack.png)
![](images/cloud-stack.png)

5
docker-cloud/release-notes.md
View File

@ -1,6 +1,7 @@
---
description: Docker Cloud
keywords: Docker, cloud, release, notes
keywords:
- Docker, cloud, release, notes
menu:
main:
parent: docker-cloud
@ -83,4 +84,4 @@ The following release notes document changes since [Tutum v0.19.5](https://suppo
### Known issues
- **Documentation screen captures** in most cases still reflect the Tutum interface and branding. We will update these and refresh the documentation as we go.
- **References to Tutum remain** in the documentation. We will update these and refresh the documentation as we go
- **References to Tutum remain** in the documentation. We will update these and refresh the documentation as we go

5
docker-cloud/slack-integration.md
View File

@ -2,7 +2,8 @@
aliases:
- /docker-cloud/tutorials/slack-integration/
description: Integrate with Slack
keywords: Slack, integrate, notifications
keywords:
- Slack, integrate, notifications
menu:
main:
parent: docker-cloud
@ -51,4 +52,4 @@ Enjoy your new Slack channel integration!
* From the Slack **Notifications** section you can also change the channel that the integration posts to. Click the reload icon (two arrows) next to the Slack integration to reopen the OAuth channel selector.
* Alternately, go to the <a href="https://slack.com/apps/manage" target="_blank">Slack App Management page</a> and search for "Docker Cloud". Click the result to see all of the Docker Cloud notification channels set for the Slack team.
* Alternately, go to the <a href="https://slack.com/apps/manage" target="_blank">Slack App Management page</a> and search for "Docker Cloud". Click the result to see all of the Docker Cloud notification channels set for the Slack team.

5
docker-for-mac/docker-toolbox.md
View File

@ -2,7 +2,8 @@
aliases:
- /mackit/docker-toolbox/
description: Docker for Mac and Docker Toolbox
keywords: mac, windows, alpha, beta, toolbox, docker-machine, tutorial
keywords:
- mac, windows, alpha, beta, toolbox, docker-machine, tutorial
menu:
main:
identifier: kit-toolbox
@ -128,4 +129,4 @@ You might decide that you do not need Toolbox now that you have Docker for Mac,
and want to uninstall it. For details on how to perform a clean uninstall of
Toolbox on the Mac, see [How to uninstall
Toolbox](/toolbox/toolbox_install_mac.md#how-to-uninstall-toolbox) in the
Toolbox Mac topics.
Toolbox Mac topics.

5
docker-for-mac/examples.md
View File

@ -1,6 +1,7 @@
---
description: Docker for Mac and Docker for Windows Tutorials
keywords: mac, windows, examples, Compose
keywords:
- mac, windows, examples, Compose
menu:
main:
identifier: docker-mac-examples
@ -21,4 +22,4 @@ For now, if you want get started experimenting with the Beta apps and Docker Com
- [Quickstart: Compose and Rails](/compose/rails/)
- [Quickstart: Compose and WordPress](/compose/wordpress/)
See also [learn by example](/engine/tutorials/index.md) tutorials on building images, running containers, networking, managing data, and storing images on Docker Hub.
See also [learn by example](/engine/tutorials/index.md) tutorials on building images, running containers, networking, managing data, and storing images on Docker Hub.

5
docker-for-mac/faqs.md
View File

@ -2,7 +2,8 @@
aliases:
- /mackit/faqs/
description: Frequently asked questions
keywords: mac faqs
keywords:
- mac faqs
menu:
main:
identifier: docker-mac-faqs
@ -154,4 +155,4 @@ 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).
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).

5
docker-for-mac/index.md
View File

@ -7,7 +7,8 @@ aliases:
- /docker-for-mac/started/
- /installation/mac/
description: Getting Started
keywords: mac, beta, alpha, tutorial
keywords:
- mac, beta, alpha, tutorial
menu:
main:
identifier: docker-mac-getstart
@ -284,4 +285,4 @@ ln -s /Applications/Docker.app/Contents/Resources/etc/docker-compose.bash-comple
* Check out the <a href="https://blog.docker.com/2016/06/docker-mac-windows-public-beta/">blog posts</a> on Docker for Mac and Docker for Windows public betas, and <a href="https://blog.docker.com/2016/03/docker-for-mac-windows-beta/">earlier posts</a> on the initial private beta.
* Please give feedback on your experience with the app and report bugs and problems by logging into our [Docker for Mac forum](https://forums.docker.com/c/docker-for-mac).
* Please give feedback on your experience with the app and report bugs and problems by logging into our [Docker for Mac forum](https://forums.docker.com/c/docker-for-mac).

5
docker-for-mac/multi-arch.md
View File

@ -2,7 +2,8 @@
aliases:
- /mackit/multi-arch/
description: Multi-CPU Architecture Support
keywords: mac, Multi-CPU architecture support
keywords:
- mac, Multi-CPU architecture support
menu:
main:
identifier: mac-multiarch
@ -32,4 +33,4 @@ Linux edd13885f316 4.1.12 #1 SMP Tue Jan 12 10:51:00 UTC 2016 ppc64le GNU/Linux
Running containers pre-configured with `qemu` has the advantage that you can use these to do builds `FROM`, so you can build new Multi-CPU architecture packages.
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.)
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.)

7
docker-for-mac/networking.md
View File

@ -2,7 +2,8 @@
aliases:
- /mackit/networking/
description: Networking
keywords: mac, networking
keywords:
- mac, networking
menu:
main:
identifier: mac-networking
@ -104,4 +105,6 @@ See the [run commmand](/engine/reference/commandline/run.md) for more details on
#### A view into implementation
We understand that these workarounds are not ideal, but there are several problems. In particular, there is a bug in macOS 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 macOS 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).
We understand that these workarounds are not ideal, but there are several problems. In particular, there is a bug in macOS 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 macOS 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).

6
docker-for-mac/opensource.md
View File

@ -1,6 +1,7 @@
---
description: Docker's use of Open Source
keywords: docker, opensource
keywords:
- docker, opensource
menu:
main:
identifier: opensource-mac
@ -19,4 +20,5 @@ details on the licensing, choose <img src="../images/whale-x.png"> -->
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).
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`.
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`.

5
docker-for-mac/osxfs.md
View File

@ -2,7 +2,8 @@
aliases:
- /mackit/osxfs/
description: OSXFS
keywords: mac, osxfs
keywords:
- mac, osxfs
menu:
main:
identifier: mac-osxfs
@ -338,4 +339,4 @@ engineering work on custom low-level components.
We appreciate your understanding as we continue development of the product and
work on all dimensions of performance. We want to continue to work with the
community on this, so please continue to report issues as you find them. We look
forward to collaborting with you on ideas and on the source code itself.
forward to collaborting with you on ideas and on the source code itself.

5
docker-for-mac/release-notes.md
View File

@ -2,7 +2,8 @@
aliases:
- /mackit/release-notes/
description: Change log / release notes per release
keywords: pinata, alpha, tutorial
keywords:
- pinata, alpha, tutorial
menu:
main:
identifier: docker-mac-relnotes
@ -985,4 +986,4 @@ work yet.
- Fixed setting hostname
- Fixed permissions on `usr/local` symbolic links
- Fixed permissions on `usr/local` symbolic links

5
docker-for-mac/troubleshoot.md
View File

@ -2,7 +2,8 @@
aliases:
- /mackit/troubleshoot/
description: Troubleshooting, logs, and known issues
keywords: mac, troubleshooting, logs, issues
keywords:
- mac, troubleshooting, logs, issues
menu:
main:
identifier: docker-mac-troubleshoot
@ -317,4 +318,4 @@ Alternatively you could create a plain-text TCP proxy on localhost:1234 using:
Then restart the NTP service with:
sudo launchctl unload /System/Library/LaunchDaemons/org.ntp.ntpd.plist
sudo launchctl load /System/Library/LaunchDaemons/org.ntp.ntpd.plist
sudo launchctl load /System/Library/LaunchDaemons/org.ntp.ntpd.plist

5
docker-for-windows/examples.md
View File

@ -1,6 +1,7 @@
---
description: Docker for Mac and Docker for Windows Tutorials
keywords: mac, windows, examples, Compose
keywords:
- mac, windows, examples, Compose
menu:
main:
identifier: docker-win-examples
@ -21,4 +22,4 @@ For now, if you want get started experimenting with the Beta apps and Docker Com
- [Quickstart: Compose and Rails](/compose/rails/)
- [Quickstart: Compose and WordPress](/compose/wordpress/)
See also [learn by example](/engine/tutorials/) tutorials on building images, running containers, networking, managing data, and storing images on Docker Hub.
See also [learn by example](/engine/tutorials/) tutorials on building images, running containers, networking, managing data, and storing images on Docker Hub.

5
docker-for-windows/faqs.md
View File

@ -1,6 +1,7 @@
---
description: Frequently asked questions
keywords: windows faqs
keywords:
- windows faqs
menu:
main:
identifier: docker-windows-faqs
@ -190,4 +191,4 @@ in [Troubleshooting](troubleshoot.md).
You might decide that you do not need Toolbox now that you have Docker for Windows, and want to uninstall it. For
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.
in the Toolbox Windows topics.

5
docker-for-windows/index.md
View File

@ -7,7 +7,8 @@ aliases:
- /docker-for-windows/started/
- /installation/windows/
description: Getting Started
keywords: windows, beta, alpha, tutorial
keywords:
- windows, beta, alpha, tutorial
menu:
main:
identifier: docker-win-getstart
@ -476,4 +477,4 @@ If you want to go back to using Docker Toolbox, you have to disable the Hyper-V
* Check out the <a href="https://blog.docker.com/2016/06/docker-mac-windows-public-beta/">blog posts</a> on Docker for Mac and Docker for Windows public betas, and <a href="https://blog.docker.com/2016/03/docker-for-mac-windows-beta/">earlier posts</a> on the initial private beta.
* Please give feedback on your experience with the app and report bugs and problems by logging into our [Docker for Windows forum](https://forums.docker.com/c/docker-for-windows).
* Please give feedback on your experience with the app and report bugs and problems by logging into our [Docker for Windows forum](https://forums.docker.com/c/docker-for-windows).

Some files were not shown because too many files have changed in this diff Show More