We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug The Puppeteer NPM-Package seems to download and install the x86 build of Chrome. This refuses to work on non-x86 CPUs.
To Reproduce Install the adapter on ARM64 platforms.
Expected behavior Use either the package manager of the distribution to install a correct build of Chrome/Chromium or download it during install.
Additional context I've fixed the problem by first installing chromium (Debian 12 / ARM64 in my case): sudo apt install chromium
sudo apt install chromium
Change the adapter's main.js onReady() function to load the correct binary (chromium in my case):
async onReady() { this.browser = await import_puppeteer.default.launch({ headless: "new", defaultViewport: null, executablePath: '/usr/bin/chromium', args: ['--no-sandbox', '--disable-setuid-sandbox'] }); this.subscribeStates("url"); this.log.info("Ready to take screenshots"); }
Now everything works as expected.
The text was updated successfully, but these errors were encountered:
Duplicate of #7
Sorry, something went wrong.
No branches or pull requests
Describe the bug
The Puppeteer NPM-Package seems to download and install the x86 build of Chrome. This refuses to work on non-x86 CPUs.
To Reproduce
Install the adapter on ARM64 platforms.
Expected behavior
Use either the package manager of the distribution to install a correct build of Chrome/Chromium or download it during install.
Additional context
I've fixed the problem by first installing chromium (Debian 12 / ARM64 in my case):
sudo apt install chromium
Change the adapter's main.js onReady() function to load the correct binary (chromium in my case):
Now everything works as expected.
The text was updated successfully, but these errors were encountered: