Hmmm, I just asked a question and the message seems to have disappeared. I'm running into a session cookie issue on a multi-container/domain setup where I have a Rails application running on the build container and a service container running the Frontend application. From the build perspective, the backend is running on http://localhost:3000 and the frontend is running on http://frontend:3002. I have an e2e that is essentially "Log in and see some protected content" that is working fine for me locally. I'm using the experimentalSessionAndOrigin features to deal with the origin changing after login since the login page is on the rails application and the user is redirected to the frontend application. On CI, the session cookie is created with SameSite=Lax and CORS is setup properly. I have a working cucumber test suite with this exact same setup in CI. Does anyone know if there Is something additional I need to configure for this setup with Cypress?

are you doing CI in their cloud, or via the gitlab runner? what version of cypress are you running?

This is a self-hosted version of Gitlab using gitlab runner.