[feature] Support docker compose as plugin #137
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Detected on: https://app.clickup.com/t/2he0te1, https://app.clickup.com/t/1mufv53
This one was tricky. Latest Docker package upgrades are making it increasingly difficult to make
docker-composework. See, for example:We can no longer delay the upgrade from
docker-composetodocker compose(as a plugin), which is the modern recommended approach. Ubuntu systems support this through thedocker-compose-v2package.Note that the docker compose plugin is a drop-in replacement a docker-compose, but it has been completely rewritten (python -> go). so this is not a breaking change, but definitely we should keep an eye to see all the configurations used in EST keep working. I've tested with SP and my local dockers, and for now, everything works as before.