Cypress/Browser Docker image is not working

Question

Cypress/Browser Docker image is not working

varshanharshank opened this issue a year ago · comments

e. I have Successfully pulled the below images but getting the below error.

node18.12.0-chrome103-ff107
node18.12.0-chrome106-ff106
node18.12.0-chrome107
node18.6.0-chrome105-ff104

Ben M · Answer 1 · Thu May 04 2023 02:50:59 GMT+0800 (China Standard Time)

Hello @varshanharshank , are these cypress containers? Can you please describe in more detail exactly what you are doing and what steps you are taking? Please also share any debugging steps you have tried.

varshanharshank · Answer 2 · Thu May 04 2023 09:50:25 GMT+0800 (China Standard Time)

Hello @varshanharshank , are these cypress containers? Can you please describe in more detail exactly what you are doing and what steps you are taking? Please also share any debugging steps you have tried.

The below docker image is used for executing the cypress scripts via Jenkins. I have successfully pulled this image in Jenkins but it is showing that container is not running

cypress/browsers:node18.12.0-chrome103-ff107
cypress/browsers:node18.12.0-chrome106-ff106
cypress/browsers:node18.12.0-chrome107
cypress/browsers:node18.6.0-chrome105-ff104

Getting the following error "The Cypress App could not be unzipped" while using the below image in Jenkins

cypress/browsers:node16.18.0-chrome107-ff106-edge
cypress/browsers:node16.16.0-chrome107-ff107-edge

Mike McCready · Answer 3 · Sat May 13 2023 01:43:37 GMT+0800 (China Standard Time)

Example repo cypress-io/cypress-example-kitchensink uses the Docker image

cypress/browsers:node18.12.0-chrome107

in .github/workflows/chrome-docker.yml
and runs successfully with it, as the log for job 8873770843 shows. So it seems there is nothing wrong with the Docker images themselves.

Mark Noonan · Answer 4 · Tue May 16 2023 02:50:28 GMT+0800 (China Standard Time)

@varshanharshank I would look into the error message itself "Target directory is expected to be absolute"

I found a similar error and comment that appears to solve it here: cypress-io/cypress#2691 (comment)

A lot might have changed in 5 years but it seems your solution would be to provide an absolute path in some similar way to this. Let me know if this works for you.

Mark Noonan · Answer 5 · Tue May 23 2023 04:38:10 GMT+0800 (China Standard Time)

I'm going to close this one for now until we have some more information that there is definitely a problem. Please comment back here if there is more to do from the Cypress side.