-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should devcontainers/cli
uses docker compose
always instead docker-compose
?
#826
Comments
Hi 👋 Looking at 👇 , I think the request makes sense for the CLI to switch to the newer Docker compose V2 syntax (ie cli/src/spec-node/devContainers.ts Line 161 in be1f203
@gauravsaini04 Can you help take a look at this request? Thanks! // cc @chrmarti Let us know if there are any concerns, thanks! |
Sounds good! We currently check for The check is here: cli/src/spec-node/dockerCompose.ts Line 687 in be1f203
|
pr #848 was merged to the codebase. closing the issue. |
Hey devcontainers/cli folks 👋
I have a CI that uses
devcontainers/ci
action (which uses the devcontainers/cli) to validate a devcontainer generated for the project.I'm trying to add the top-level name property into the compose file rails/rails#51791
but it is failing on CI with the error of:
https://github.com/rails/rails/actions/runs/9044514158/job/24853256908?pr=51791
I also tried to specify the version 3.8 on the compose but without success.
I see that
devcontainers/cli
code base usesdocker-compose
insteaddocker compose
. should we replace the codebase to usedocker compose
instead so we avoid to use the old compose which is deprecate since jul 23? https://docs.docker.com/compose/migrate/I also see a test on devcontainers/cli codebase https://github.com/devcontainers/cli/blob/main/src/test/configs/compose-with-name/.devcontainer/docker-compose.yml which tests the exact same scenario but in my case it is not working.
thoughts?
The text was updated successfully, but these errors were encountered: