Latest ppiper/node-browsers:24-bookworm image causes wdi5 to not start at all [Jenkins]

Start by comparing the Dockerfile and image changes between the working and breaking commits, then reproduce the Jenkins WDI5 run using each image version. The issue is resolved when the latest ppiper/node-browsers:24-bookworm image starts the WDI5 workers and completes the same WebDriver test run without requiring the pinned image.

Hi colleagues,

We are using a piper step to run WDI5 Tests in our Jenkins Pipeline.
Suddenly, with the laster docker image of ppiper/node-browsers:24-bookworm they stopped running at all.

3:56:30 > wdio run wdio.conf.js --suite systemTests --ci
13:56:30
13:56:31 ◇ injecting env (0) from .env // tip: ⌁ auth for agents [www.vestauth.com]
13:56:31 2026-05-27T11:56:31.617Z DEBUG @wdio/utils:initializeServices: initialize service "ui5" as NPM package
13:56:31 2026-05-27T11:56:31.639Z INFO @wdio/cli:launcher: Run onPrepare hook
13:56:32 2026-05-27T11:56:31.723Z DEBUG @wdio/cli:utils: Finished to run "onPrepare" hook in 0ms
13:56:32
13:56:32 Execution of 11 workers started at 2026-05-27T11:56:31.734Z
13:56:32
13:56:32 2026-05-27T11:56:31.812Z INFO @wdio/utils: Setting up browser driver for: chrome@stable
13:56:32 2026-05-27T11:56:31.823Z INFO @wdio/utils: Setting up browser binaries for: chrome@stable
13:56:32 2026-05-27T11:56:31.948Z INFO webdriver: Downloading Chromedriver v148.0.7778.178
13:56:33
13:56:33
13:56:33 Ended WebDriver sessions gracefully after a SIGINT signal was received!

No test was running, the issue appeared over night and we noticed that it is because of the latest changes to docker image "ppiper/node-browsers:24-bookworm".

Breaking commit: sha256__4835b6718bec46634ca305a2a14b1ebadf1f4279e083619fc5bae5d7eb4626a4
Working commit: sha256__657689e0b04a044955bcbf8f396afe95024dec27af5f2ed4046a1688f03de891

So we pinned the old version but obviously it cannot stay like this. Could you please support us here?

Thanks and best regards,
Anna