[BUG]: DockerCompose task compatibility mode issue

[sadmdbrezack-metabolon]

New issue checklist

• I searched for existing GitHub issues
• I read pipeline troubleshooting guide
• I checked how to collect logs

Task name

DockerCompose

Task version

0.240.2

Issue Description

azure-pipelines-tasks/Tasks/DockerComposeV0/dockercomposeconnection.ts

Line 99 in fa06ce1

command.arg("--compatibility");

Docker no longer supports comparability flag in newer versions. This should be removed or we need a flag to disable compatibility mode. Happy to ship a fix if someone wants to help walk me through it

Dockercompose git for reference
docker/compose#8618 (comment)

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

All

Relevant log output

unknown flag: --compatibility

Full task logs with system.debug enabled

No response

Repro steps

No response

[okamilobo]

This has taken down all of our builds so we would appreciate rapid resolution.

[okamilobo]

We worked around by specifying a path to the docker-compose.exe and will be working on moving to a more recent version.

[sleipper]

This relate to recent uodates https://learn.microsoft.com/en-us/azure/devops/release-notes/2024/sprint-240-update#dockercompose0-uses-docker-compose-v2-in-v1-compatibility-mode that flag isn't supported in later versions.

[v-schhabra]

Hi @sadmdbrezack-metabolon
Thanks for reporting this issue. Could you please share the complete debug logs of the pipeline by adding variable system.debug to "true"?

[severindheureuse]

Hi, I worked around this issue by specifying a projectName (in lowercase) in the azure-pipeline.yml DockerCompose@0 task.

[sadmdbrezack-metabolon]

For anyone that is having issues with this you can set the docker compose path until this gets fixed.

dockerComposePath: '/usr/local/bin/docker-compose'

[sadmdbrezack-metabolon]

Hi @sadmdbrezack-metabolon Thanks for reporting this issue. Could you please share the complete debug logs of the pipeline by adding variable system.debug to "true"?

Run docker compose --compatibility up with any newer version of docker to recreate.

Removing line 99 should fix.

[Peralysis]

I found that as a temporary workaround I can disable the --compatibility switch from being passed by adding a variable with the name USE_DOCKER_COMPOSE_V2_COMPATIBLE_MODE to the pipeline and setting the value to false. This variable gets passed to the task as an environment variable and is picked up as a feature flag that disables the block of code that adds the problematic --compatibility flag.

[v-schhabra]

Hello Everyone,
For now we have disabled the FF DistributedTask.Agent.UseDockerComposeV2CompatibleMode for all the organizations.
I hope you will not be having any issues related to compatibility mode.

[w1s3one805]

New issue checklist

• I searched for existing GitHub issues
• I read pipeline troubleshooting guide
• I checked how to collect logs

Task name

DockerCompose

Task version

0.240.2

Issue Description

azure-pipelines-tasks/Tasks/DockerComposeV0/dockercomposeconnection.ts

Line 99 in fa06ce1

command.arg("--compatibility");

Docker no longer supports comparability flag in newer versions. This should be removed or we need a flag to disable compatibility mode. Happy to ship a fix if someone wants to help walk me through it

Dockercompose git for reference
docker/compose#8618 (comment)

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

All

Relevant log output

unknown flag: --compatibility

Full task logs with system.debug enabled

No response

Repro steps

No response

[v-schhabra]

Hi @w1s3one805
Please migrate to DockerCompose@1 task and if you have any issues, please feel free to raise an issue.
For now we are closing this ticket.