Docker Compose should not default to v2 when Desktop is in Windows containers mode

[karolz-ms]

Since Compose v2 does not support Windows containers (as of today), Docker Desktop should not default to ("translate") invocations of docker-compose into Compose v2 (docker compose) when Docker Desktop is running in Windows containers mode.

This was discussed with @nebuk89
@BigMorty @Chuxel FYI

[mat007]

Yes, indeed! We will address this hopefully for Desktop 4.2.0.
Thanks!

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[BigMorty]

We still want to get this change in please.

/remove-lifecycle stale

[mat007]

I think this was implemented and released in Desktop 4.1.1: in Windows container mode, Desktop is supposed to always fall back to Compose V1.

[karolz-ms]

Yep, thanks for doing the change and verifying that it solves the issue 🤗

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked