Docker Compose v5 requires buildx

[ndeloof]

Next Compose release (v5.0.0) will require Buildx to run compose build and compose up --build commands

also removed duplicated entry in deb/control

[crazy-max]

https://github.com/docker/packaging/actions/runs/19368420725/job/55417636835?pr=311#step:9:407

I think we need to update the verify step, I will take a look

[thaJeztah]

Did you remove this deliberately? I think it's recommended (or even mandatory) to include it (as it's not a debian system package that's required)

[ndeloof]

it was declared twice in this file

[thaJeztah]

Ah! Thanks I didn't spot that 👍

[thaJeztah]

Same question for this one; was this removed on purpose?

[ndeloof]

same, already set on the top of this file

[thaJeztah]

So I'm wondering is if we should make it Requires; bare with me;

• Recommends is already a strong dependency; package managers by default will install the dependency
• BUT allow explicitly opting-out (--no-install-recommends)
• For the docker CLI we have Recommends for buildx and compose; in most setups, this means that installing the CLI will also install compose and buildx UNLESS explicitly opted-out;

  packaging/pkg/docker-cli/deb/control

  Lines 19 to 21 in 91070db

  	Recommends: docker-buildx-plugin,
  	docker-compose-plugin
  	Suggests: docker-model-plugin

The opt-out option allows a more minimal setup, for example in a production environment where containers are deployed from images that exist in the registry, but never expected to be built. Making buildx Required for compose means that implicitly the Recommends in the CLI is also changed to Required;

• Without buildx installed, is compose able to do a docker compose up if the compose-file doesn't have a build ?
• What does docker compose up do if the image referenced is available in the registry, and no explicit --build is passed on docker compose up ?
• ☝️ this would be in a scenario where the compose file has a build, but only intended for developer situations, and in production it would not do a build, only a docker pull of the image(s) referenced.

[thaJeztah]

cc @tianon perhaps you have thoughts as well with your insight in common recommendations for this from a packaging perspective.

[tianon]

Agreed that what Debian calls "Recommends" is the appropriate relationship here:

https://www.debian.org/doc/debian-policy/ch-relationships.html#binary-dependencies-depends-recommends-suggests-enhances-pre-depends

Recommends

This declares a strong, but not absolute, dependency.

The Recommends field should list packages that would be found together with this one in all but unusual installations.