-
Notifications
You must be signed in to change notification settings - Fork 380
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
Cypress in docker fails to run with read-only project dir #686
Comments
Interestingly, this seems to only happen in docker. Running is locally (installed with npm) leads to the desired result:
|
The use-case is that I want to run cypress in kubernetes, and the project dir is mounted from a readonly configmap. |
I'm encountering this too. Desperately looking for a fix |
Encountering this in a gitlab pipeline, also see the error is related here as well: cypress-io/cypress#23326 |
Similar errors displayed here, with Kubernetes. Surprisingly, the tests are working fine.
|
I have this problem too, on Cypress version 12.17.4 |
Got this problem as well. |
Can you provide some more information? Which Cypress Docker image are you using? |
Cypress image : cypress/included:cypress-13.11.0 |
I understand that you are running your workflow through Kubernetes (K8s) under GitHub Actions. If you would like this issue investigated further, please open a new issue. You can find an example workflow .github/workflows/example-cypress-github-action.yml showing Cypress Docker images running successfully under GitHub Actions on GitHub-hosted runners (no K8s involved). |
Current behavior
Currently, when using the
cypress/included
docker image and mounting a project dir read-only, cypress fails to run.Desired behavior
It should not fail and run the tests. It could issue a warning that it is not able to save screenshots or videos.
Test code to reproduce
Cypress Version
10.2.0
Other
These issues/PRs might be related, however I was not able to determine if this behaviour should be already fixed or not:
config
cypress#6407The text was updated successfully, but these errors were encountered: