Define and run multi-container applications with Docker https://docs.docker.com/compose/
Find a file
Ian Campbell 6649e9aba3 tearDown the project override at the end of each test case
self._project.client is a docker.client.Client, so creating a new self._project
leaks (via the embedded connection pool) a bunch of Unix socket file
descriptors for each test which overrides self.project using this mechanism.

In my tests I observed the test harness using 800-900 file descriptor, which is
OK on Linux with the default limit of 1024 but breaks on OSX (e.g. with
Docker4Mac) where the default limit is only 256. The failure can be provoked on
Linux too with `ulimit -n 256`.

With this fix I have observed the process ending with ~100 file descriptors
open, including 83 Unix sockets, so I think there is likely at least one more
leak lurking.

Signed-off-by: Ian Campbell <ian.campbell@docker.com>
2016-07-20 14:34:12 +01:00
bin Rename binary to docker-compose and config file to docker-compose.yml 2015-01-20 21:00:23 +00:00
compose Merge pull request #3364 from TomasTomecek/3355-detailed-error-messages 2016-07-11 16:29:35 -04:00
contrib Merge pull request #3662 from albers/completion-bundle--fetch-digests 2016-07-07 10:39:18 -07:00
docs Add support for creating internal networks 2016-07-11 11:34:01 +02:00
experimental Update links 2015-12-21 01:52:54 +01:00
project Build osx binary on travis and upload to bintray. 2016-03-01 11:34:54 -05:00
script Upgrade pip on osx 2016-06-30 20:52:15 -04:00
tests tearDown the project override at the end of each test case 2016-07-20 14:34:12 +01:00
.dockerignore alpine docker image for running compose and a script to pull and run it with the 2015-10-02 11:38:35 -04:00
.gitignore Ignore extra coverge files 2015-12-10 15:29:36 -08:00
.pre-commit-config.yaml Tests use updated get_config_paths_from_options signature 2016-03-24 10:57:01 -07:00
.travis.yml Build osx binary on travis and upload to bintray. 2016-03-01 11:34:54 -05:00
appveyor.yml Move all build scripts to script/build 2016-02-24 16:24:13 -08:00
CHANGELOG.md Update install.md and CHANGELOG.md for 1.7.1 2016-07-07 11:41:11 -07:00
CHANGES.md Rename CHANGES.md to CHANGELOG.md 2015-08-14 11:27:27 +01:00
CONTRIBUTING.md Convert readthedocs links for their .org -> .io migration for hosted projects 2016-06-08 03:52:12 +01:00
docker-compose.spec Merge v1 config jsonschemas into a single file. 2016-02-24 15:59:10 -08:00
Dockerfile Upgade pip to latest 2016-04-26 11:58:41 -04:00
Dockerfile.run Pin base image to alpine:3.4 in Dockerfile.run 2016-07-06 18:01:27 -07:00
LICENSE Docker, Inc. 2014-07-24 10:24:17 -07:00
logo.png include logo in README 2015-09-15 09:17:00 +02:00
MAINTAINERS update maintainers file for parsing 2015-12-04 16:52:29 +01:00
MANIFEST.in Add the git sha to version output 2015-11-18 13:21:14 -05:00
README.md Readme should use new docker compose format instead of the old one 2016-04-14 10:49:10 +01:00
requirements-build.txt Upgrade pyinstaller. 2016-02-11 13:50:41 -05:00
requirements-dev.txt Use py.test as the test runner 2015-09-01 16:27:44 -04:00
requirements.txt Merge pull request #3661 from dnephin/fix_requirements 2016-06-30 18:21:40 -04:00
ROADMAP.md Prevent unnecessary inspection of containers when created from an inspect. 2016-04-06 11:14:42 -04:00
setup.py Update docker-py version in requirements 2016-06-28 15:49:06 -07:00
SWARM.md Update Swarm integration guide and make it an official part of the docs 2016-02-19 09:32:43 -08:00
tox.ini Merge pull request #2388 from dnephin/fix_long_lines 2016-02-25 16:52:33 -08: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:

version: '2'

services:
  web:
    build: .
    ports:
     - "5000:5000"
    volumes:
     - .:/code
  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.