feat: update to Debian 12 (bookworm)

[MikeMcC399]

• closes Update from Debian 11 bullseye to Debian 12 bookworm #937

Issue

Cypress Docker Images are currently built based on debian:bullseye-slim (Debian 11) from https://hub.docker.com/_/debian

cypress-docker-images/factory/.env

Lines 7 to 8 in b952572

	# The debian image the factory is based on
	BASE_IMAGE='debian:bullseye-slim'

• This relies on using Debian 11 codenamed bullseye which is the oldstable release
• Debian 12 codenamed bookworm is the current stable release and it was originally released almost one year ago on June 10th, 2023.

The Cypress Docker images need to transition to using the Debian stable release 12 (bookworm).

Changes

In factory/.env:

1. FACTORY_VERSION is updated to 4.0.0 since it is a major change moving from Debian 11 (bullseye) to Debian 12 (bookworm).
2. BASE_IMAGE is updated to debian:12-slim (long-term equivalent to debian:bookworm-slim, current equivalent to debian:12.5-slim)
3. FACTORY_DEFAULT_NODE_VERSION is updated to 20.13.1 LTS, released May 9, 2024 Edit: This update is already done.
4. Git version check updated to 2.39.2 for Debian 12

Verification

On Ubunu 22.04.4 LTS, Node.js v20.13.1 LTS

Execute:

cd factory
docker compose build factory
docker compose build

and confirm that all images are built without errors or warnings.

Continue with

cd test-project
set -a && . ../.env && set +a
docker compose run test-factory-all-included

and confirm that the image builds without errors or warnings and runs successfully.

References

• https://www.debian.org/releases/
• https://hub.docker.com/_/debian

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[MikeMcC399]

Tests exhibit flake

test-image-medium-browsers-test-browsers-edge failed once with the following error. On re-run, it passed.

  Running:  2-advanced-examples/querying.cy.js                                            (13 of 20)
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.

Timed out waiting for the browser to connect. Retrying...
Missing browserCriClient in connectToNewSpec
Error: Missing browserCriClient in connectToNewSpec
    at Object.connectToNewSpec (<embedded>:4407:48611)
    at Object.connectToNewSpec (<embedded>:4407:27043)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async v.relaunchBrowser (<embedded>:4492:37697)

Exited with code exit status 1

[MikeMcC399]

Should we proceed with this PR? Are there any other tests needed?

[jennifer-shehane]

@MikeMcC399 We're going to have @AtofStryker take a look if he has some time this iteration.

[MikeMcC399]

@jennifer-shehane

We're going to have @AtofStryker take a look if he has some time this iteration.

Very good!

I'm going to be pushing through a few clean-up PRs in the meantime. They should not affect the Debian 12 PR in content though.

[MikeMcC399]

• I've opened a separate issue XDG_RUNTIME_DIR error in Debian 12.x headless cypress#29554 regarding the test flakiness. I don't expect that this can be solved by doing anything with Docker. Possibly an Electron update may help, since this is only happening in a headless environment where Xvfb comes into play.

[MikeMcC399]

@AtofStryker

What do you think about merging this PR?

[AtofStryker]

@AtofStryker

What do you think about merging this PR?

I should be able to give it a thorough review today. Sorry for the delay!

[AtofStryker]

gave the factory a build, along with all other images in the docker-compose on my amd64 Ubuntu 22.04.4 machine and ran the included docker image in addition. Everything works as expected. Thank you @MikeMcC399

[MikeMcC399]

@AtofStryker

Thanks for your tests and the merge! It was good to see that the merge into master went without error!