Dependencies missing while using your docker image
See original GitHub issueCurrent behavior:
I am trying to integrate cypress into our deployment process and I am using one of the your docker images for that (base:8 also tried a chrome one) It runs perfectly on my laptop but when i am deploying to the server it gives this error
up to date in 1.239s
It looks like this is your first time using Cypress: 2.1.0
[21:26:18] Verifying Cypress can run /usr/src/app/node_modules/cypress/dist/Cypress [started]
[21:26:19] Verifying Cypress can run /usr/src/app/node_modules/cypress/dist/Cypress [failed]
[21:26:19] → Cypress failed to start.
This is usually caused by a missing library or dependency.
The error below should indicate which dependency is missing.
https://on.cypress.io/required-dependencies
If you are using Docker, we provide containers with all required dependencies installed.
----------
----------
Platform: linux (Debian - 8.10)
Cypress Version: 2.1.0
Cypress failed to start.
This is usually caused by a missing library or dependency.
The error below should indicate which dependency is missing.
https://on.cypress.io/required-dependencies
If you are using Docker, we provide containers with all required dependencies installed.
----------
----------
Platform: linux (Debian - 8.10)
Cypress Version: 2.1.0
Desired behavior:
I want it to not fail
How to reproduce:
I am not sure maybe try to run it in a container on a remote server
- Operating System: ubuntu 14.04
- Cypress Version: 2.1.0
- Browser Version: headless
Issue Analytics
- State:
- Created 5 years ago
- Comments:33 (9 by maintainers)
Top Results From Across the Web
Missing installed dependencies when docker image is used
Firstly the Docker image. The command bluebase plugins:add seems to be very dependent on the $HOME environment variable. Your Docker image ...
Read more >Image-building best practices - Docker Documentation
Update the Dockerfile to copy in the package.json first, install dependencies, and then copy everything else in. · Create a file named ....
Read more >Custom build images and live package updates
If you have specific dependencies that take a long time to install during a build using Amplify's default container, you can create your...
Read more >How to handle missing dependencies with composer & docker?
Just use --ignore-platform-reqs (docs). What I usually put in my Dockerfiles when creating images for this kind of project is something like this,...
Read more >Visual Studio Code Dev Containers Frequently Asked Questions
I am seeing errors when trying to mount the local filesystem into a container ... Right-click on the Docker task bar item. On...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m finally able to resolve my issue and now Cypress is working fine for me.
Following environment variable was being set DISPLAY=:1.5
Unsetting this variable solved my problem. I hope this help someone else as well.
You can verify if you have value set in DISPLAY, by running the following command:
echo $DISPLAY
Please try unsetting the
NODE_OPTIONS
environment variable if you have this set - as this causes Cypress to crash. This is due to an Electron bug prior to version 2.0.3, where havingNODE_OPTIONS
set causes either a failure or arguments to be ignored. https://github.com/electron/electron/issues/12695#issuecomment-385826834To see all environment variables currently set
MacOS / Linux
Windows
To unset
NODE_OPTIONS
environment variableMacOS / Linux
Windows
We have open issues for this being fixed that you can follow here:
NODE_OPTIONS
should not exit0
: https://github.com/cypress-io/cypress/issues/1676