feat: support x-context extension to set Docker context in compose.yaml#13694
Open
ssam18 wants to merge 1 commit intodocker:mainfrom
Open
feat: support x-context extension to set Docker context in compose.yaml#13694ssam18 wants to merge 1 commit intodocker:mainfrom
ssam18 wants to merge 1 commit intodocker:mainfrom
Conversation
Allow users to specify a Docker context at the compose project level via an x-context extension field. When set, all compose operations use the specified context instead of the CLI default, without needing --context on every invocation. Fix for the bug docker#13501 Signed-off-by: Samaresh Kumar Singh <ssam3003@gmail.com>
c86db7d to
774cd20
Compare
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
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.
This adds support for an x-context top-level extension in compose.yaml that lets users pin a named Docker context for all compose operations. It removes the need to pass --context on every invocation when working with non-default contexts like rootless or remote SSH endpoints. The implementation detects the extension after loading the project and reinitializes the Docker CLI for the specified context before dispatching to the backend.