-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
chrome was not found within cypress/included:11.2.0 #24810
Comments
When digging down into the node16.16.0-chrome105-ff104-edge Dockerfile that # install Chrome browser
RUN node -p "process.arch === 'arm64' ? 'Not downloading Chrome since we are on arm64: https://crbug.com/677140' : process.exit(1)" || \
(wget --no-verbose -O /usr/src/google-chrome-stable_current_amd64.deb "http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_105.0.5195.125-1_amd64.deb" && \
dpkg -i /usr/src/google-chrome-stable_current_amd64.deb ; \
apt-get install -f -y && \
rm -f /usr/src/google-chrome-stable_current_amd64.deb) This means: when building and executing the image on M1 Mac (arm64), no chrome browser is installed and actually "included" into the image. There is an open issue in the cypres-docker-images repo about this. Now it makes sense why cypress can not find the "installed" chrome, its literally not there so the error message reported in this issue is completely correct. What workarounds are there to get a chromium / chrome started on all platforms (amd64 and arm64)? It is not really an option for our team to switch to Electron since we need the |
@SMenigat I'm going to close as a duplicate of cypress-io/cypress-docker-images#695. Right now for the docker images themselves for arm64 devices, there isn't a work around to run other browsers. But you should be able to set |
Current behavior
When running cypress within an container built using the
cypress/included:11.2.0
image, cypress fails to locate the chrome browser:Desired behavior
Cypress being executed within
cypress/included
images should be able to findchrome
and run it.Test code to reproduce
We have the following Docker image:
We execute the follwing command within the running docker container:
Cypress Version
11.2.0
Node version
v16.16.0 (within the cypress/included:11.2.0 container)
Operating System
macOS 13.0.1 (m1-max)
Debug Logs
Other
I also tried the 10.x versions and have the same effect on my machine.
The text was updated successfully, but these errors were encountered: