Welcome message displayed every time I start Docker container

[the0neWhoKnocks]

I've seen discussion 1 and discussion 2, and I haven't found a solution in the docs.

I run v13.3.0 with open --e2e --browser electron --project ., and every time I'm presented with the "What's New in Cypress" screen, which can delay the start of me running tests because it's loading an external page with a video. I can understand if it does this once when a new version is run, but every time is too much.

Is there a way to bypass that screen, or does Cypress remember that this screen was viewed and I just need to persist that data via a Docker mount or something?

[jennifer-shehane]

It's an attribute we keep track of in the AppData called majorVersionWelcomeDismissed, with an object where 13 would track when it was dismissed. I'd check your local AppData for a global state.json file that contains this info and maybe copy that to the docker container. Haven't tried this though.

Open Cypress via cypress open
Go to Developer Tools -> View App Data

[the0neWhoKnocks]

Hm, when I click on View App Data the container crashes with this error:

Exited with code 4
Error: Exited with code 4
    at ChildProcess.<anonymous> (<embedded>:3180:421654)
    at Object.onceWrapper (node:events:628:26)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at Socket.<anonymous> (node:internal/child_process:449:11)
    at Socket.emit (node:events:513:28)
    at Pipe.<anonymous> (node:net:322:12)

[the0neWhoKnocks]

Do you have an idea of what the file path for state.json is within the Docker image?

[the0neWhoKnocks]

After digging around other posts, some trial and error, I ended up with this:

// [state.json]

{
  "majorVersionWelcomeDismissed": {
    "13": 1696614696387
  }
}

# [Dockerfile]

# Added at bottom of e2e specific Dockerfile to ensure quick builds in case any other state changes are required in the future.
COPY --chown=node:node ./state.json /home/node/.config/Cypress/cy/production/projects/__global__/

Ideally this should be configurable via an environment variable. It's not great that a User has to build a custom image just to disable this.