docs: remove deprecated version field from docker-compose examples#184
Open
andrerfneves wants to merge 1 commit into
Open
docs: remove deprecated version field from docker-compose examples#184andrerfneves wants to merge 1 commit into
andrerfneves wants to merge 1 commit into
Conversation
Docker Compose v2 ignores the version field, and it is deprecated in modern Compose specifications. The version field was required for validation in Docker Compose v1 but is no longer needed and produces warnings in newer Docker releases.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes the deprecated
version: '3.8'field from the docker-compose YAML examples inDEPLOYMENT_DOCKER.md.Why
Docker Compose v2 (the Go-based
docker compose) ignores theversionfield and it is deprecated in modern Compose Specification (v2+). Including it in examples:versionin examplesChanges
DEPLOYMENT_DOCKER.md: Removedversion: '3.8'from both YAML code blocks (simple example and SSL/TLS production example)Test Plan
versionfield was always optional in practice for modern Compose