• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics Irrelevant
• Diagnostics ID:

Expected behavior

When I upgrade to a new version of Docker Desktop, I should have the same settings that I had before upgrading.

Actual behavior

Some users are getting the "Use Docker Compose v2" experimental setting enabled for them on upgrade to Docker Desktop 3.5+ without their consent or buy-in.

There are a number of features of Docker Compose v2 which break ddev currently. I'm happy to try to sort them out and make sure things work in upcoming versions (already filed several issues in compose-cli and ddev issue queues), but it's not friendly behavior to enable features like this without user opt-in.

Apparently you have some kind of "canary experiment" going on. Please don't do this. Experimental features are experimental and should be enabled by choice of the user.

Information

• macOS Version: All
• Intel chip or Apple chip: All
• Docker Desktop Version: 3.5+

Steps to reproduce the behavior

This isn't under the control of the users. Some users upgrading to docker desktop 3.5+ get the "compose v2" checkbox enabled for them.

Note that this happens on both Windows and macOS.