Migrate to Docker Compose V2 #99
Merged
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
pemoticak
force-pushed
the
docker-compose-v2
branch
from
f906de2
to
0ca61cf
Compare
Signed-off-by: Peter Motičák <peter.moticak@pantheon.tech>
pemoticak
force-pushed
the
docker-compose-v2
branch
from
0ca61cf
to
534632e
Compare
fgschwan
approved these changes
Jul 14, 2023
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.
This PR replaces all occurences of standalone
docker-compose(Compose V1) with compose plugindocker compose(Compose V2). As from July 2023 Docker Compose V1 stopped receiving updates (more info here). Moreoverswctlalready used V2 so this change unifies the usage of Compose across the codebase.Mentions of Docker/Docker Compose in docs are also updated.
Signed-off-by: Peter Motičák peter.moticak@pantheon.tech