Detached `up` used to run create() then start() back to back: two separate daemon snapshots, the second blind to what the first just created or recreated. preparePlan already supports planning both phases in one pass (ScopeCreateStart, landed across lot 1) -- this wires it in for the one caller that can use it outright: `up -d`. preparePlan gains an explicit scope parameter (ScopeCreate for create(), unchanged); Up()'s detached branch now calls a new upDetached, which runs preparePlan(..., ScopeCreateStart) + executePlan once instead of create() + start(). --wait stays a post-plan verification: it re-lists containers after the plan runs (the plan may have created or recreated some, so the pre-execution snapshot can't be reused for this) and runs the same waitDependencies check start() already does. Interactive up is untouched: it still runs create() then start() with its printer/monitor listener wired in between, converging onto the plan engine separately (a riskier, later item of the same lot). ScopeCreateStart landed in lot 1 as inert code with no real caller; this is the first one, and it surfaced two latent bugs in the container-recreate path that nothing had exercised end to end before: - planRecreateContainer plans a container's recreation as Create (under a temporary "<shortID>_<name>" to avoid colliding with the old container still holding the final name) -> Stop -> Remove -> Rename(final name). The start phase's event naming and container-ID resolution (groupEventName, resolveContainerID) read the create node's published result by design (plannedReplica keeps every start-phase reference pointed at CreateNodeID, not the rename node), but execRenameContainer never updated that result after renaming -- so a recreated container's Starting/Started events kept reporting the temporary name forever. - execCreateContainer also publishes the new container into containersByService (the live view OpWaitCondition reads for depends_on health waits) under that same temporary name, with nothing refreshing it after rename either -- a dependent waiting on the recreated container's health reported Waiting/Healthy under the temporary name too. Both fixed in execRenameContainer: it now updates the create node's pctx result in place after a successful rename, and (via a new Service field on the rename Operation) patches the matching containersByService entry's name too. Each pinned by a regression test, verified by reverting the fix locally and confirming the test catches it. Verified with the full e2e suite (`go test -tags e2e ./pkg/e2e/...`) against a locally built binary -- including TestRestartWithDependencies, which is what caught both bugs in the first place -- plus the existing unit suite and lint. Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com> |
||
|---|---|---|
| .github | ||
| cmd | ||
| desktop-module | ||
| docs | ||
| internal | ||
| pkg | ||
| relay | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .go-version | ||
| .golangci.yml | ||
| AGENTS.md | ||
| AI_POLICY.md | ||
| BUILDING.md | ||
| CLAUDE.md | ||
| codecov.yml | ||
| CONTRIBUTING.md | ||
| docker-bake.hcl | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| logo.png | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
Table of Contents
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
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-pluginsOR/usr/local/libexec/docker/cli-plugins/usr/lib/docker/cli-pluginsOR/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:
- Define your app's environment with a
Dockerfileso it can be reproduced anywhere. - Define the services that make up your app in
compose.yamlso they can be run together in an isolated environment. - Lastly, run
docker compose upand 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.
