Keine Beschreibung

Joffrey F 265d9dae4b Update zsh completion with new options, and ensure service names are properly retrieved vor 7 Jahren
.circleci 5ad50dc0b3 Bump Python SDK -> 3.5.0 vor 7 Jahren
bin 0c4fc93895 Use newer versions of pre-commit hooks vor 8 Jahren
compose 373c83ccd7 Fix some typo vor 7 Jahren
contrib 265d9dae4b Update zsh completion with new options, and ensure service names are properly retrieved vor 7 Jahren
docs 7d68d4bb44 missing "is" vor 8 Jahren
experimental 07e2426d89 Remove doc on experimental networking support vor 9 Jahren
project 7536c331e0 Document new release process vor 7 Jahren
script d491a81cec Skip testing TPs/betas for now vor 7 Jahren
tests db391c03ad Merge pull request #6100 from docker/5960-parallel-pull-progress vor 7 Jahren
.dockerignore 6a4adb64f9 Some more test adjustments for Swarm support vor 8 Jahren
.gitignore 541fb65259 Add --hash opt for config command vor 7 Jahren
.pre-commit-config.yaml 0c4fc93895 Use newer versions of pre-commit hooks vor 8 Jahren
CHANGELOG.md b66782b412 Fix typos in CHANGELOG vor 7 Jahren
CHANGES.md 478054af47 Rename CHANGES.md to CHANGELOG.md vor 10 Jahren
CONTRIBUTING.md 981df93f12 Keep CONTRIBUTING.md information up to date vor 8 Jahren
Dockerfile dce62c81d5 Remove obsolete code that slows down test execution vor 8 Jahren
Dockerfile.armhf a0f78539b6 Test and build on 3.6 (replaces 3.4) ; dist 3.6-compiled binaries vor 8 Jahren
Dockerfile.run 3a93e85762 Fix broken url vor 7 Jahren
Dockerfile.s390x b2a03265e4 Use slim alpine instead of bulky debian vor 8 Jahren
Jenkinsfile 5ad50dc0b3 Bump Python SDK -> 3.5.0 vor 7 Jahren
LICENSE 99064d17dd Docker, Inc. vor 11 Jahren
MAINTAINERS 06593110dc Fix indentation + HOF comment vor 8 Jahren
MANIFEST.in d4b9845201 Add the git sha to version output vor 10 Jahren
README.md 95005e6c03 Improve spelling in the README.md vor 8 Jahren
SWARM.md 520c695bf4 Update Swarm integration guide and make it an official part of the docs vor 10 Jahren
appveyor.yml 5ad50dc0b3 Bump Python SDK -> 3.5.0 vor 7 Jahren
docker-compose.spec 025fb7f860 Add composefile v3.7 vor 7 Jahren
logo.png 0bdbb33447 include logo in README vor 10 Jahren
requirements-build.txt a0f78539b6 Test and build on 3.6 (replaces 3.4) ; dist 3.6-compiled binaries vor 8 Jahren
requirements-dev.txt 5ad50dc0b3 Bump Python SDK -> 3.5.0 vor 7 Jahren
requirements.txt 5ad50dc0b3 Bump Python SDK -> 3.5.0 vor 7 Jahren
setup.cfg 2648af6807 enable universal wheels vor 9 Jahren
setup.py 5ad50dc0b3 Bump Python SDK -> 3.5.0 vor 7 Jahren
tox.ini 5ad50dc0b3 Bump Python SDK -> 3.5.0 vor 7 Jahren

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.