When I upgrade to a new version of Docker Desktop, I should have the same settings that I had before upgrading. Mark the issue as fresh with /remove-lifecycle stale comment. Sign in We didn't skip step 1. @damienmckenna Docker Desktop doesn't follow semver. Yes, and that has been the situation since December (eight months ago), which is how we got 10% adoption even before starting to switch people over to it. I could have checked everything and both ddev and compose-cli could have matured to where there was no issue. 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. Perhaps you could have a "canary me" checkbox :). From https://github.com/docker/compose-cli/issues/2012: Yes, that's a separate tool and can co-exist (for now). yes indeed, as we do for many other features on each and every release, This was the first time that docker-compose changed behavior for all users of Docker Desktop, Not for all users. that we bundle; (2) VM management and pass-through magic to make containers run on Windows and Mac and appear to be running natively; (3) a GUI on top. I'm all for v2 being successful, and have worked hard to describe and report the many differences of behavior, but haven't been able to test the results of those fixes. Here are a few issues I saw when using V2 (while not realizing I was using V2): This was all on Windows, but I think some of my teammates on Mac were having issues as well. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Please don't start the 100% canary yet. I understand from @mat007 that your announcement here basically means you're going to turn on 100% canary on this, which means that current ddev will refuse to run with it (but tell people what to do). Even 10% of users on such a large user base is still significant with thousands usages a day. I even read through the release notes when upgrading Docker Desktop, and they also don't make it clear that I was going to automatically be using V2. We haven't yet been able to pass our test suite with compose v2, and of course although issue responsiveness has been great, the latest docker-compose has not been bundled into a desktop version to test with. We have both a popup and a CLI warning when it's turned on. Think of Docker Desktop as basically three things (1) lots of upstream Linux components (engine, docker CLI, compose, Kubernetes etc.) Some users upgrading to docker desktop 3.5+ get the "compose v2" checkbox enabled for them. Please don't default-enable v2 in Desktop 3.6.0. Following this convention the switch from Docker Compose v1 to v2 would be in 4.0.0 instead of a 3.x.0 release, while 3.x.0 releases would support both and let folks prepare for the upgrade. Today a team member discovered that PHPStorm doesn't support docker-compose v2 fully yet. Save it for a few weeks until compose v2 and ddev can make progress on passing tests and resolving things that need to be done differently. This isn't under the control of the users. I also wasted a bunch of time on this, because I had no idea I was using the Compose V2 beta. But let me give you some context to explain our reasoning. I'm pleased to say we're getting very few bug reports in phase 2, but of course we're keen to hear of incompatibilities at https://github.com/docker/compose-cli. I'd like to compare this to the experience of using Docker on Linux directly. Closed issues are locked after 30 days of inactivity. If this issue is safe to close now please do so. There may be a bug in this logic. When we do, we notify the user and give them instructions how to turn it off again. Issues go stale after 90 days of inactivity. I've opened several issues in docker/compose-cli, they've been promptly addressed, but there are too many problems outstanding, and I can't get though a test run with ddev. I thought I was still using V1. It would be a significant issue if all of a sudden docker-compose swapped to docker compose in a minor release. We find that not many people switch on the experimental features unless they are trying to fix some specific problem. I think the only additional thing we could have done is to allow people to switch on the docker-compose -> v2 alias for a period of time before starting to force them. @stephen-turner: following semantic versioning practices, shouldn't changes that introduce backwards compatibility problems be made with major releases rather than minor releases? AFAICT there is no officially sanctioned way to install docker-compose (as opposed to docker compose) on Linux. Please, if a feature is "experimental", let it be opt-in for everybody for a period of time. Prevent issues from auto-closing with an /lifecycle frozen comment. Experimental features are experimental and should be enabled by choice of the user. Our team never saw any notification of Docker Compose V2 being enabled. So it won't currently get the use it needs. But I accept that it is possible that ddev and lando use cases were still not captured, and we didn't consider that. Per conversations with @mat007 I will also be adding the ability to test with v2 in next alpha, drud/ddev#3152. We needed to be at step 1 for a few months. Make a clear statement about when it may appear as a canary or as a default. We use canary testing here to get a limited set of users to opt-it, and still notify them so they can opt-out. When compose v2 is enabled, all of my images fail to build with errors like this: The current implementation of docker compose v2 isn't ready to be a default setting for everyone. https://github.com/docker/compose-cli/issues/1867. So we think it's better to turn it on for a gradually increasing percentage of users, rather than switch everyone's behaviour at once. You signed in with another tab or window. I don't object to your four steps. Even for a few canary users. I've got an M1 chip. I object to skipping step 1. Have a question about this project? We advertised it in a blog post and in the release notes, and individually for each person who we move onto v2. Please report any bugs at https://github.com/docker/compose-cli. Unfortunately the opt-in phase in step 1 doesn't give us enough users and enough data to find all the bugs in all the millions of use cases our software is used for: it's the peril of being a platform. /lifecycle stale, Closing this, but I appreciate you being gentle next time there's an "experimental" feature. I think that we still would have hit a time where we had to move people forcibly and see what breaks. The unintended impact of what you've done is to delay acceptance of docker-compose v2. We advertised it in-app, and we got about 10% of people using it. I realise it's step 2 you're objecting to. ddev's latest version now detects docker-compose v2 and notifies people and insists on docker-compose v1. But those who aren't on latest ddev will just have the various remaining problems in compose v2. We just had another coworker experience this despite not having any notifications. I continue to get support issues, including this morning about the compose-cli critical failure on Windows, docker/compose-cli#1854, where somebody installed latest docker desktop, was canaried in, and had a fatal experience for their first experience. It would have been very easy to delay the canarying for a couple of months while notifying all of us wrapper maintainers (and the rest of the world) that it was going to happen then, that "docker-compose" would start to appear as a completely different animal in a few months. Hey, that's how canary testing work! There are a number of features of Docker Compose v2 which break ddev currently. On macOS, it looks like the warning is in the form of a system notification: Unfortunately, it's easy for this to get lost the backlog of notifications. in such a way that it caused mass confusion across our team and cost us several hours of debugging. I suppose in principle we could follow semver by changing our major version number whenever any of the upstream components had an API change, but we don't: we'd be bumping the major version pretty frequently if we did that. But the problem is, I was running into issues with no idea what had changed, until I stumbled onto this in my Docker Desktop settings. DDEV always tries to support and adapt to every new version of Docker, but this one just isn't possible yet. Not always the answers I wanted, but super, super responsive, thanks @ndeloof!). I asked about this in https://github.com/docker/compose-cli/issues/2012 but I guess since it hasn't had a response from the team there must not yet be a way. And I object to Step 2 being randomly distributed to users without notice. It would be better if there was also a text notification when using docker-compose, such as "Docker compose v2 beta will become the default on
French Bulldog Rescue In Texas, Shaved Black Goldendoodle, Dockerfile Print Current Directory, Trained Golden Retrievers For Sale Near Me,
docker enable experimental features mac