Pinning Docker Compose version for Travis in order to avoid intermittent Docker errors #466
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.
Description
We've been facing different errors in Alegre Travis jobs related to Docker, for example:
And:
It doesn't happen consistently. Although the Travis file is configured for
dist: jammy
(which is the latest they support), looks like different versions of Docker are used in different jobs.For now, my suggestion to fix this is by using a pinned version of the latest Docker Compose version. Once we move from Travis to GitHub Actions hopefully this can be more stable and use the latest versions of these packages.
(No ticket created for this).
How has this been tested?
The Travis job passed after these changes: https://app.travis-ci.com/github/meedan/alegre/builds/272951439