-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Remove deprecated version field #4459
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
Conversation
https://www.docker.com/blog/new-docker-compose-v2-and-v1-deprecation/ Signed-off-by: Tibor <tiborcasteleijn@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just adding this link for reference to compose spec: https://github.com/compose-spec/compose-spec/blob/main/04-version-and-name.md#version-top-level-element-obsolete
Looks like the example is still written for compose v1 ( |
@tiborrr mind updating distribution/docs/content/recipes/nginx.md Lines 193 to 195 in 4615d30
|
Looks like there's a couple of other places as well; git grep 'docker-compose[^\.-]'
docs/content/about/deploying.md:$ docker-compose up -d
docs/content/recipes/apache.md:$ docker-compose up -d
docs/content/recipes/nginx.md:$ docker-compose up -d
releases/v3.0.0-alpha.1.toml:* Use docker-compose spec v3 in nginx receipt ([#3872](https://github.com/distribution/distribution/pull/3872))
releases/v3.0.0-alpha.1.toml: * [`c624b9ed`](https://github.com/distribution/distribution/commit/c624b9eda7d193856216ee0013468777a16f2e8a) Use docker-compose spec v3 in nginx receipt |
|
Signed-off-by: Tibor <tiborcasteleijn@gmail.com>
Signed-off-by: Tibor <tiborcasteleijn@gmail.com>
Signed-off-by: Tibor <tiborcasteleijn@gmail.com>
@thaJeztah can you approve this pull request with the changes I have made? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh! thought I did
LGTM, thanks!
https://www.docker.com/blog/new-docker-compose-v2-and-v1-deprecation/