Support for docker compose v2.0.0 incl. using dock binary instead of docker-compose

[Ross-Duckworth-Pharos]

The recently released Docker Compose V2 (https://github.com/docker/compose/releases/tag/v2.0.0) introduces the following change: container names use hyphens to produce a valid hostname

This breaks the container name parsing in ExtractName in Ductus.FluentDocker/Services/Impl/DockerComposeCompositeService.cs which assumes underscores are being used (now hyphens are).

[mariotoffia]

Hi @Ross-Duckworth-Pharos and thanks for reporting this!

I will add the possibility to AssumeComposeVersion / AutoDetect so it could use different strategies depending on version.

(another task is actually to allow for docker compose command as well.

Cheers,
Mario :)

[psavva]

Docker-Compose v1 has been deprecated, and we should all switch to docker compose v2

Any ideas as to when this can be supported?

[psavva]

As a potential quick fix:
alias docker-compose="docker compose"

edit: Ductus.FluentDocker.Common.FluentDockerException: Could not resolve binary docker-compose is it installed on the local system?
I'm not able to get FluentDocker to work with the alias....

[adamf-dp]

Docker-Compose v1 has been deprecated, and we should all switch to docker compose v2

Any ideas as to when this can be supported?

Docker provide Compose Switch, which translates calls made to the old V1 docker-compose command to the new V2 docker compose - however, the container name parsing is still broken due to the issue mentioned in the original post.

This PR allows the compose version to be specified to ensure the correct parsing logic is used, which combined with Compose Switch means FluentDocker is able to work with the latest Compose version.

[jchannon]

Just hit this same issue, is there a path forward

[mariotoffia]

There's a setting so you can specify the compose version ComposeVersion.V2. For example in the fluent API:

AssumeComposeVersion(ComposeVersion.V2)

Default is Unknown and hence falls back to V1 behavoiur. This behaviour will be deprecated and migrated to default as V2 this year.

Cheers,
Mario :)

[cvicenti-apr]

This does not seem to work when passing a docker-compose.yml file through DockerComposeCompositeService.
I'm using the following:

new DockerComposeCompositeService(
                DockerHost,
                new DockerComposeConfig
                {
                    ComposeFilePath = [filePath],
                    ForceRecreate = true,
                    RemoveOrphans = true,
                    StopOnDispose = true,
                    ComposeVersion = ComposeVersion.V2,
                    TimeoutSeconds = TimeSpan.FromSeconds(300)
                });

But it's still using V1 unfortunately