No Description

Joffrey F e35be8b0d4 Merge pull request #5770 from docker/bump-1.20.0-rc2 7 years ago
.circleci 742979371d Install both versions of python 7 years ago
bin 4652d3c38a Use newer versions of pre-commit hooks 8 years ago
compose 8c4af54257 Bump 1.20.0-rc2 7 years ago
contrib 9e42b50063 Add support for options added in 1.20.0 to bash completion 7 years ago
docs a8ff4285d1 updated README per vnext branch plan 9 years ago
experimental 07e2426d89 Remove doc on experimental networking support 9 years ago
project 7dfb856244 Better installation instruction in release notes 8 years ago
script 8c4af54257 Bump 1.20.0-rc2 7 years ago
tests ca012640c1 Preserve security_opt values in extends 7 years ago
.dockerignore c923ea1320 Some more test adjustments for Swarm support 8 years ago
.gitignore fbcc1510cc Handle giving help a nonexistent command 9 years ago
.pre-commit-config.yaml 4652d3c38a Use newer versions of pre-commit hooks 8 years ago
CHANGELOG.md 8c4af54257 Bump 1.20.0-rc2 7 years ago
CHANGES.md 478054af47 Rename CHANGES.md to CHANGELOG.md 10 years ago
CONTRIBUTING.md 981df93f12 Keep CONTRIBUTING.md information up to date 7 years ago
Dockerfile dce62c81d5 Remove obsolete code that slows down test execution 7 years ago
Dockerfile.armhf a0f78539b6 Test and build on 3.6 (replaces 3.4) ; dist 3.6-compiled binaries 7 years ago
Dockerfile.run 768e28ee30 Update Dockerfile.run to produce smaller image 7 years ago
Dockerfile.s390x cb2d65556b Use slim alpine instead of bulky debian 8 years ago
Jenkinsfile 632abe94c0 Parallelize Docker versions 7 years ago
LICENSE 99064d17dd Docker, Inc. 11 years ago
MAINTAINERS 74f5037f78 Add Joffrey to maintainers 8 years ago
MANIFEST.in bea2072b95 Add the git sha to version output 10 years ago
README.md ea64baa8fe Improve spelling in the README.md 7 years ago
SWARM.md a716bdc482 Update Swarm integration guide and make it an official part of the docs 9 years ago
appveyor.yml a0f78539b6 Test and build on 3.6 (replaces 3.4) ; dist 3.6-compiled binaries 7 years ago
docker-compose.spec 9dde4fff0e Add support for 3.6 schema and tmpfs mount size 7 years ago
logo.png 0bdbb33447 include logo in README 10 years ago
requirements-build.txt a0f78539b6 Test and build on 3.6 (replaces 3.4) ; dist 3.6-compiled binaries 7 years ago
requirements-dev.txt a0f78539b6 Test and build on 3.6 (replaces 3.4) ; dist 3.6-compiled binaries 7 years ago
requirements.txt 4d1dad24ae SDK version 3.1.1 7 years ago
setup.cfg 340a3fc09c enable universal wheels 8 years ago
setup.py 4d1dad24ae SDK version 3.1.1 7 years ago
tox.ini a0f78539b6 Test and build on 3.6 (replaces 3.4) ; dist 3.6-compiled binaries 7 years ago

README.md

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.