Upstream software project

docker-compose

Define and run multi-container applications with Docker

About docker-compose

Define and run multi-container applications with Docker

This project links 6 native package records across 6 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

docker-compose repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 15.6: 1 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.docker-compose: recorded package coverageDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Leap 15.61 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
docker-compose
Publisher
Not authoritatively mapped
Native package records
6
Operating systems
debian-13, fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
Apache-2.0
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

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 the 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.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 13 (Trixie)

  1. Package docker-compose

    trixie (Debian 13 (Trixie)) (admin): Define and run multi-container applications with Docker (program)

    2.26.1-4: amd64 arm64

Fedora 43

  1. Package docker-compose

    43 (Fedora 43) (Unspecified): Define and run multi-container applications with Docker

    5.3.1-1.fc43: aarch64 x86_64

    Source: docker-compose

Fedora 44

  1. Package docker-compose

    44 (Fedora 44) (Unspecified): Define and run multi-container applications with Docker

    5.5.0-1.fc44: aarch64 x86_64

    Source: docker-compose

openSUSE Leap 15.6

  1. Package docker-compose

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Define and run multi-container applications with Docker

    2.22.0-bp156.1.11: aarch64 ppc64le s390x x86_64

    Source: docker-compose

openSUSE Leap 16.0

  1. Package docker-compose

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Define and run multi-container applications with Docker

    2.33.1-160000.3.2: aarch64 ppc64le s390x x86_64

    Source: docker-compose

openSUSE Tumbleweed

  1. Package docker-compose

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Define and run multi-container applications with Docker

    5.5.0-1.1: x86_64

    Source: docker-compose

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.