-
-
Notifications
You must be signed in to change notification settings - Fork 313
Use Chromium by default in Dockerfile for all architectures #4680
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
Co-authored-by: DonnieBLT <[email protected]>
Co-authored-by: DonnieBLT <[email protected]>
e-esakman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally. The fallback to Chromium works correctly and resolves the Chrome install issue.
|
@copilot lets update this to use Chromium by default |
Co-authored-by: DonnieBLT <[email protected]>
gojo-satorou-v7
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change looks good.
@copilot in the PR description mention issue #4731 as closed to trigger checks.
Google Chrome is only packaged for amd64 on Linux. To ensure consistent behavior across all platforms and support ARM64 systems (Apple Silicon, ARM servers), this PR switches to using Chromium by default on all architectures.
Changes
chromiumon all architectures (amd64, ARM64, etc.)/usr/local/bin/google-chromesymlink to maintain compatibility with applications expecting thegoogle-chromecommandImplementation
Benefits
💡 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.