-
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
An unexpected error occurred while verifying the Cypress executable. #29884
Comments
The Cypress Docker image cypress/browsers:node18.12.0-chrome106-ff106 you are using was published in November 2022. To use this image in GitHub Actions make sure that you run it with user container:
image: cypress/browsers:node18.12.0-chrome106-ff106
options: --user 1001 You can find an example workflow on .github/workflows/example-cypress-github-action.yml in the Cypress Docker image repository. You may also want to consider updating to an equivalent current image, such as cypress/browsers:node-18.20.3-chrome-125.0.6422.141-1-ff-126.0.1-edge-125.0.2535.85-1 which was published in June 2024. Older images are frozen and corrections are made by publishing a newer image. If the above does not solve your issue, then please post your full GitHub Actions workflow. |
The original Docker file was Current builds use We've added the documentation section https://github.com/cypress-io/cypress-docker-images/blob/master/README.md#user to make it clear about the need to set |
Did the previous comments help resolve your issue? |
yes it worked but having issues with curl command - I just need to install curl |
Current behavior
Failing to run github actions and verifying cypress fails
Desired behavior
Image used:
image: cypress/browsers:node18.12.0-chrome106-ff106
It wil allow to execute: Run npx cypress info without any issues
Test code to reproduce
Github actions:
Image used:
image: cypress/browsers:node18.12.0-chrome106-ff106
Cypress Version
12.17.4
Node version
18.12.0
Operating System
linux-x64 (Debian - [11])
Debug Logs
Other
NA
The text was updated successfully, but these errors were encountered: