Docker Compose
Tool that defines a multi-container application in a YAML file and starts it on one Docker host with the command docker compose up.
| ID | docker-compose |
| Layer | orchestration |
| Version | v5.8.0 |
| Tiers | T1, T2 |
| Requires | nothing |
| License | Apache-2.0 |
| Evidence | docs |
| Last verified | 2026-11-21 |
Choose it when
Section titled “Choose it when”- The system runs on one host and its services are described in one YAML file: the Compose documentation says the easiest way to deploy an application is to run it on a single server (Use Compose in production page), and the features page says Compose supports production deployments on single hosts.
Avoid it when
Section titled “Avoid it when”- A service must be spread over several hosts: the production page says to run Compose apps on a Swarm cluster to scale up, while the repository README says Swarm is not maintained by Docker Inc and some Compose features are not accessible to Swarm users; this entry does not resolve the two statements, and K3s is the catalog’s alternative.
Caveats
Section titled “Caveats”- Docker Engine and the Docker CLI are outside the catalog: the Linux plugin page says its instructions assume Docker Engine and Docker CLI are already installed, and the container engine, its images and the operating system’s package source have no entry here. Compose does not start containers itself; it talks to the engine.
- GPUs: the Compose GPU page says services reserve GPUs with the deploy.resources.reservations.devices attribute (capabilities is required; count or device_ids; driver, for example nvidia) and that the host must contain such devices and the Docker daemon must be set accordingly. The Docker Engine GPU page names the NVIDIA drivers and the NVIDIA Container Toolkit as the prerequisites for NVIDIA GPUs. The drivers, the container toolkit and their packages and images are outside the catalog, and no AMD or Intel GPU documentation was found on the Compose GPU page (it covers NVIDIA only).
- No paid edition or license check of Compose itself was found in the documentation read; Docker Desktop, which the installation overview recommends, is a separate product with its own terms and is not part of this entry.
Alternatives
Section titled “Alternatives”Carrying it in
Section titled “Carrying it in”No container images.
Packages:
- docker-compose-linux-x86_64
Downloads at run time
Section titled “Downloads at run time”What the software tries to fetch while it runs, and how to stage it instead.
- Images of the application: the Compose file names the images, and docker compose up pulls the ones that are not in the engine’s image cache from their registry (pull_policy missing is the default when the Compose file has no build section; the latest tag is always pulled even then). In an air-gapped site, load the images into the engine beforehand (or push them to an internal registry and name that registry in the Compose file) and set pull_policy to never for a service to make Compose fail instead of reaching out (container-spec reference).
License server
Section titled “License server”No license server is contacted.
Offline behavior is documented but not verified: the entry author did not run Compose, and the installation pages do not describe an offline procedure (searching the Compose pages of docker/docs at the cited commit and the repository README and docs at the tag for air-gap, offline and disconnected found no occurrence; the Docker Engine installation pages mention air-gapped systems only for installing from downloaded packages). The files in airgap.packages are for linux/amd64 (x86_64) hosts. The manual plugin installation on the Linux plugin page downloads docker-compose-linux-x86_64 and saves it as the file docker-compose in the directory $HOME/.docker/cli-plugins (current user) or /usr/local/lib/docker/cli-plugins (all users), then applies chmod +x; the README of the repository at the tag adds that the binary is copied under the name docker-compose into one of /usr/local/lib/docker/cli-plugins, /usr/local/libexec/docker/cli-plugins, /usr/lib/docker/cli-plugins or /usr/libexec/docker/cli-plugins. The legacy standalone installation (marked not recommended by the page) saves the same file as /usr/local/bin/docker-compose and is run as docker-compose instead of docker compose. Files for other architectures, named by the release: docker-compose-linux-aarch64, docker-compose-linux-armv6, docker-compose-linux-armv7, docker-compose-linux-ppc64le, docker-compose-linux-riscv64 and docker-compose-linux-s390x; the Linux plugin page says to replace x86_64 in the file name with the architecture wanted from the releases page. The release also publishes, for each binary, a .sha256 file, .sigstore.json, .provenance.json and .sbom.json file, and one checksums.txt; the installation pages name none of them, so they are not listed in packages. Other install route, not a carry item of this entry: the Docker Engine installation pages for Ubuntu and Debian list docker-compose-plugin_<version><arch>.deb among the packages to download and install with dpkg (amd64, armhf, arm64 or s390x directories under pool/stable/) and the CentOS page describes downloading rpm files; the pages do not say which Compose version a given package contains. Windows binaries (docker-compose-windows-x86_64.exe and docker-compose-windows-aarch64.exe) and macOS binaries are published and not relevant to a Linux design. No image of Compose itself is named by the installation pages. In the release v5.8.0 notes, scheduled jobs need Docker Engine 29.10 or later with the jobs extension enabled (off by default); manual jobs work on any engine. The installation pages name no minimum Docker Engine version. Outbound calls: no telemetry, analytics or update-check documentation was found on 2026-11-21 (searched the Compose pages of docker/docs and the repository at the tag for telemetry, analytics, usage statistics, phone home, update check and DO_NOT_TRACK; a search is not proof of absence); vet before adoption. From the source code (not a documentation page): internal/tracing/tracing.go in v5.8.0 exports OpenTelemetry traces only when an OTEL*ENDPOINT environment variable is set or the active Docker context carries an otel endpoint in its metadata (the code dials that endpoint through a local Unix socket or named pipe, the integration with Docker Desktop); nothing is exported otherwise.
Evidence
Section titled “Evidence”All values were read on 2026-11-21 from the pages in sources. The version v5.8.0 is the latest GitHub release (published 2026-11-17, not a prerelease); the file names under airgap.packages are the release assets listed by the GitHub API for that release. The docker/docs repository has no recent tags, so its pages are cited at commit 747e4c7528c703b357b1ae83cbbf411229ce59d2 (the head of main on 2026-11-21); the repository pages at the tag v5.8.0 are cited for the README, the license and the source code. The installation pages in that commit take the version from the Hugo setting compose_version, which is v5.6.0 there (hugo.yaml), so the commands on the rendered pages name v5.6.0 while the latest release is v5.8.0: this entry names v5.8.0 and the file names are the same for both. Compose was not run by the entry author: the offline behavior is documented only in the sense given in airgap.notes, and is not verified in a disconnected network.
Sources:
- https://api.github.com/repos/docker/compose/releases/latest
- https://github.com/docker/compose/releases/tag/v5.8.0
- https://api.github.com/repos/docker/compose/releases/tags/v5.8.0
- https://api.github.com/repos/docker/compose/license
- https://github.com/docker/compose/blob/v5.8.0/LICENSE
- https://github.com/docker/compose/blob/v5.8.0/README.md
- https://github.com/docker/compose/blob/v5.8.0/internal/tracing/tracing.go
- https://github.com/docker/compose/blob/v5.8.0/internal/tracing/docker_context.go
- https://github.com/docker/docs/blob/747e4c7528c703b357b1ae83cbbf411229ce59d2/content/manuals/compose/install/_index.md
- https://github.com/docker/docs/blob/747e4c7528c703b357b1ae83cbbf411229ce59d2/content/manuals/compose/install/linux.md
- https://github.com/docker/docs/blob/747e4c7528c703b357b1ae83cbbf411229ce59d2/content/manuals/compose/install/standalone.md
- https://github.com/docker/docs/blob/747e4c7528c703b357b1ae83cbbf411229ce59d2/hugo.yaml
- https://github.com/docker/docs/blob/747e4c7528c703b357b1ae83cbbf411229ce59d2/content/manuals/compose/how-tos/gpu-support.md
- https://github.com/docker/docs/blob/747e4c7528c703b357b1ae83cbbf411229ce59d2/content/manuals/compose/how-tos/production.md
- https://github.com/docker/docs/blob/747e4c7528c703b357b1ae83cbbf411229ce59d2/content/manuals/compose/intro/features-uses.md
- https://github.com/docker/docs/blob/747e4c7528c703b357b1ae83cbbf411229ce59d2/content/manuals/engine/containers/gpu.md
- https://github.com/docker/docs/blob/747e4c7528c703b357b1ae83cbbf411229ce59d2/content/manuals/engine/install/ubuntu.md
- https://github.com/docker/docs/blob/747e4c7528c703b357b1ae83cbbf411229ce59d2/content/manuals/engine/install/centos.md
- https://github.com/docker/docs/blob/747e4c7528c703b357b1ae83cbbf411229ce59d2/content/reference/compose-file/container-spec.md
Source of this page: skills/airgap-architect/catalog/components/docker-compose.toml.