-
Notifications
You must be signed in to change notification settings - Fork 156
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
Docker compose 'version' element has been deprecated and shows up with an obsoleted error #2034
Labels
area:docs
Documentations
Comments
studioego
added a commit
that referenced
this issue
Apr 18, 2024
Docker compose 'version' element has been deprecated and shows up with an obsoleted error. On the install from Package guide, remove docker compose top-level element 'version' Following the document https://github.com/compose-spec/compose-spec/blob/master/spec.md#version-top-level-element , The top-level version property is defined by the Compose Specification for backward compatibility. It is only informative. As a result, On the install from Package documents need to remove deprecated top-level version element. Fixed #2034
6 tasks
adrysn
pushed a commit
that referenced
this issue
Apr 25, 2024
Docker compose 'version' element has been deprecated and shows up with an obsoleted error. On the install from Package guide, remove docker compose top-level element 'version' Following the document https://github.com/compose-spec/compose-spec/blob/master/spec.md#version-top-level-element , The top-level version property is defined by the Compose Specification for backward compatibility. It is only informative. As a result, On the install from Package documents need to remove deprecated top-level version element. Fixed #2034 <!-- Please precisely, concisely, and concretely describe what this PR changes, the rationale behind codes, and how it affects the users and other developers. --> **Checklist:** (if applicable) - [ ] Milestone metadata specifying the target backport version - [ ] Mention to the original issue - [ ] Installer updates including: - Fixtures for db schema changes - New mandatory config options - [ ] Update of end-to-end CLI integration tests in `ai.backend.test` - [ ] API server-client counterparts (e.g., manager API -> client SDK) - [ ] Test case(s) to: - Demonstrate the difference of before/after - Demonstrate the flow of abstract/conceptual models with a concrete implementation - [ v ] Documentation - Contents in the `docs` directory - docstrings in public interfaces and type annotations <!-- readthedocs-preview sorna start --> ---- 📚 Documentation preview 📚: https://sorna--2035.org.readthedocs.build/en/2035/ <!-- readthedocs-preview sorna end --> <!-- readthedocs-preview sorna-ko start --> ---- 📚 Documentation preview 📚: https://sorna-ko--2035.org.readthedocs.build/ko/2035/ <!-- readthedocs-preview sorna-ko end -->
Resolve it. then close. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Main idea
Docker compose 'version' element has been deprecated and shows up with an obsoleted error.
Example)
https://github.com/lablup/backend.ai/blob/main/docs/install/install-from-package/prepare-cache-service.rst
https://github.com/lablup/backend.ai/blob/main/docs/install/install-from-package/prepare-database.rst
Following the document https://github.com/compose-spec/compose-spec/blob/master/spec.md#version-top-level-element ,
The top-level version property is defined by the Compose Specification for backward compatibility. It is only informative.
As a result,
docker-compose.yaml
like files need to remove deprecated top-levelversion
element.Alternative ideas
No response
Anything else?
Reference Issues
'version' is obsolete
docker/compose#11628The text was updated successfully, but these errors were encountered: