Repository navigation
fix(browser): make Chromium sandbox configurable - #2376
Open
deswanth12 wants to merge 1 commit into
Open
deswanth12 wants to merge 1 commit into
deswanth12 wants to merge 1 commit into
Conversation
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.
Summary
Fixes #2371 by making Chromium sandbox behavior configurable and ensuring the sandbox setting is respected across browser launch paths.
Changes
BrowserConfig.chromium_sandboxfor explicit programmatic configuration.CRAWL4AI_CHROMIUM_SANDBOX=trueas the environment-based fallback when the config is unspecified.--no-sandboxand pass Playwright'schromium_sandbox=Truewhen sandboxing is enabled.Validation
Runtime note: Linux/Docker sandbox operation still depends on compatible container and host security settings.
Fixes #2371