webdriverio: [🐛 Bug]: Chrome testing fails on Gitlab CI, but not locally

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

WebdriverIO Version

latest

Node.js Version

18.17.1

Mode

WDIO Testrunner

Which capabilities are you using?

No response

What happened?

I’ve setup a small example repo to use WebDriverIO with chrome for a vite project with lit components here. The test passes locally, but when running on Gitlab CI the execution stops. See the error message below (see whole log here).

Are there conflicts because of incompatible versions? I don’t really know what I’m doing on Gitlab CI.

What is your expected behavior?

No response

How to reproduce the bug.

To reproduce the bug, you can fork the gitlab repo and then push a commit to trigger the ci pipeline.

Relevant log output

[0-0] 2024-02-07T20:14:05.133Z WARN webdriver: Request failed with status 500 due to session not created: Chrome failed to start: exited normally.
[0-0]   (session not created: DevToolsActivePort file doesn't exist)
[0-0]   (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)

Code of Conduct

• I agree to follow this project’s Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues