-
Notifications
You must be signed in to change notification settings - Fork 38
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
[Package Request] - chromium and chromedriver #356
Comments
I have the same need. Would like to switch to AL2023 but need chromium and chromedriver... this is the last roadblock. |
I have the same need |
I was able to run chromium after installing this: |
Do you mean you compiled chromium from source then? Or did you get an RPM for it from somewhere? Either way we still really need it to be included in the repo. |
I forgot to say it was a workaround for dependencies, I was running chromium for unit testing using https://playwright.dev/ I hope this could help someone needing a quick workaround 😄 |
I created a discussion on recommended way to install Chromium at #417 |
@trivikr - That is installing Chrome, not Chromium. Here is our current install method for Chrome. If using for Angular testing, make sure to set CHROME_BIN so that Karma can find it.
|
I would love to see an |
We need chromium headless aarch64 to be used with puppeteer. |
Well the problem with chrome and firefox is that both do not provide aarch64 builds for linux. https://googlechromelabs.github.io/chrome-for-testing/ Bugs: IMHO we need upstream support and not rely on aws to be in sync with regular monthly releases. But would love some compatible spec (srpm) file to build rpm ourselves. |
this worked for me commands: |
The following is what I did to have Chrome for Testing, Google's recommended builds of Chrome and CheomeDriver for testing, working on an EC2 instance running Amazon Linux 2023. I hope this helps: With Node.js# A hacky way to install all the package dependencies required by Chrome for Testing.
# See: https://github.com/GoogleChromeLabs/chrome-for-testing/issues/55
sudo dnf install --assumeyes --quiet findutils
sudo dnf deplist https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm | \
grep provider | \
sort --unique | \
awk '{print $2}' | \
xargs sudo dnf install --best --allowerasing --skip-broken --assumeyes --quiet > /dev/null 2>&1
npx --yes @puppeteer/browsers install chrome@stable | \
awk '{print $2}' | \
xargs -I {} sudo ln --symbolic {} /usr/local/bin/chrome
npx --yes @puppeteer/browsers install chromedriver@stable | \
awk '{print $2}' | \
xargs -I {} sudo install --owner=root --group=root --mode=+x {} /usr/local/bin/chromedriver Without Node.js# A hacky way to install all the package dependencies required for Chrome for Testing.
# See: https://github.com/GoogleChromeLabs/chrome-for-testing/issues/55
sudo dnf install --assumeyes --quiet findutils jq unzip
sudo dnf deplist https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm | \
grep provider | \
sort --unique | \
awk '{print $2}' | \
xargs sudo dnf install --best --allowerasing --skip-broken --assumeyes --quiet > /dev/null 2>&1
CHROME_FOR_TESTING_RELEASE="$(curl --silent https://googlechromelabs.github.io/chrome-for-testing/last-known-good-versions-with-downloads.json | jq '.channels.Stable')"
CHROME_DOWNLOAD_URL="$(echo ""${CHROME_FOR_TESTING_RELEASE}"" | jq -r '.downloads.chrome[] | select(.platform == "linux64") | .url')"
curl --remote-name --silent "${CHROME_DOWNLOAD_URL}"
unzip -q chrome-linux64.zip
sudo ln --symbolic "${PWD}/chrome-linux64/chrome" /usr/local/bin/chrome
CHROMEDRIVER_DOWNLOAD_URL="$(echo ""${CHROME_FOR_TESTING_RELEASE}"" | jq -r '.downloads.chromedriver[] | select(.platform == "linux64") | .url')"
curl --remote-name --silent "${CHROMEDRIVER_DOWNLOAD_URL}"
unzip -q chromedriver-linux64.zip
sudo install --owner=root --group=root --mode=+x "${PWD}/chromedriver-linux64/chromedriver" /usr/local/bin/chromedriver |
As per #543 - there is a request also for |
What package is missing from Amazon Linux 2023? Please describe and include package name.
Please make the "chromium" package available in Amazon Linux 2023. We use headless chromium to run unit tests on typescript.
Is this an update to existing package or new package request?
This is not currently available in Amazon Linux 2023.
Is this package available in Amazon Linux 2? If it is available via external sources such as EPEL, please specify.
This is an EPEL package available in Amazon Linux 2.
Any additional information you'd like to include. (use-cases, etc)
I am currently using the amazonlinux:2023 docker image. Thanks for your consideration!
The text was updated successfully, but these errors were encountered: