Revert "Use new Docker Compose installation method" #187
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
Closed
BytesGuy
approved these changes
Aug 24, 2022
This reverts commit 2b2cc95.
felicianotech
force-pushed
the
revert-178-apt-compose
branch
from
c7100d6
to
07f9915
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Reverts #178
This was an exciting idea when we found out that Docker started including Docker Compose in the apt repository. Unfortunately, this new install method is not working out for us. Docker doesn't publish new Docker Compose releases to the repo until they do a new Docker release. This is preventing us from releasing new Docker Compose versions within our image itself. I have an open issue upstream regarding this.
Until that gets resolved at some point, we'll go back to how we use to install Docker Compose. Not as "cool", but it worked.