devcontainers / devcontainers/cli
docker-compose do not use --project-name param to set COMPOSE_PROJECT_NAME
- Vorherrschende Sprache
- TypeScript
- Sterne
- 3k
- Forks
- 457
- Ø Merge
- 13 Std. 17 Min.
- Gemergte PRs (30 T.)
- 6
Beschreibung
This is an issue in docker-compose but affects devcontainers: the devcontainer `use docker-compose --project-name `, but unfortunatelly and surprisingly it do not set COMPOSE_PROJECT_NAME for the compose file. The short version of that command line param behave correctly (-p).
I would recommend to change --project-name command line param usage to -p.
Beitragsleitfaden
Rechercherichtung
Start by reproducing the devcontainer command with --project-name and compare its behavior with the equivalent -p form. Trace how the CLI passes each option to Docker Compose and verify that the long form sets COMPOSE_PROJECT_NAME for the compose file. Done means both forms produce the same project-name behavior.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- docker, docker-compose, typescript
- Bereich
- cli, devops
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100