Skip to content

Should devcontainers/cli uses docker compose always instead docker-compose? #826

@duduribeiro

Description

@duduribeiro

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:

he Compose file .. is invalid because:
  'name' does not match any of the regexes: '^x-'

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 uses docker-compose instead docker compose. should we replace the codebase to use docker 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?

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions