[master] add docker-compose-plugin package (deb, rpm)

[thaJeztah]

depends on:

• [master] CentOS 8: switch to use centos 8 stream (quay.io/centos/centos:stream8) #621

Adds a package for the docker-compose cli plugin

with this:

dpkg -i ./docker-ce-cli_0.0.0-20210629140245-4a6fe51-0~ubuntu-focal_amd64.deb
dpkg -i ./docker-compose-plugin_2.0.0-beta.6~ubuntu-focal_amd64.deb

docker info --format '{{json .ClientInfo.Plugins}}' | jq .
[
  {
    "SchemaVersion": "0.1.0",
    "Vendor": "Docker Inc.",
    "Version": "v0.5.1-docker",
    "ShortDescription": "Build with BuildKit",
    "Name": "buildx",
    "Path": "/usr/libexec/docker/cli-plugins/docker-buildx"
  },
  {
    "SchemaVersion": "0.1.0",
    "Vendor": "Docker Inc.",
    "Version": "v2.0.0-beta.6",
    "ShortDescription": "Docker Compose",
    "Name": "compose",
    "Path": "/usr/libexec/docker/cli-plugins/docker-compose"
  }
]

rpm -i \
    ./docker-ce-cli-0.0.0.20210702143511.f782d13-0.el8.x86_64.rpm \
    ./docker-scan-plugin-0.8.0-0.el8.x86_64.rpm \
    ./docker-compose-plugin-2.0.0.beta.6-0.el8.x86_64.rpm

docker info --format '{{json .ClientInfo.Plugins}}' | jq .
[
  {
    "SchemaVersion": "0.1.0",
    "Vendor": "Docker Inc.",
    "Version": "v0.5.1-docker",
    "ShortDescription": "Build with BuildKit",
    "Name": "buildx",
    "Path": "/usr/libexec/docker/cli-plugins/docker-buildx"
  },
  {
    "SchemaVersion": "0.1.0",
    "Vendor": "Docker Inc.",
    "Version": "v2.0.0-beta.6",
    "ShortDescription": "Docker Compose",
    "Name": "compose",
    "Path": "/usr/libexec/docker/cli-plugins/docker-compose"
  },
  {
    "SchemaVersion": "0.1.0",
    "Vendor": "Docker Inc.",
    "Version": "v0.8.0",
    "ShortDescription": "Docker Scan",
    "Name": "scan",
    "Path": "/usr/libexec/docker/cli-plugins/docker-scan"
  }
]

[thaJeztah]

We really need to update the Dockerfiles to include the source-code in an (intermediate) stage, instead of bind-mounting from the host. Especially with go modules, we should cache those.

[thaJeztah]

Will now push a commit to (temporarily) ignore the difference

Removed the temporary fix, because v2.0.0-beta.5 was tagged, which removes the v prefix https://github.com/docker/compose-cli/releases/tag/v2.0.0-beta.5

[rfay]

Is there going to be a way to use this as docker-compose on Linux? (Request at https://github.com/docker/compose-cli/issues/2012)

Interesting that this is being done in docker-ce-packaging repo.

[thaJeztah]

Is there going to be a way to use this as docker-compose on Linux? (Request at docker/compose-cli#2012)

On linux, we could document creating an alias;

alias docker-compose="docker compose"

or to set it automatically for new sessions (for Bash)

echo 'alias docker-compose="docker compose"' >> ~/.bashrc

Or zsh:

echo 'alias docker-compose="docker compose"' >> ~/.zshrc

I don't think those will/should be set automatically, because the linux packages current do not install docker-compose (and it would "conflict" with docker-compose installs installed through other means), but we can document.

Interesting that this is being done in docker-ce-packaging repo.

Yeah, the release pipeline for Linux packages is quite complex (this repository and https://github.com/docker/containerd-packaging are only a small bit of the release pipeline); currently the CLI plugins are packaged in the same pipeline / pipeline-steps as the docker cli, also because for most plugins we consider them "being a plugin" an intermediate stage (and the functionality to be ultimately rolled into the docker cli itself, not as a separate binary).

[thaJeztah]

If you take the .bashrc or zshrc approach, that file needs to be "reloaded" to take effect for the current shell, by sourcing it;

source ~/.bashrc

source ~/.zshrc

[rfay]

I replied in https://github.com/docker/compose-cli/issues/2012#issuecomment-906367152 - a wrapper of some type really is required. Most of these usages aren't logged in users, think CI and a dozen other contexts. We're not talking about personal accounts that can be adjusted to make an alias work. We need a distributed wrapper named docker-compose that does what it needs to do.

[thaJeztah]

wrt to aliasing docker-compose to docker compose, would it make sense/be possible to use the alternatives system?

Hmm.. that's indeed an interesting idea. I must admit I've never looked into that, but it appears there's (at least for deb package) a helper dh_installalternatives