Nicolas De Loof
27c9a231ea
get-relay-info answers pointed a locally-bound provider at one of the dependents' own networks: shared infrastructure every other service on it could also reach, and no more isolated than any project bridge. Provision a dedicated, internal:true bridge network scoped to that one provider service instead, created only when the provider itself sends get-relay-info -- the provider's own declaration that it binds locally, never for a provider backing a remote resource. The relay container joins it alongside the dependents' networks it already joins; it is torn down with the relay on endpoint changes and on down, including the no-compose-file down path. The network's lifecycle is hardened against the races a shared, project-scoped resource runs into: - a NetworkCreate conflict on the deterministic name re-checks by label (not just by name) before adopting the existing network, so a genuine name clash with an unrelated, user-declared network fails loudly instead of being silently adopted into the relay's isolation boundary; - a NotFound gateway lookup after losing that conflict falls back to an unresolved answer instead of propagating the error; - removeRelayLinkNetwork and ensureRelayLinkNetworksDown both tolerate a NetworkRemove conflict from the daemon's asynchronous endpoint disconnect, which can race the relay container's own removal; - ensureRelayLinkNetworksDown accumulates failures with errors.Join across every relay-link network of a project instead of aborting on the first one, and skips (warn-only) a network that still has active endpoints, mirroring removeNetwork's existing tolerance for regular project networks. docs/extension.md documents that the "desktop" network name in the get-relay-info answer (under Docker Desktop) is an opaque placeholder, never a real Docker network a provider can inspect or connect to. Signed-off-by: Nicolas De Loof <[email protected]>
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
: 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-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.