Skip to content

Future strategy for Docker Compose (binary vs library) and Docker Buildx #7915

@stasadev

Description

@stasadev

docker-compose v5.0.0 is out https://github.com/docker/compose/releases/tag/v5.0.0

  • There is new Go SDK for Compose, using it is going to give us more control on the internal logic.
  • docker-compose v5.0.0 binary is 2.5 times smaller than v2.40.3
  • docker-compose v2.40.2 introduced minimal required version for docker-buildx fail build if minimal required version of buildx isn't installed docker/compose#13295
  • Debian Trixie 13 uses docker-buildx v0.13.1, which doesn't meet that requirement, users need to install Docker from their repos - it may be confusing.
  • We may use a private docker-buildx to bypass all restrictions for LTS distros

We should decide the path we're going to continue with:

  1. Investigate if Go SDK has a requirement for minimal docker-buildx, if it doesn't have it, it'll be ideal for us.
  2. Considering that docker-compose v5.0.0 is much smaller now, it's preferred to use it.
  3. If we want to have widespread support including users of Debian Trixie 13, we could downgrade to docker-compose v2.40.1
  4. Investigate if we can bundle docker-buildx in the same way as we bundle docker-compose

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions