Fix Puppeteer launch failure on ARM by using system-installed Chromium#122
Merged
orangecoding merged 1 commit intoorangecoding:masterfrom Jan 4, 2025
Merged
Fix Puppeteer launch failure on ARM by using system-installed Chromium#122orangecoding merged 1 commit intoorangecoding:masterfrom
orangecoding merged 1 commit intoorangecoding:masterfrom
Conversation
Owner
|
looks good. thanks! |
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
2 participants
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.
Description
This PR fixes an issue where Puppeteer fails to launch on ARM-based systems due to an incompatible Chromium binary. The solution ensures Puppeteer uses a system-installed Chromium compatible with ARM.
Context
Fixes #121
Changes Made
RUN apt-get update && apt-get install -y chromiumENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true \ PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium