Use v2 as default for Docker Compose version - #621
Conversation
Update README
|
@samruddhikhandale I wasn't sure if there was an automated process for bumping versions, updating the README, so I did it manually |
|
Regarding tests:
|
Remove reference to compose-switch
samruddhikhandale
left a comment
There was a problem hiding this comment.
Thanks you so much for taking the time to contribute this PR, we really appreciate the support! ✨
I have left some thoughts/comments, thanks again!
| "default": "v1", | ||
| "description": "Default version of Docker Compose (v1 or v2 or none)" | ||
| "default": "latest", | ||
| "description": "Default version of Docker Compose (latest, none or specific version number e.g. 2.20.2)" |
There was a problem hiding this comment.
I like the idea of letting users pass specific version number, however, what would happen if they pass 1.29.0 for ARM architectures? Because it doesn't seem like v1 architectures provide ARM supported artifacts 🤔
Earlier we were installing docker compose with pip to address this issue. However, as we are deprecating v1 support, it doesn't make sense to have that fallback.
Maybe failing with informative messages should be good for now? Feel free to share your thoughts!
| }, | ||
| "containerUser": "vscode" | ||
| }, | ||
| "docker_dash_compose_v1": { |
There was a problem hiding this comment.
You would be able to revert these changes after you add back compose switch installation!
Can we add a test scenario which validates specific version/semver changes? Thanks!
| "default": "v1", | ||
| "description": "Default version of Docker Compose (v1 or v2 or none)" | ||
| "default": "latest", | ||
| "description": "Default version of Docker Compose (latest, none or specific version number e.g. 2.20.2)" |
There was a problem hiding this comment.
| "description": "Default version of Docker Compose (latest, none or specific version number e.g. 2.20.2)" | |
| "description": "Select or enter a Docker Compose version" |
Add else
Update install Update tests
|
Is there any reason why this was not merged? it seems that docker-outside-of-docker already defaults to compose V2. features/src/docker-outside-of-docker/devcontainer-feature.json Lines 23 to 32 in 0cf690e |
Resolves #620