Žiadny popis

Guillaume Lours 508d71c5df ci: fix merge workflow (#10685) 2 rokov pred
.github 508d71c5df ci: fix merge workflow (#10685) 2 rokov pred
cmd 3c8a56dbf3 trace: add OTEL initialization (#10526) 2 rokov pred
docs 65b714c108 fix build issue 2 rokov pred
e2e 2ca8ab914a e2e: make test re-runnable on the same machine 2 rokov pred
internal 3c8a56dbf3 trace: add OTEL initialization (#10526) 2 rokov pred
packaging 2aea82a7c6 packaging: Add EULA 5 rokov pred
pkg e63ab14b1e ci: merge Go coverage reports before upload (#10666) 2 rokov pred
.dockerignore 5ec20296e4 Better sandboxed workflow and enhanced cross compilation 3 rokov pred
.gitattributes 93984f8c68 Removed test requiring linux containers 5 rokov pred
.gitignore 85ddfde5d6 use go 1.20 -cover support 3 rokov pred
.golangci.yml be6c9565e3 ci: bump golangci-lint to v1.53.x (#10659) 2 rokov pred
BUILDING.md 06e71371ff docs: fix grammatical issues (#9997) 3 rokov pred
CONTRIBUTING.md 2bef9769e5 Broken Link fixed in compose docs 3 rokov pred
Dockerfile e63ab14b1e ci: merge Go coverage reports before upload (#10666) 2 rokov pred
LICENSE d7d9bb28bb Add LICENSE and NOTICE files 5 rokov pred
MAINTAINERS 97752b23e8 refresh Maintainers list 3 rokov pred
Makefile e63ab14b1e ci: merge Go coverage reports before upload (#10666) 2 rokov pred
NOTICE 1ae9b3cb5d move compose-cli code into docker/compose/v2 4 rokov pred
README.md c342891f3e Squashed commit of the following: 3 rokov pred
codecov.yml e63ab14b1e ci: merge Go coverage reports before upload (#10666) 2 rokov pred
docker-bake.hcl e63ab14b1e ci: merge Go coverage reports before upload (#10666) 2 rokov pred
go.mod 0a9b9fd8fe build(deps): bump github.com/Microsoft/go-winio from 0.5.2 to 0.6.1 2 rokov pred
go.sum 0a9b9fd8fe build(deps): bump github.com/Microsoft/go-winio from 0.5.2 to 0.6.1 2 rokov pred
logo.png 1ae9b3cb5d move compose-cli code into docker/compose/v2 4 rokov pred

README.md

Table of Contents

GitHub release PkgGoDev Build Status Go Report Card Codecov OpenSSF Scorecard Docker Compose

Docker Compose is a tool for running multi-container applications on Docker defined using the Compose file format. A Compose file is used to define how one or more containers that make up your application are configured. Once you have a Compose file, you can create and start your application with a single command: docker compose up.

About update and backward compatibility

Docker Compose V2 is a major version bump release of Docker Compose. It has been completely rewritten from scratch in Golang (V1 was in Python). The installation instructions for Compose V2 differ from V1. V2 is not a standalone binary anymore, and installation scripts will have to be adjusted. Some commands are different.

For a smooth transition from legacy docker-compose 1.xx, please consider installing compose-switch to translate docker-compose ... commands into Compose V2's docker compose ..... Also check V2's --compatibility flag.

Where to get Docker Compose

Windows and macOS

Docker Compose is included in Docker Desktop for Windows and macOS.

Linux

You can download Docker Compose binaries from the release page on this repository.

Rename the relevant binary for your OS to docker-compose and copy it to $HOME/.docker/cli-plugins

Or copy it into one of these folders to install it system-wide:

  • /usr/local/lib/docker/cli-plugins OR /usr/local/libexec/docker/cli-plugins
  • /usr/lib/docker/cli-plugins OR /usr/libexec/docker/cli-plugins

(might require making the downloaded file executable with chmod +x)

Quick Start

Using Docker Compose is 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 Compose file looks like this:

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

Contributing

Want to help develop Docker Compose? Check out our contributing documentation.

If you find an issue, please report it on the issue tracker.