Mike Bland
|
e04f063645
|
Add detailed project name requirements, mechanisms (#16915)
* Add detailed project name requirements, mechanisms
These changes reflect updated `docker compose` behavior regarding
acceptable project names.
compose-spec/compose-go#261 changed `docker compose` behavior to require
normalized project names as input when using `-p`. Previously `docker
compose` normalized project names automatically, leading to errors for
some users after the change landed in compose-spec/compose-go v1.2.5 and
docker/compose v2.5.1.
compose-spec/compose-spec#314 updated the compose spec, effectively
enforcing the same constraint for the `name:` config file property.
compose-spec/compose-go#362 added information to the error message
specifying the correct project name format. compose-spec/compose-go#364
added enforcement of the new project name requirements for all project
name mechanisms (`-p`, `name:`, `COMPOSE_PROJECT_NAME`, project dir,
working dir).
Local development URLs:
- http://localhost:4000/compose/reference/#use--p-to-specify-a-project-name
- http://localhost:4000/compose/environment-variables/envvars/#compose_project_name
- http://localhost:4000/engine/reference/commandline/compose/#use--p-to-specify-a-project-name
Production URLs:
- https://docs.docker.com/compose/reference/#use--p-to-specify-a-project-name
- https://docs.docker.com/compose/environment-variables/envvars/#compose_project_name
- https://docs.docker.com/engine/reference/commandline/compose/#use--p-to-specify-a-project-name
Signed-off-by: Mike Bland <mbland@acm.org>
* Revert _data/compose-cli/docker_compose.yaml
This reverts part of commit 9ce29a8aec.
As @glours noted in the review of #16915, this content comes from the
upstream docker/compose repo. He's opened docker/compose#10390 to apply
the update there instead.
Signed-off-by: Mike Bland <mbland@acm.org>
---------
Signed-off-by: Mike Bland <mbland@acm.org>
|
2023-03-22 08:59:55 +00:00 |
Allie Sadler