How to use The "Chrome For Test" in the Docker File to verify the scripts in the Jenkins

[SivaAdaveni91]

How to use The "Chrome For Test" in the Docker File to verify the scripts in the Jenkins:

We are using Docker to install the Chrome browser/driver in the Chrome browser and execute the script on Jenkins (Linux).
But unable to use the "Chrome For Test" in the docker.
Please suggest the steps on how we can use chrome for testing in the docker to execute the scripts in Jenkins.

[christian-bromann]

Can you provide more information why you are unable to use "Chrome For Test"? This feature is integrated into WebdriverIO which takes care of downloading browser and driver for you.

[SivaAdaveni91]

Hi @christian-bromann ,
In the local environment, we are able to use "Chrome For Test". However we are unable to execute the script in the pipeline.
To execute the scripts in Chrome in the pipeline we are downloading the Chrome using Docker.

First, we tried, to execute the scripts in the pipeline after adding "chrome for Test" capabilities in the conf file. but got a "Chrome Crashed Error".
So, we are trying to add the "chrome for test" line of code in the docker file to download and execute the scripts on the pipeline.

Previous Docker file with "Google Chrome Stable":

Pipeline Error after adding "chrome for test" in the "wdio.conf" file and commented previous chrome code in the docker file as like above:

Please help us, to resolve the issue.

[christian-bromann]

after adding "chrome for test" in the "wdio.conf"

What do you mean by this?

[SivaAdaveni91]

Hi @christian-bromann ,
means, i have added following lines of code in the "wdio.conf.ts" file under capabilities:
browserName: 'chrome',
browserVersion: 'stable',

after adding, the script is working locally. but unable to use the "chrome for test" in the Jenkins.
Can you please suggest how we pass the "chrome for test" and install it in Jenkins to execute the Webdriverio scripts.

[christian-bromann]

Please provide available WebdriverIO logs that help identify the problem.

[denemorhun-tc]

We are seeing some very similar issue. Wdio's puppeteer seems to install chrome under /tmp within a docker structure, and it's not able to launch afterwards:

Execution of 6 workers started at 2023-09-12T21:40:31.862Z

[0-2] default
[0-4] default
[0-0] default
[0-5] default
[0-1] default
[0-3] default
[0-4] RUNNING in chrome - file:///test/specs/prodhc/pricing.spec.ts
[0-4] 2023-09-12T21:41:47.510Z ERROR webdriver: Request failed with status 500 due to unknown error: unknown error: Chrome failed to start: crashed.
[0-4] (unknown error: DevToolsActivePort file doesn't exist)
[0-4] (The process started from chrome location /tmp/chrome/linux-116.0.5845.96/chrome-linux64/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
[0-4] 2023-09-12T21:41:47.532Z ERROR webdriver: unknown error: unknown error: Chrome failed to start: crashed.
[0-4] (unknown error: DevToolsActivePort file doesn't exist)
[0-4] (The process started from chrome location /tmp/chrome/linux-116.0.5845.96/chrome-linux64/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
[0-4] at getErrorFromResponseBody (file:///app/node_modules/webdriver/build/utils.js:194:12)
[0-4] at NodeJSRequest._request (file:///app/node_modules/webdriver/build/request/index.js:164:23)
[0-4] at processTicksAndRejections (node:internal/process/task_queues:96:5)
[0-4] at async startWebDriverSession (file:///app/node_modules/webdriver/build/utils.js:63:20)
[0-4] at async Function.newSession (file:///app/node_modules/webdriver/build/index.js:27:45)
[0-4] at async remote (file:///app/node_modules/webdriverio/build/index.js:45:22)
[0-4] at async Runner._startSession (file:///app/node_modules/@wdio/runner/build/index.js:224:29)
[0-4] at async Runner._initSession (file:///app/node_modules/@wdio/runner/build/index.js:190:25)
[0-4] at async Runner.run (file:///app/node_modules/@wdio/runner/build/index.js:79:19)
[0-4] 2023-09-12T21:41:47.564Z ERROR @wdio/runner: Error: Failed to create session.
[0-4] unknown error: Chrome failed to start: crashed.
[0-4] (unknown error: DevToolsActivePort file doesn't exist)
[0-4] (The process started from chrome location /tmp/chrome/linux-116.0.5845.96/chrome-linux64/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
[0-4] at startWebDriverSession (file:///app/node_modules/webdriver/build/utils.js:68:15)
[0-4] at processTicksAndRejections (node:internal/process/task_queues:96:5)
[0-4] at async Function.newSession (file:///app/node_modules/webdriver/build/index.js:27:45)
[0-4] at async remote (file:///app/node_modules/webdriverio/build/index.js:45:22)
[0-4] at async Runner._startSession (file:///app/node_modules/@wdio/runner/build/index.js:224:29)
[0-4] at async Runner._initSession (file:///app/node_modules/@wdio/runner/build/index.js:190:25)
[0-4] at async Runner.run (file:///app/node_modules/@wdio/runner/build/index.js:79:19)
[0-4] FAILED in chrome - file:///test/specs/prodhc/pricing.spec.ts
[0-2] RUNNING in chrome - file:///test/specs/prodhc/home.spec.ts
[0-3] [@faker-js/faker]: faker.random.alphaNumeric() is deprecated since v8.0 and will b

[denemorhun-tc]

I've noticed this problem only occurs on M1 / M2 apple silicon and not on intel machines.

[provsateeshayyagari]

docker run --rm --entrypoint '' 6f9934413f08 /bin/bash -c '/usr/bin/google-chrome --headless --disable-gpu --no-sandbox'
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[1025/015057.991744:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[1025/015058.060979:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Function not implemented (38)
Assertion failed: p_rcu_reader->depth != 0 (/qemu/include/qemu/rcu.h: rcu_read_unlock: 101)

Below is the actual test execution in docker on Apple M1 chip

docker run --rm --entrypoint '' 6f9934413f08 /bin/bash -c 'npm test -- /app/wdio.conf.local_headless.js --spec /app/tests/BotClose-NEW.js'
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

qasawebdriverio@0.0.1 test
wdio /app/wdio.conf.local_headless.js --spec /app/tests/BotClose-NEW.js

Browser Version: Google Chrome 118.0.5993.88
Chrome driver version: 118.0.5993.70

Execution of 1 workers started at 2023-10-25T01:52:00.562Z

2023-10-25T01:52:00.700Z INFO @wdio/cli:launcher: Run onPrepare hook
2023-10-25T01:52:00.708Z INFO @wdio/utils: Setting up browser driver for: chrome@stable
2023-10-25T01:52:00.736Z INFO @wdio/utils: Setting up browser binaries for: chrome@stable
2023-10-25T01:52:01.643Z INFO webdriver: Downloading Chromedriver v118.0.5993.88
2023-10-25T01:52:02.949Z INFO webdriver: Downloading Chromedriver 0.19%
2023-10-25T01:52:04.014Z INFO webdriver: Downloading Chromedriver 2.17%
2023-10-25T01:52:05.066Z INFO webdriver: Downloading Chromedriver 5.14%
2023-10-25T01:52:06.115Z INFO webdriver: Downloading Chromedriver 9.70%
2023-10-25T01:52:07.263Z INFO webdriver: Downloading Chromedriver 11.48%
2023-10-25T01:52:08.298Z INFO webdriver: Downloading Chromedriver 12.67%
2023-10-25T01:52:09.371Z INFO webdriver: Downloading Chromedriver 14.26%
2023-10-25T01:52:10.416Z INFO webdriver: Downloading Chromedriver 16.44%
2023-10-25T01:52:11.569Z INFO webdriver: Downloading Chromedriver 19.01%
2023-10-25T01:52:12.736Z INFO webdriver: Downloading Chromedriver 20.00%
2023-10-25T01:52:13.826Z INFO webdriver: Downloading Chromedriver 21.39%
2023-10-25T01:52:14.912Z INFO webdriver: Downloading Chromedriver 23.77%
2023-10-25T01:52:16.034Z INFO webdriver: Downloading Chromedriver 26.54%
2023-10-25T01:52:17.087Z INFO webdriver: Downloading Chromedriver 28.13%
2023-10-25T01:52:18.181Z INFO webdriver: Downloading Chromedriver 29.51%
2023-10-25T01:52:19.254Z INFO webdriver: Downloading Chromedriver 31.49%
2023-10-25T01:52:20.314Z INFO webdriver: Downloading Chromedriver 33.67%
2023-10-25T01:52:21.389Z INFO webdriver: Downloading Chromedriver 36.65%
2023-10-25T01:52:22.528Z INFO webdriver: Downloading Chromedriver 38.03%
2023-10-25T01:52:23.602Z INFO webdriver: Downloading Chromedriver 39.42%
2023-10-25T01:52:24.670Z INFO webdriver: Downloading Chromedriver 41.60%
2023-10-25T01:52:25.738Z INFO webdriver: Downloading Chromedriver 44.57%
2023-10-25T01:52:26.762Z INFO webdriver: Downloading Chromedriver 46.75%
2023-10-25T01:52:27.806Z INFO webdriver: Downloading Chromedriver 47.94%
2023-10-25T01:52:28.926Z INFO webdriver: Downloading Chromedriver 49.52%
2023-10-25T01:52:29.990Z INFO webdriver: Downloading Chromedriver 51.50%
2023-10-25T01:52:30.995Z INFO webdriver: Downloading Chromedriver 54.48%
2023-10-25T01:52:32.009Z INFO webdriver: Downloading Chromedriver 56.26%
2023-10-25T01:52:33.093Z INFO webdriver: Downloading Chromedriver 57.45%
2023-10-25T01:52:34.185Z INFO webdriver: Downloading Chromedriver 59.03%
2023-10-25T01:52:35.251Z INFO webdriver: Downloading Chromedriver 61.21%
2023-10-25T01:52:36.328Z INFO webdriver: Downloading Chromedriver 63.79%
2023-10-25T01:52:37.537Z INFO webdriver: Downloading Chromedriver 65.18%
2023-10-25T01:52:38.650Z INFO webdriver: Downloading Chromedriver 67.16%
2023-10-25T01:52:39.710Z INFO webdriver: Downloading Chromedriver 69.53%
2023-10-25T01:52:40.719Z INFO webdriver: Downloading Chromedriver 72.90%
2023-10-25T01:52:41.830Z INFO webdriver: Downloading Chromedriver 75.48%
2023-10-25T01:52:42.913Z INFO webdriver: Downloading Chromedriver 76.67%
2023-10-25T01:52:43.936Z INFO webdriver: Downloading Chromedriver 78.25%
2023-10-25T01:52:44.944Z INFO webdriver: Downloading Chromedriver 80.63%
2023-10-25T01:52:46.017Z INFO webdriver: Downloading Chromedriver 84.00%
2023-10-25T01:52:47.147Z INFO webdriver: Downloading Chromedriver 86.18%
2023-10-25T01:52:48.156Z INFO webdriver: Downloading Chromedriver 87.56%
2023-10-25T01:52:49.185Z INFO webdriver: Downloading Chromedriver 89.74%
2023-10-25T01:52:50.207Z INFO webdriver: Downloading Chromedriver 92.71%
2023-10-25T01:52:51.227Z INFO webdriver: Downloading Chromedriver 96.68%
2023-10-25T01:52:52.349Z INFO webdriver: Downloading Chromedriver 98.46%
2023-10-25T01:52:54.147Z INFO @wdio/cli:launcher: Run onWorkerStart hook
2023-10-25T01:52:54.155Z INFO @wdio/local-runner: Start worker 0-0 with arg: /app/wdio.conf.local_headless.js,--spec,/app/tests/BotClose-NEW.js
[0-0] 2023-10-25T01:52:59.623Z INFO @wdio/local-runner: Run worker command: run
[0-0] Browser Version: Google Chrome 118.0.5993.88
[0-0] Chrome driver version: 118.0.5993.70
[0-0] RUNNING in chrome - file:///tests/BotClose-NEW.js
[0-0] 2023-10-25T01:53:04.503Z INFO webdriver: Initiate new session using the WebDriver protocol
[0-0] 2023-10-25T01:53:05.418Z INFO webdriver: Using Chromedriver v118.0.5993.88 from cache directory /tmp
[0-0] 2023-10-25T01:53:06.526Z INFO @wdio/utils: Started Chromedriver v118.0.5993.88 with params --port=42327 --allowed-origins=* --allowed-ips=0.0.0.0 in 2019ms on port 42327
[0-0] 2023-10-25T01:53:06.797Z INFO webdriver: [POST] http://0.0.0.0:42327/session
[0-0] 2023-10-25T01:53:06.798Z INFO webdriver: DATA {
[0-0] capabilities: {
[0-0] alwaysMatch: { browserName: 'chrome', 'goog:chromeOptions': [Object] },
[0-0] firstMatch: [ {} ]
[0-0] },
[0-0] desiredCapabilities: {
[0-0] browserName: 'chrome',
[0-0] 'goog:chromeOptions': {
[0-0] binary: '/usr/bin/google-chrome',
[0-0] prefs: [Object],
[0-0] args: [Array]
[0-0] }
[0-0] }
[0-0] }
[0-0] 2023-10-25T01:53:08.736Z 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.)
[0-0] 2023-10-25T01:53:08.737Z INFO webdriver: Retrying 1/3
[0-0] 2023-10-25T01:53:08.738Z INFO webdriver: [POST] http://0.0.0.0:42327/session
[0-0] 2023-10-25T01:53:08.740Z INFO webdriver: DATA {
[0-0] capabilities: {
[0-0] alwaysMatch: { browserName: 'chrome', 'goog:chromeOptions': [Object] },
[0-0] firstMatch: [ {} ]
[0-0] },
[0-0] desiredCapabilities: {
[0-0] browserName: 'chrome',
[0-0] 'goog:chromeOptions': {
[0-0] binary: '/usr/bin/google-chrome',
[0-0] prefs: [Object],
[0-0] args: [Array]
[0-0] }
[0-0] }
[0-0] }
[0-0] 2023-10-25T01:53:10.541Z 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.)
[0-0] 2023-10-25T01:53:10.543Z INFO webdriver: Retrying 2/3
[0-0] 2023-10-25T01:53:10.543Z INFO webdriver: [POST] http://0.0.0.0:42327/session
[0-0] 2023-10-25T01:53:10.544Z INFO webdriver: DATA {

[christian-bromann]

It seems like you try to emulate Google Chrome amd64 with Docker on your arm64 system. Could also be that you run amd64 Chrome inside your arm64 docker container.

Since Google Chrome is only available for amd64, we recommend using Chromium since its available for arm64 as well.

[provsateeshayyagari]

Will "Google chrome" capabilities work for chromium as well? In saucelabs platform configuration, I do not see an option for chromium.

[christian-bromann]

You are running your tests in Docker , why do you use Sauce Labs Platform configurator? It shows the browser that are supported by Sauce Labs. You can run in Chromium by setting browserName: 'chromium'

[swtestacademy]

We are also stucking here:

[0-0] 2023-11-14T10:20:20.190Z INFO webdriver: Setting up Chrome v119.0.6045.105
[0-0] 2023-11-14T10:20:20.192Z INFO webdriver: Using Chromedriver v119.0.6045.105 from cache directory /tmp

Both in Docker in M1 machine and Jenkins in Linux AWS servers. We are debugging and trying to solve for the last 4 days.