Remove obsolete version field from docker-compose.yml#167
Open
mahmoodhamdi wants to merge 1 commit into
Open
Conversation
The top-level `version` key is no longer used by Compose V2; it triggers an "obsolete" warning on every `docker compose` invocation. Removing it makes the file conform to the current Compose Spec without changing any service definitions. Validated with `docker compose config`: the file still parses correctly and the warning is no longer emitted.
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 top-level
version: '3'key fromdocker-compose.yml. The fieldis no longer used by Compose V2 and triggers an "obsolete" warning on every
docker composeinvocation:The rest of the file is already valid Compose Spec syntax (
services:,build:,image:,volumes:, etc.), so no other changes are needed.Verification
Ran
docker compose configagainst the patched file — it still parsescorrectly, expands both services as before, and no longer emits the
deprecation warning.
Note
Independent of #166 (PHP version bump). They can land in either order; both
target the local Docker development path.