migrate to Docker Compose V2 using 'docker compose' #70
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since July 2023, Docker Compose V1 (
docker-compose
) is no longer included in Docker Desktop, and it is highly recommended to migrate to Docker Compose V2 (docker compose
).Tested on my Docker (version 20.10.19) installation on Linux:
docker-compose
was not automatically aliased todocker compose
so.omero/docker cli
failed previously. After changing todocker compose
, tests passed. This should work on all currently supported versions of Docker (according to their migration page linked above), but would be nice for someone on Windows (@erickmartins?) to confirm.Another option would be to replace with
docker compose --compatibility
which keeps the container naming scheme of V1, if any tests refer to hard-coded container names. But both ran fine for me and I don't know how long--compatibility
will be supported.