Driver isn't created when using @DockerBrowser with browser type "CHROME" on macOS.

[David91]

I'm not able to run a test when docker browser type is set to CHROME:
When I set the Browser type to chrome, driver isn't being initialized and after first usage of driver NullPointerException appears, as the driver is null.

Browser and version: Chrome in docker - chrome_99.0

Operating system: macOS Monterey 12.3, chip - Apple M1 Pro

Selenium-Jupiter version: Currently, the latest version - 4.1.0

Selenium-Jupiter use:

Error trace:

NOTE:

I'm not 100% sure that this is an exact selenium-jupiter problem, but when specifying type FIREFOX, driver gets created successfully. And also plus, after setting "vnc" to true still there is no noVNC URL generated.

[bonigarcia]

I have just made some quick test and it seems working, at least when using Windows or Linux. I don't have a macOS to test it. To discover the problem, I would need to see your Selenium-Jupiter traces. I mean something like this:

2022-03-22 17:07:16 [ForkJoinPool-1-worker-9] DEBUG i.g.b.wdm.docker.DockerHubService.listTags(60) - Getting browser image list from Docker Hub
2022-03-22 17:07:17 [ForkJoinPool-1-worker-9] DEBUG i.g.b.wdm.docker.DockerService.getImageVersionFromDockerHub(440) - The latest version of Chrome in Docker Hub is 99.0
2022-03-22 17:07:17 [ForkJoinPool-1-worker-9] INFO  i.g.b.wdm.docker.DockerService.pullImageIfNecessary(299) - Pulling Docker image selenoid/vnc:chrome_99.0 (this might take some time, but only the first time)
2022-03-22 17:07:58 [ForkJoinPool-1-worker-9] DEBUG i.g.b.wdm.cache.ResolutionCache.putValueInResolutionCacheIfEmpty(119) - Storing resolution chrome-container-latest=99.0 in cache (valid until 18:07:58 22/03/2022 CET)
2022-03-22 17:07:58 [ForkJoinPool-1-worker-9] INFO  i.g.b.wdm.docker.DockerService.startContainer(173) - Starting Docker container selenoid/vnc:chrome_99.0
2022-03-22 17:08:00 [ForkJoinPool-1-worker-9] DEBUG i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(77) - Creating WebDriver object for chrome at http://localhost:49153/ with Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu], extensions: []}}
Mar 22, 2022 5:08:01 PM org.openqa.selenium.remote.tracing.opentelemetry.OpenTelemetryTracer createTracer
INFO: Using OpenTelemetry for tracing
Mar 22, 2022 5:08:02 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected dialect: W3C
2022-03-22 17:08:02 [ForkJoinPool-1-worker-9] DEBUG i.g.b.wdm.webdriver.WebDriverCreator.getSessionId(115) - The sessionId is 5b0affce8a176444877da1257700368a
2022-03-22 17:08:03 [ForkJoinPool-1-worker-9] DEBUG i.g.bonigarcia.wdm.WebDriverManager.quit(911) - Quitting RemoteWebDriver: chrome on LINUX (5b0affce8a176444877da1257700368a)
2022-03-22 17:08:03 [ForkJoinPool-1-worker-9] INFO  i.g.b.wdm.docker.DockerService.stopAndRemoveContainer(323) - Stopping Docker container selenoid/vnc:chrome_99.0

[David91]

Hi. Thank you for quick response.
Unfortunately what is represented in the screenshot is the all that has been generated during run. I've also tried to run the test from command line ( build tool is gradle ) using "-i" option, but still no Selenium-jupiter traces :/

[bonigarcia]

For getting the Selenium-Jupiter logs, you need to include a Logback configuration file (for example, like this) in your project classpath. The name of this file should be src/test/resources/logback-test.xml (if you want logs only for your tests) or src/test/resources/logback.xml (if you want logs for both tests and application code).

After that, when running a test, you should see the traces as described before.

For further info about logging with with SLF4J and Logback you can see the following tutorial.

[David91]

Ah, thank you. Now I get logs:

2022-03-23 17:03:55 [Test worker] DEBUG i.g.b.wdm.cache.ResolutionCache.checkKeyInResolutionCache(186) -- Resolution chrome-container-latest=99.0 in cache (valid until 17:54:21 23/03/2022 AMT)
2022-03-23 17:03:55 [Test worker] INFO  i.g.b.wdm.docker.DockerService.startContainer(173) -- Starting Docker container selenoid/vnc:chrome_99.0
2022-03-23 17:03:55 [Test worker] DEBUG i.g.b.wdm.docker.DockerService.startBrowserContainer(667) -- VNC server URL: vnc://localhost:55031/
2022-03-23 17:03:55 [Test worker] DEBUG i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(77) -- Creating WebDriver object for chrome at http://localhost:55032/ with Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu], extensions: []}}

And here what displays after redirecting to http://localhost:55032/

{"value":{"error":"unknown command","message":"unknown command: unknown command: ","stacktrace":"#0 0x0040006a17d3 \u003Cunknown>\n#1 0x0040003fd688 \u003Cunknown>\n#2 0x00400044ee11 \u003Cunknown>\n#3 0x00400044eb77 \u003Cunknown>\n#4 0x0040003d41d4 \u003Cunknown>\n#5 0x0040003d5020 \u003Cunknown>\n#6 0x0040006d249d \u003Cunknown>\n#7 0x0040006eb60c \u003Cunknown>\n#8 0x0040006d4205 \u003Cunknown>\n#9 0x0040006ebee5 \u003Cunknown>\n#10 0x0040006c8070 \u003Cunknown>\n#11 0x0040003d3d49 \u003Cunknown>\n#12 0x004002a730b3 \u003Cunknown>\n"}}

[bonigarcia]

Not sure about VNC, but the driver instance seems to be properly created.

[David91]

If it had been created, then driver wouldn't be null I guess. Despite the logs show that WebDriver object is created, actually after redirecting with that URL error message is shown which I pasted in my previous comment:

For browser type of FIREFOX noVNC URL is generated successfully and the Webdriver object is created at this URL properly, because code gets executed successfully.

[David91]

I'm sorry for non-informative logs, somehow didn't place the right screenshot.
Here it's shown that an error occurred while creating WebDriver object for chrome. And the same is for other browsers - Opera, Safari ... ( except Firefox )

[bonigarcia]

It seems the Docker container with the browser cannot be started. I don't know what the problem is, and unfortunately, I don't have a Mac to test with. If you want, you can try the following alternatives to try to discover the problem:

1. Run the following command in the shell, which should be equivalent to what is done by WebDriverManager through Selenium-Jupiter:

docker run --rm --cap-add=SYS_ADMIN -p 4444:4444 -p 5900:5900 -e ENABLE_VNC=true selenoid/vnc:chrome_99.0

Then, you should be able to connect with the browser, for example checking the following URL:

http://localhost:4444/status

2. Change the logging level to TRACE, including the following line in your Logback configuration file:

<logger name="io.github.bonigarcia" level="TRACE" />

Then, run the test again, and copy the traces here. Thank you.

[David91]

Thank you for response.

1. By running your specified command, container has been started successfully and the /status URL also shows it.

2. Here are the logs with level TRACE:

2022-03-24 18:42:46 [Test worker] TRACE i.g.b.seljup.SeleniumJupiter.resolveParameter(151) -- Resolving parameter org.openqa.selenium.WebDriver arg0 (contextId [engine:junit-jupiter]/[class:tests.DockerBrowserTest], index 0)
2022-03-24 18:42:46 [Test worker] TRACE i.g.bonigarcia.seljup.config.Config.getProperty(121) -- Property key sel.jup.selenium.server.url not found, using default value
2022-03-24 18:42:46 [Test worker] TRACE i.g.b.seljup.SeleniumJupiter.isSingleSession(737) -- Single session false
2022-03-24 18:42:46 [Test worker] TRACE i.g.b.seljup.CapabilitiesHandler.getOptionsClass(104) -- Getting capabilities for type=interface org.openqa.selenium.WebDriver -- browserType=Optional[CHROME]
2022-03-24 18:42:46 [Test worker] TRACE i.g.b.seljup.CapabilitiesHandler.getOptions(147) -- Getting options for class org.openqa.selenium.chrome.ChromeOptions
2022-03-24 18:42:46 [Test worker] TRACE i.g.b.seljup.CapabilitiesHandler.handlePreferences(247) -- Exception reading preferences of class org.openqa.selenium.chrome.ChromeOptions (org.openqa.selenium.chrome.ChromeOptions.addPreference(java.lang.String,java.lang.Object))
2022-03-24 18:42:46 [Test worker] TRACE i.g.b.seljup.CapabilitiesHandler.getOptions(167) -- Gathered Capabilities {browserName: chrome, goog:chromeOptions: {args: [], extensions: []}}
2022-03-24 18:42:46 [Test worker] TRACE i.g.bonigarcia.seljup.OutputHandler.getOutputFolder(113) -- Output folder .
2022-03-24 18:42:46 [Test worker] TRACE i.g.b.seljup.SeleniumJupiter.putManagerInMap(718) -- Put manager io.github.bonigarcia.wdm.managers.ChromeDriverManager@421bba99 in map (context id [engine:junit-jupiter]/[class:tests.DockerBrowserTest])
2022-03-24 18:42:46 [Test worker] TRACE i.g.b.seljup.SeleniumJupiter.putManagerInMap(726) -- Adding io.github.bonigarcia.wdm.managers.ChromeDriverManager@421bba99 to new map (id [engine:junit-jupiter]/[class:tests.DockerBrowserTest])
2022-03-24 18:42:47 [Test worker] DEBUG i.g.b.wdm.cache.ResolutionCache.checkValidity(156) -- Removing resolution chrome-container-latest=99.0 from cache (expired on Thu Mar 24 11:45:09 AMT 2022)
2022-03-24 18:42:47 [Test worker] DEBUG i.g.b.wdm.docker.DockerHubService.listTags(60) -- Getting browser image list from Docker Hub
2022-03-24 18:42:47 [Test worker] TRACE i.g.b.wdm.docker.DockerHubService.listTags(73) -- Sending request to https://hub.docker.com/v2/repositories/selenoid/vnc/tags?page=1&page_size=1024
2022-03-24 18:42:47 [Test worker] TRACE i.g.b.wdm.docker.DockerHubService.listTags(73) -- Sending request to https://hub.docker.com/v2/repositories/selenoid/vnc/tags?page=2&page_size=1024
2022-03-24 18:42:48 [Test worker] DEBUG i.g.b.wdm.docker.DockerService.getImageVersionFromDockerHub(440) -- The latest version of Chrome in Docker Hub is 99.0
2022-03-24 18:42:48 [Test worker] TRACE i.g.b.wdm.docker.DockerService.getDockerImage(486) -- Docker image: selenoid/vnc:chrome_99.0
2022-03-24 18:42:48 [Test worker] INFO  i.g.b.wdm.docker.DockerService.pullImageIfNecessary(299) -- Pulling Docker image selenoid/vnc:chrome_99.0 (this might take some time, but only the first time)
2022-03-24 18:42:50 [Test worker] TRACE i.g.b.wdm.docker.DockerService.pullImageIfNecessary(305) -- Docker image selenoid/vnc:chrome_99.0 pulled
2022-03-24 18:42:50 [Test worker] DEBUG i.g.b.wdm.cache.ResolutionCache.putValueInResolutionCacheIfEmpty(119) -- Storing resolution chrome-container-latest=99.0 in cache (valid until 19:42:50 24/03/2022 AMT)
2022-03-24 18:42:50 [Test worker] TRACE i.g.bonigarcia.wdm.config.Config.getDockerMemSizeBytes(1115) -- The memory size 256m is equivalent to 268435456 bytes)
2022-03-24 18:42:50 [Test worker] TRACE i.g.bonigarcia.wdm.config.Config.getDockerMemSizeBytes(1115) -- The memory size 128m is equivalent to 134217728 bytes)
2022-03-24 18:42:50 [Test worker] INFO  i.g.b.wdm.docker.DockerService.startContainer(173) -- Starting Docker container selenoid/vnc:chrome_99.0
2022-03-24 18:42:50 [Test worker] TRACE i.g.b.wdm.docker.DockerService.startContainer(186) -- Adding sysadmin capability
2022-03-24 18:42:50 [Test worker] TRACE i.g.b.wdm.docker.DockerService.startContainer(192) -- Using shm size: 268435456
2022-03-24 18:42:50 [Test worker] TRACE i.g.b.wdm.docker.DockerService.startContainer(198) -- Using network: bridge
2022-03-24 18:42:50 [Test worker] TRACE i.g.b.wdm.docker.DockerService.startContainer(203) -- Using exposed ports: [4444, 5900]
2022-03-24 18:42:50 [Test worker] TRACE i.g.b.wdm.docker.DockerService.startContainer(210) -- Using binds: []
2022-03-24 18:42:50 [Test worker] TRACE i.g.b.wdm.docker.DockerService.startContainer(216) -- Using mounts: [Mount(type=TMPFS, source=null, target=/tmp, readOnly=null, bindOptions=null, volumeOptions=null, tmpfsOptions=TmpfsOptions(sizeBytes=134217728, mode=null))]
2022-03-24 18:42:50 [Test worker] TRACE i.g.b.wdm.docker.DockerService.startContainer(222) -- Using envs: [TZ=Etc/UTC, LANG=EN, SCREEN_RESOLUTION=1280x1080x24, ENABLE_VNC=true, DRIVER_ARGS=--whitelisted-ips= --allowed-origins=*]
2022-03-24 18:42:51 [Test worker] TRACE i.g.b.wdm.docker.DockerService.getBindPort(283) -- Port list {4444/tcp=[Lcom.github.dockerjava.api.model.Ports$Binding;@71978f46, 5900/tcp=[Lcom.github.dockerjava.api.model.Ports$Binding;@304d0259} -- Exposed port 4444/tcp = [0.0.0.0:55076]
2022-03-24 18:42:51 [Test worker] TRACE i.g.b.wdm.docker.DockerService.startBrowserContainer(660) -- Browser remote URL http://localhost:55076/
2022-03-24 18:42:51 [Test worker] TRACE i.g.b.wdm.docker.DockerService.getBindPort(283) -- Port list {4444/tcp=[Lcom.github.dockerjava.api.model.Ports$Binding;@1d23ff23, 5900/tcp=[Lcom.github.dockerjava.api.model.Ports$Binding;@2133661d} -- Exposed port 5900/tcp = [0.0.0.0:55075]
2022-03-24 18:42:51 [Test worker] DEBUG i.g.b.wdm.docker.DockerService.startBrowserContainer(667) -- VNC server URL: vnc://localhost:55075/
2022-03-24 18:42:51 [Test worker] TRACE i.g.bonigarcia.wdm.WebDriverManager.createDockerWebDriver(1656) -- The Selenium Serverl URL is http://localhost:55076/
2022-03-24 18:42:51 [Test worker] DEBUG i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(77) -- Creating WebDriver object for chrome at http://localhost:55076/ with Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu], extensions: []}}
2022-03-24 18:42:51 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(92) -- SocketException creating WebDriver object (Unexpected end of file from server)
2022-03-24 18:42:52 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(92) -- SocketException creating WebDriver object (Unexpected end of file from server)
2022-03-24 18:42:53 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(86) -- Requesting http://localhost:55076/ (the response code is 404)
Mar 24, 2022 6:42:53 PM org.openqa.selenium.remote.tracing.opentelemetry.OpenTelemetryTracer createTracer
INFO: Using OpenTelemetry for tracing
2022-03-24 18:42:55 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(92) -- SessionNotCreatedException creating WebDriver object (Could not start a new session. Response code 500. Message: unknown error: Chrome failed to start: crashed.
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '4.1.2', revision: '9a5a329c5a'
System info: host: 'Davits-MacBook-Pro.local', ip: 'fe80:0:0:0:18ce:380f:e288:859%en0', os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '12.3', java.version: '17.0.2'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Command: [null, newSession {capabilities=[Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu], extensions: []}}], desiredCapabilities=Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu], extensions: []}}}]
Capabilities {})
2022-03-24 18:42:56 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(86) -- Requesting http://localhost:55076/ (the response code is 404)
2022-03-24 18:42:57 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(92) -- SessionNotCreatedException creating WebDriver object (Could not start a new session. Response code 500. Message: unknown error: Chrome failed to start: crashed.
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '4.1.2', revision: '9a5a329c5a'
System info: host: 'Davits-MacBook-Pro.local', ip: 'fe80:0:0:0:18ce:380f:e288:859%en0', os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '12.3', java.version: '17.0.2'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Command: [null, newSession {capabilities=[Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu], extensions: []}}], desiredCapabilities=Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu], extensions: []}}}]
Capabilities {})
2022-03-24 18:42:59 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(86) -- Requesting http://localhost:55076/ (the response code is 404)
2022-03-24 18:43:00 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(92) -- SessionNotCreatedException creating WebDriver object (Could not start a new session. Response code 500. Message: unknown error: Chrome failed to start: crashed.
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '4.1.2', revision: '9a5a329c5a'
System info: host: 'Davits-MacBook-Pro.local', ip: 'fe80:0:0:0:18ce:380f:e288:859%en0', os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '12.3', java.version: '17.0.2'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Command: [null, newSession {capabilities=[Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu], extensions: []}}], desiredCapabilities=Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu], extensions: []}}}]
Capabilities {})
2022-03-24 18:43:01 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(86) -- Requesting http://localhost:55076/ (the response code is 404)
2022-03-24 18:43:03 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(92) -- SessionNotCreatedException creating WebDriver object (Could not start a new session. Response code 500. Message: unknown error: Chrome failed to start: crashed.
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '4.1.2', revision: '9a5a329c5a'
System info: host: 'Davits-MacBook-Pro.local', ip: 'fe80:0:0:0:18ce:380f:e288:859%en0', os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '12.3', java.version: '17.0.2'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Command: [null, newSession {capabilities=[Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu], extensions: []}}], desiredCapabilities=Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu], extensions: []}}}]
Capabilities {})

And so on ... the mentioned part in logs is repetitive.

[bonigarcia]

As I temporary fix, you can try to include this logic in your test class:

    static {
        System.setProperty("wdm.dockerDefaultArgs", "--disable-gpu,--no-sandbox");
    }

If this works, I put it in the next release of Selenium-Jupiter. Please let me know the result.

[David91]

Included in the test class.

Same result.

2022-03-25 14:23:56 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(86) -- Requesting http://localhost:55109/ (the response code is 404)
2022-03-25 14:23:58 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(92) -- SessionNotCreatedException creating WebDriver object (Could not start a new session. Response code 500. Message: unknown error: Chrome failed to start: crashed.
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '4.1.2', revision: '9a5a329c5a'
System info: host: 'Davits-MacBook-Pro.local', ip: 'fe80:0:0:0:18ce:380f:e288:859%en0', os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '12.3', java.version: '17.0.2'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Command: [null, newSession {capabilities=[Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu, --no-sandbox], extensions: []}}], desiredCapabilities=Capabilities {browserName: chrome, goog:chromeOptions: {args: [--disable-gpu, --no-sandbox], extensions: []}}}]
Capabilities {})
2022-03-25 14:23:59 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(86) -- Requesting http://localhost:55109/ (the response code is 404)
2022-03-25 14:24:01 [Test worker] TRACE i.g.b.wdm.webdriver.WebDriverCreator.createRemoteWebDriver(92) -- SessionNotCreatedException creating WebDriver object (Could not start a new session. Response code 500. Message: unknown error: Chrome failed to start: crashed.

Please let me know if they are more possible options for bypassing the problem. I'll try them all :)

[bonigarcia]

Please try this (I read the order of parameter might be important):

    static {
        System.setProperty("wdm.dockerDefaultArgs", "--no-sandbox,--disable-gpu");
    }

If this does not work, please try this:

    static {
        System.setProperty("wdm.dockerDefaultArgs", "--no-sandbox,--disable-gpu");
        System.setProperty("wdm.dockerShmSize", "512m");
    }

Please let me know the result.

[David91]

Hi. I think I have gotten new updates.
It's regarding your comment, where you suggested me to run the command
docker run --rm --cap-add=SYS_ADMIN -p 4444:4444 -p 5900:5900 -e ENABLE_VNC=true selenoid/vnc:chrome_99.0

It shows this message after redirecting to localhost:4444/status

But after the removal of /status part from URL, again the same error message appears as it appeared after running the test and redirecting by the browser remote URL

So it's most probably not a Selenium-Jupiter related issue.
Your suggested options didn't help :/

[bonigarcia]

I don't know, maybe you can try with even more shared memory:

docker run --rm --shm-size=2g --cap-add=SYS_ADMIN -p 4444:4444 -p 5900:5900 -e ENABLE_VNC=true selenoid/vnc:chrome_99.0

... or in your test:

    static {
        System.setProperty("wdm.dockerShmSize", "2g");
    }

[David91]

Again no success :/
I think the problem may be related to this:
SeleniumHQ/docker-selenium#1076

[bonigarcia]

More precisely, it is related to:

aerokube/images#524

[MariaSportChef]

More precisely, it is related to:

aerokube/images#524

Seems that's already ready :) I'd like to kindly ask if it's possible to fix Selenium's images? thanks a lot ;)