Daniel Nephin 7fc577c31d Remove name from config schema.
Refactors config validation of a service to use a ServiceConfig data object.
Instead of passing around a bunch of related scalars, we can use the
ServiceConfig object as a parameter to most of the service validation functions.

This allows for a fix to the config schema, where the name is a field in the
schema, but not actually in the configuration. My passing the name around as
part of the ServiceConfig object, we don't need to add it to the config options.
Fixes #2299

validate_against_service_schema() is moved from a conditional branch in
ServiceExtendsResolver() to happen as one of the last steps after all
configuration is merged. This schema only contains constraints which only need
to be true at the very end of merging.

Signed-off-by: Daniel Nephin <dnephin@docker.com>
2015-11-12 13:54:41 -05:00
2015-11-12 13:54:41 -05:00
2015-11-12 13:54:41 -05:00
2015-06-22 08:44:41 -07:00
2015-11-03 12:36:30 -05:00
2015-11-12 13:54:41 -05:00
2015-10-07 14:54:05 -04:00
2015-11-03 12:36:30 -05:00
2015-08-14 11:27:27 +01:00
2015-09-02 18:09:34 -07:00
2014-07-24 10:24:17 -07:00
2015-09-15 09:17:00 +02:00
2015-07-01 15:38:07 +01:00
2015-11-12 13:54:39 -05:00
2015-10-14 11:18:21 -04:00
2015-06-15 15:19:55 -07:00

Docker Compose

Docker Compose

Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a Compose file to configure your application's services. Then, using a single command, you create and start all the services from your configuration. To learn more about all the features of Compose see the list of features.

Compose is great for development, testing, and staging environments, as well as CI workflows. You can learn more about each case in Common Use Cases.

Using Compose is basically a three-step process.

  1. Define your app's environment with a Dockerfile so it can be reproduced anywhere.
  2. Define the services that make up your app in docker-compose.yml so they can be run together in an isolated environment:
  3. Lastly, run docker-compose up and Compose will start and run your entire app.

A docker-compose.yml looks like this:

web:
  build: .
  ports:
   - "5000:5000"
  volumes:
   - .:/code
  links:
   - redis
redis:
  image: redis

For more information about the Compose file, see the Compose file reference

Compose has commands for managing the whole lifecycle of your application:

  • Start, stop and rebuild services
  • View the status of running services
  • Stream the log output of running services
  • Run a one-off command on a service

Installation and documentation

Contributing

Build Status

Want to help build Compose? Check out our contributing documentation.

Releasing

Releases are built by maintainers, following an outline of the release process.

Description
Define and run multi-container applications with Docker
Readme Apache-2.0 51 MiB
Languages
Go 97.1%
Dockerfile 2%
Makefile 0.5%
HCL 0.3%