Nicolas De loof
Nicolas De loof
This isn't a bug: builder design require to store more details about the images than the docker engine needs. Typically builder do support multi-platform builds while the engine will only...
see https://github.com/compose-spec/compose-go/pull/652
checked by https://github.com/docker/compose/pull/11961
better get this published with the compose release
Compose v2 can run standalone as `docker-compose` and AFAICT this _should_ be the case within Docker Desktop, but maybe recent removal for legacy compose-cli broke this ?
@LikeAJohny please report error running you application on github.com/docker/compose with error details so we can investigate
Docker Desktop setup creates symlink `/usr/local/bin/docker-compose -> /Applications/Docker.app/Contents/Resources/cli-plugins/docker-compose`. `docker-compose` binary can _both_ be used as a CLI plugin (i.e. `docker compose ...` or standalone for backward compatibility This issue should...
After docker compose v1 was eventually declared End of Life, we removed the feature for user to select compose v1 vs v2 as they run `docker-compose`. The side-effect is that...
This flag is available on `docker compose run`. `compose up` serves a distinct purpose, and typically relies on previous container to inherit anonymous volumes, and will recreate container if needed,...
Your should indeed run e2e test using `docker compose run` and use `depends_on` to make it explicit the service being required for the test to run. We also could expose...