Closed afscrome closed 1 year ago
@afscrome, do you have "Use Docker Compose V2" in Docker Desktop settings checked?
Nope, it was unchecked. Checking it fixed the issue.
Given that compose v1 is now deprecated, maybe the tooling could issue a warning if V1 compose is detected. (or migrate to use docker compose
directly - https://docs.docker.com/compose/migrate/ )
Thanks. Nice to hear that resolved it. We may at some point migrate but for now it should be aliased if using V2 and still allows for compatibility with V1.
I do see this Warning in our the Container Tools output pane in Visual Studio when using V1
WARNING: Compose V1 is no longer supported and will be removed from Docker Desktop in an upcoming release. See https://docs.docker.com/go/compose-v1-eol/
Trying to build a docker-compose file containing secrets results in the following error
It looks like the visual studio integration is using
docker-compose
rather thandocker compose
. Starting the above compose file withdocker compose up
starts successfully, butdocker-compose up
fails with similar errors to visual studiodocker-compose.yml
VS Error
MSBuild output