bug: modify scripts to leverage either "docker compose" or "docker-compose", depending on availability #47
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.
The latest versions of Docker have the
docker composecommand built in (or at least, provided through a plugin), thus rendering thedocker-composecommand obsolete in modern Docker installations.This PR modifies Bash scripts that reference the
docker-composecommand to leverage a dynamically-determined Docker command instead. This will enable backwards-compatibility with older system that only havedocker-composeavailable while introducing support for the newdocker composecommand. Furthermore, future extendability may be possible for other containerization platforms/commands, likepodman.This was tested on a fresh installation as shown below.