From 467c5c6389c2b66a47d8c23b1ccd37fa8f18ab45 Mon Sep 17 00:00:00 2001 From: ddeyo Date: Mon, 24 Sep 2018 13:57:50 -0700 Subject: [PATCH] topic work --- ee/ucp/deploy-application-package.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/ee/ucp/deploy-application-package.md b/ee/ucp/deploy-application-package.md index 5888ddbac1..accdc4306a 100644 --- a/ee/ucp/deploy-application-package.md +++ b/ee/ucp/deploy-application-package.md @@ -8,10 +8,14 @@ keywords: ucp, swarm, kubernetes, application > > This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice. -An application package has one of these formats: +In Docker 2.1 EE, an application package has one of these formats: - **Three-file format**: Defined by a metadata.yml, a docker-compose.yml, and a settings.yml files inside a `my-app.dockerapp` folder. This is also called the folder format. - **Single-file format**: Defined by a data from the previously three files concatenated in the order givem and separated by `---\n` in a single file named named 'my-app.dockerapp'. - **Image format**: Defined by a Docker image in the engine store or exported as a tarball. The docker-app binary lets a user render an application package to a Compose file using the settings values in the settings file or those specified by the user. This Compose file can then be deployed to a cluster running in Swarm mode or Kubernetes using `docker stack deploy` or to a single engine or Swarm classic cluster using `docker-compose up`. + +The docker-app binary also lets a user deploy an application package directly, essentially executing a `docker-app render` command followed by a `docker stack deploy` command. + +Once a stack has been deployed, you must use the `docker stack` or `docker-compose` commands to manipulate and manage the stack.