Make DockerCommandLineCodeExecutor the default for MagenticOne team #6684
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
This PR changes MagenticOne to use
DockerCommandLineCodeExecutor
by default instead ofLocalCommandLineCodeExecutor
, addressing security concerns about local code execution.Changes
Security Enhancement
Implementation Details
_is_docker_available()
function to detect Docker availability_create_default_code_executor()
function that prioritizes Docker executorExample Usage
Before (uses local execution by default):
After (uses Docker by default when available):
Backward Compatibility
code_executor
parameter continues to work unchangedTesting
This change aligns with the security-first principle mentioned in the MagenticOne documentation warnings about using containers for isolation.
Fixes #6683.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.