Disable docker image being used to call compose when running tests #3046
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.
Related to #2948
By default the
testcontainers
(specifically the Docker Compose Module) would use an additional container to deploy docker for the compose step (to avoid failures if the runner machine does not have docker compose).However not only does this slow down the tests but - in some cases - it causes them to fail, as the
docker
container has only 30 seconds to start, and sometimes this is not enough to download it.Forcing us to use local
docker compose
should help.Make sure that:
mvn formatter:format
target. Don’t submit any formatting related changes.