Nicolas De LoofandClaude Fable 5 0ac224d9d9 test(e2e): Files() declares multi-file projects as a txtar archive
A scenario could only declare a lone compose.yaml; anything needing a
Dockerfile, an env file or a config file fell back to fixture
directories, breaking the "self-contained in the test source" rule.

Files() takes the project files as a txtar archive
(golang.org/x/tools/txtar, already in the module graph): each file
introduced by a `-- name --` line, extracted into the project
directory. txtar is the format Go's own cmd/go tests are written in —
diff-friendly, and one every human and coding agent already knows by
heart, which is the point: e2e scenarios are the main reading surface
between the two.

TestUpBuildUnchangedContext demonstrates the need — compose.yaml +
Dockerfile + a copied file — and locks a real invariant: an unchanged
`up --build` hits the build cache and must not recreate the service.
Project() is exposed so a scenario can Defer removal of the image it
built.

Co-Authored-By: Claude Fable 5 <[email protected]>
Signed-off-by: Nicolas De Loof <[email protected]>
2026-08-18 11:18:22 +02:00
2026-06-29 20:56:31 +02:00
2026-08-14 14:20:41 +02:00
2026-08-14 14:20:41 +02:00
2020-08-17 10:20:49 +02:00
2026-08-17 11:09:19 +02:00
2026-07-16 11:39:14 +02:00

Table of Contents

Docker Compose

GitHub release PkgGoDev Build Status 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.

Note

: About Docker Swarm Docker Swarm used to rely on the legacy compose file format but did not adopt the compose specification so is missing some of the recent enhancements in the compose syntax. After acquisition by Mirantis swarm isn't maintained by Docker Inc, and as such some Docker Compose features aren't accessible to swarm users.

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 compose.yaml 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.

Legacy

The Python version of Compose is available under the v1 branch.

S
Description
Define and run multi-container applications with Docker
Readme Apache-2.0
58 MiB
Languages
Go 98.6%
Dockerfile 0.9%
Makefile 0.3%
HCL 0.2%