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
The screenshot command fails on arm64 due to the an upstream dependency only pulling down a binary blob for one particular CPU architecture.
Until this is resolved upstream (pyppeteer/pyppeteer#155), consider installing chromium from the OS package manager.
This fix is demonstrated by changing only the Dockerfile, in the forked repo branch at master...kairzha:kairzha-patch-1
You can test this out yourself via:
arm64:
docker run --rm busybox uname -a Linux a2ca1418e374 5.4.0-1022-raspi #25-Ubuntu SMP PREEMPT TIMESTAMP aarch64 GNU/Linux docker build --tag witnessmeme https://github.com/kairzha/WitnessMe.git#kairzha-patch-1 docker run --rm -v "$PWD":/data -w /data witnessmeme screenshot 'https://www.bing.com/search?q=apple+m1' [witnessme.screenshot] INFO - Saved scan to scan_TIMESTAMP/
x64:
docker run --rm busybox uname -a Linux fb2651a302d5 5.4.39-linuxkit #1 SMP TIMESTAMP x86_64 GNU/Linux docker build --tag witnessmeme https://github.com/kairzha/WitnessMe.git#kairzha-patch-1 docker run --rm -v "$PWD":/data -w /data witnessmeme screenshot 'https://www.bing.com/search?q=apple+m1' [witnessme.screenshot] INFO - Saved scan to scan_TIMESTAMP/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The screenshot command fails on arm64 due to the an upstream dependency only pulling down a binary blob for one particular CPU architecture.
Until this is resolved upstream (pyppeteer/pyppeteer#155), consider installing chromium from the OS package manager.
This fix is demonstrated by changing only the Dockerfile, in the forked repo branch at master...kairzha:kairzha-patch-1
You can test this out yourself via:
arm64:
x64:
The text was updated successfully, but these errors were encountered: