Describe and demonstrate base and browsers non-root usages

[MikeMcC399]

What would you like?

Describe and demonstrate how to use cypress/base and cypress/browsers Docker images with a non-root user. Discuss workarounds for Cypress' issues running in read-only environments.

Why is this needed?

Currently only the cypress/included README contains a section with the linked example examples/included-as-non-root demonstrating how to run cypress/included with the built-in node user.

There is no equivalent description and example using cypress/base and cypress/browsers Docker images with the node non-root user.

Other

When running from a custom Docker image built from either a cypress/base or a cypress/browsers Docker image, using a Dockerfile, the following issues may be encountered, due to the default Docker build process using the root user, leaving a non-root user such as node only read access:

• Failure due to Cypress issue Cypress fails verification if directory for binary_state.json is read-only cypress#30684
• Warning due to Cypress issue Read-only warning given even when screenshots and videos folders writable cypress#30810

[MikeMcC399]

• Failure due to Cypress issue Cypress fails verification if directory for binary_state.json is read-only cypress#30684 is now described in EACCES permission denied binary_state.json (PR docs: add binary_state.json permission denied known problem #1274).

• Warning due to Cypress issue Read-only warning given even when screenshots and videos folders writable cypress#30810 is now described in examples/included-as-non-root> GitHub Actions and the example project is configured to be able to write screenshots with a non-root user and a non-writable project (PR test: set up included-non-root example screenshot #1273).