Frequent EACCES: permission denied errors with Docker image cypress/included:9.1.1

[mauricedb]

Recently I have been seeing frequent EACCES: permission denied errors while running GitHub actions.

They all seem to be around the /root/.cache/Cypress folder. I am under the impression this started when Cypress 9.0.0 was released.

Some examples:

• https://github.com/mauricedb/ts-react/runs/4531029507?check_suite_focus=true
• https://github.com/mauricedb/ts-react/runs/4530723435?check_suite_focus=true

This only seems to happen in GitHub Actions that are using the cypress/included:9 Docker image. Other ones that don't use the Docker image run just fine.

[FabianBruengerDedalus2]

Hey, i just wanted du fire up (almost) the same issue. I am running the image 9.1.1 as a job container:

(The image is cypress/included:9.1.1, just the wrong screenshot)

And then i am trying to start cypress:

This is my error:

If i am running the container manually on my machine everything works fine. I would appreciate some help.

Cheers

[mauricedb]

FYI. This is still happening with the Cypress 9.2.0 images.
[FAILED] EACCES: permission denied, unlink '/root/.cache/Cypress/9.2.0/binary_state.json'

The same build running with image: cypress/included:8.7.0 works just fine.

[FabianBruengerDedalus2]

Hi @mauricedb, thx for the info. I also tested older version and it is running fine, I just missed to put the info here. I am also running on 8.7.0 now. I hope this is fixed soon. Cheers!

[mjhenkes]

Can you try the work around mentioned here: cypress-io/github-action#446 (comment)

configuring the job to run as a non root user.

[FabianBruengerDedalus2]

Hi @mjhenkes,
this is not working. But i found finally a workaround even for the 9.2.0:

chmod -R 777 /github/home

If you have tests which are creating folders you probably will run into the same kind of issues. Then also give full permissions to the target folders.

[mmahalwy]

@FabianBruengerDedalus2 where did you run that? example?

[ohueter]

Can you try the work around mentioned here: cypress-io/github-action#446 (comment)

configuring the job to run as a non root user.

That worked for me using the cypress/browsers:node16.5.0-chrome94-ff93 image, thank you!

[FabianBruengerDedalus2]

@FabianBruengerDedalus2 where did you run that? example?

example_step:
    name: Example
    runs-on: [self-hosted]
    container:
      image: cypress/included:9.2.0

    steps:
      # Init
      - name: Checkout project
        uses: actions/checkout@v2

      # This workaround is required for running npm install and cypress because of some kind of bug in the new cypress included images (or might be the node version!)
      - name: Set permissions
        run: |
          chmod -R 777 /github/home
          chmod -R 777 cypress
          
      # Start the actual cypress tests
      - name: Run Tests
        uses: cypress-io/github-action@v2
        timeout-minutes: 120
        with:
          install: false
          command: npm run cy:chrome

[humoyun91]

I had the same issue and tried above mentioned solutions but did not work for me. By adding CYPRESS_CACHE_FOLDER and defining non-root user options: --user 1001 I managed to pass this issue:

cypress-tests:
  runs-on: ubuntu-latest
  container:
    image: cypress/included:9.5.4
    options: --user 1001 # setting this user is also important
  steps:
    - name: checkout
      uses: actions/checkout@v3

    - name: cache node modules
      uses: actions/cache@v3
      with:
        path: ~/.npm
        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/yarn.lock') }}
        restore-keys: |
          ${{ runner.os }}-build-${{ env.cache-name }}-
          ${{ runner.os }}-build-
          ${{ runner.os }}-

    - name: Cypress run
      id: cy-e2e-tests
      uses: cypress-io/github-action@v2
      env:
        CYPRESS_CACHE_FOLDER: '${GITHUB_WORKSPACE}/.cypress-cache' # this line fixed the problem
        GITHUB_TOKEN: ${{ secrets.COMPANY_TOKEN }}
        REACT_APP_DEPLOYMENT_PHASE: development

[Dottenpixel]

I'm using a playwright image and landed here googling the error message
> options: --user 1001 did the trick for me! Thx @humoyun91 !!

[gkatsanos]

None of the proposed workarounds work.

1. options: --user 1001

- name: Reclaim cache directory
   run: chown -R 1001:1001 /github/home/.cache && echo "pwn dat cache"

using a self-hosted runner (simple linux instance ) and tried all images from node 16.x and above..

[MikeMcC399]

Closing this issue, as Cypress GitHub Actions now documents

Include options: --user 1001 to avoid permissions issues.

The issue from @gkatsanos #560 (comment) appears to have a separate root cause as recent tests showed that GitHub-hosted runners had no problem.