CreatePlatformSocket() returned an error, errno=97: Address family not supported by protocol (97)

[lumean...@gmail.com]

Hello,
we try to use chromedriver from java with headless chrome inside a docker container.

Whenever we start the chromedriver we get tons of errormessages as follows, sometimes there are only few messages and chromedriver starts, but sometimes those messages continue for 60 seconds and then chromedriver fails with the error below

Starting ChromeDriver 2.37.544315 (730aa6a5fdba159ac9f4c1e8cbc59bf1b5ce12b7) on port 15226
Only local connections are allowed.
[1522330168.207][SEVERE]: CreatePlatformSocket() returned an error, errno=97: Address family not supported by protocol (97)
[1522330168.260][SEVERE]: CreatePlatformSocket() returned an error, errno=97: Address family not supported by protocol (97)
[1522330168.312][SEVERE]: CreatePlatformSocket() returned an error, errno=97: Address family not supported by protocol (97)
...
...
...
...

org.openqa.selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally
(Driver info: chromedriver=2.37.544315 (730aa6a5fdba159ac9f4c1e8cbc59bf1b5ce12b7),platform=Linux 2.6.32-573.18.1.el6.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 60.08 seconds
Build info: version: '3.5.3', revision: 'a88d25fe6b', time: '2017-08-29T12:42:44.417Z'
System info: host: 'vega-regression-delphi', ip: '172.17.1.237', os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-573.18.1.el6.x86_64', java.version: '1.8.0_161'
Driver info: driver.version: ChromeDriver
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:215)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:167)
at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$new$0(JsonWireProtocolResponse.java:53)
at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$getResponseFunction$2(JsonWireProtocolResponse.java:91)
at org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$24(ProtocolHandshake.java:359)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126)
at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:362)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:136)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:142)
at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:82)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:646)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:255)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:237)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:138)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:178)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:167)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:156)

Anyone an idea about a possible reason?
Should I file a bug?

Many thanks

[salah.k...@gmail.com]

did you manage to fix this issue?
i am getting it now and i didn't have any solution yet

[John Chen]

Which version of ChromeDriver are you using, and how was the Docker image created? If possible, I'd recommend using Docker images created by Selenium to run Chrome and ChromeDriver, e.g., https://hub.docker.com/r/selenium/standalone-chrome/.

--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[lumean...@gmail.com]

In the end I think was related to this:
https://bugs.chromium.org/p/chromium/issues/detail?id=700347

Although we didn't confirm the root-cause 100%, I'm quite sure it was related to kernel as mentioned in the chromium issue. I'm not sure about IPv6, as we did actually disable IPv6 via chromedriver options, but still saw the issue.

As soon as we swapped the docker host OS to ubuntu 16.04 (kernel 4.X , instead of centos 7 - kernel 3.10) the issue was gone. We did not modify our docker image or the chromedriver options.