[🐛 Bug]:Use dynamic grid error

[Gongcong]

What happened?

use dynamic grid error ，i use nodedocker to create a node that build only for webdriver

my config :
`services:
#==================

Selenium Hub

#==================
selenium-hub:
image: selenium/hub:latest
container_name: selenium-hub
ports:
- "4442:4442"
- "4443:4443"
- "4444:4444"
environment:
# - SE_LOG_LEVEL=DEBUG
- SE_NODE_SESSION_TIMEOUT=100
- SE_SESSION_REQUEST_TIMEOUT=30
- SE_ENABLE_TRACING=true
- SE_LOG_LEVEL=DEBUG
# volumes:
# # 挂载Hub配置文件
# - ./config/grid-config.toml:/opt/selenium/config.toml:ro
networks:
- selenium-grid

#==================

Node-Docker (直接使用宿主机Docker)

#==================
node-docker:
image: selenium/node-docker:latest
container_name: selenium-node-docker
environment:
- SE_EVENT_BUS_HOST=selenium-hub
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
- SE_NODE_DOCKER_CONFIG_FILENAME=docker.toml
# - SE_ENABLE_TRACING=true
# - SE_LOG_LEVEL=DEBUG
volumes:
- ./assets:/opt/selenium/assets
- /var/run/docker.sock:/var/run/docker.sock
- ./config/node-docker-config.toml:/opt/selenium/docker.toml
privileged: true
depends_on:
- selenium-hub
networks:
- selenium-grid

#==================

Portainer (可选 - Docker管理界面)

#==================
portainer:
image: portainer/portainer-ce:latest
container_name: portainer
ports:
- "9000:9000"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- portainer-data:/data
networks:
- selenium-grid
restart: unless-stopped

#==================

网络配置

#==================
networks:
selenium-grid:
driver: bridge

#==================

数据卷

#==================
volumes:
portainer-data: `

Command used to start Selenium Grid with Docker (or Kubernetes)

this is my chromedirver file :
FROM selenium/node-base:4.33.0-20250606

USER root

#==================
# 安装基础依赖包
#------------------
# ca-certificates - SSL 客户端
# curl - 数据传输工具
# wget - 网络下载工具
# unzip - 解压工具
# adb - Android Debug Bridge
# xvfb - X virtual framebuffer
# fonts-liberation - 字体库
#==================
RUN apt-get update && apt-get install -y \
    ca-certificates \
    curl \
    wget \
    unzip \
    android-tools-adb \
    xvfb \
    fonts-liberation \
    && apt-get clean \
    && rm -rf /var/lib/apt/lists/*

#==================
# 注意：此节点仅安装 ChromeDriver，不安装 Chrome 浏览器
# 主要用于 Android WebView 和远程 Chrome 实例的自动化测试
#==================

#==================
# 使用本地 ChromeDriver 文件
#==================
ENV CHROMEDRIVER_VERSION=128.0.6613.0
RUN mkdir -p /opt/chromedriver
COPY node/chromedriver-128/chromedriver /opt/chromedriver/chromedriver
RUN chmod +x /opt/chromedriver/chromedriver

#==================
# 设置环境变量
#==================
ENV PATH="/opt/chromedriver:${PATH}"
ENV DISPLAY=:99
ENV CHROMEDRIVER_BIN=/opt/chromedriver/chromedriver

#==================
# 创建必要的目录和权限
#==================
RUN mkdir -p /tmp/.X11-unix \
    && chmod 1777 /tmp/.X11-unix \
    && mkdir -p /home/seluser/.android \
    && chown -R seluser:seluser /home/seluser/.android

#==================
# 复制配置文件
#==================
COPY node/node_config/chromedriver-node.toml /opt/selenium/chromedriver-node.toml

#==================
# 切换到 selenium 用户
#==================
USER seluser

#==================
# 设置工作目录
#==================
WORKDIR /home/seluser

#==================
# 健康检查
#==================
HEALTHCHECK --interval=15s --timeout=30s --start-period=5s --retries=3 \
    CMD curl -sSL http://localhost:5555/status || exit 1

#==================
# 启动脚本
#==================
COPY node/chromedriver-entrypoint.sh /opt/bin/chromedriver-entrypoint.sh
USER root
RUN chmod +x /opt/bin/chromedriver-entrypoint.sh
USER seluser

ENTRYPOINT ["/opt/bin/chromedriver-entrypoint.sh"]

Relevant log output

`2025-07-11 21:00:05.636 | ERROR    | __main__:connect_remote:507 - RemoteWebDriver 创建失败: Message: Could not start a new session. New session request timed out
Build info: version: '4.1.1', revision: 'e8fcc2cecf'
System info: host: '2d098ea37739', ip: '172.18.0.2', os.name: 'Linux', os.arch: 'amd64', os.version: '5.15.0-140-generic', java.version: '11.0.13'
Driver info: driver.version: unknown
Stacktrace:
    at org.openqa.selenium.grid.sessionqueue.local.LocalNewSessionQueue.addToQueue (LocalNewSessionQueue.java:202)
    at org.openqa.selenium.grid.sessionqueue.NewSessionQueue.lambda$new$0 (NewSessionQueue.java:68)
    at org.openqa.selenium.remote.http.Route$TemplatizedRoute.handle (Route.java:192)
    at org.openqa.selenium.remote.http.Route.execute (Route.java:68)
    at org.openqa.selenium.remote.http.Route$CombinedRoute.handle (Route.java:336)
    at org.openqa.selenium.remote.http.Route.execute (Route.java:68)
    at org.openqa.selenium.grid.sessionqueue.NewSessionQueue.execute (NewSessionQueue.java:120)
    at org.openqa.selenium.remote.tracing.SpanWrappedHttpHandler.execute (SpanWrappedHttpHandler.java:86)
    at org.openqa.selenium.remote.http.Filter$1.execute (Filter.java:64)
    at org.openqa.selenium.remote.http.Route$CombinedRoute.handle (Route.java:336)
    at org.openqa.selenium.remote.http.Route.execute (Route.java:68)
    at org.openqa.selenium.grid.router.Router.execute (Router.java:91)
    at org.openqa.selenium.grid.web.EnsureSpecCompliantResponseHeaders.lambda$apply$0 (EnsureSpecCompliantResponseHeaders.java:34)
    at org.openqa.selenium.remote.http.Filter$1.execute (Filter.java:64)
    at org.openqa.selenium.remote.http.Route$CombinedRoute.handle (Route.java:336)
    at org.openqa.selenium.remote.http.Route.execute (Route.java:68)
    at org.openqa.selenium.remote.http.Route$NestedRoute.handle (Route.java:270)
    at org.openqa.selenium.remote.http.Route.execute (Route.java:68)
    at org.openqa.selenium.remote.http.Route$CombinedRoute.handle (Route.java:336)
    at org.openqa.selenium.remote.http.Route.execute (Route.java:68)
    at org.openqa.selenium.remote.http.Route$CombinedRoute.handle (Route.java:336)
    at org.openqa.selenium.remote.http.Route.execute (Route.java:68)
    at org.openqa.selenium.remote.AddWebDriverSpecHeaders.lambda$apply$0 (AddWebDriverSpecHeaders.java:35)
    at org.openqa.selenium.remote.ErrorFilter.lambda$apply$0 (ErrorFilter.java:44)
    at org.openqa.selenium.remote.http.Filter$1.execute (Filter.java:64)
    at org.openqa.selenium.remote.ErrorFilter.lambda$apply$0 (ErrorFilter.java:44)
    at org.openqa.selenium.remote.http.Filter$1.execute (Filter.java:64)
    at org.openqa.selenium.netty.server.SeleniumHandler.lambda$channelRead0$0 (SeleniumHandler.java:44)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)
    at java.util.concurrent.FutureTask.run (FutureTask.java:264)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)
    at java.lang.Thread.run (Thread.java:829)`

Operating System

linux

Docker Selenium version (image tag)

4.33.0-20250606

Selenium Grid chart version (chart version)

4.33.0-20250606

[github-actions]

@Gongcong, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

- SE_SESSION_REQUEST_TIMEOUT=30 this means queue request just alive within 30 seconds, otherwise it will fail
In this case, Node start up just fast when all node images are pre-pulled on host. If a new host, pull image took time, it also fail.
Can you also share code snippet that you start RemoteWebDriver? Is there capability set that mismatch for slot matching? for example, enable downloads manage but Node config didn't enable it.

[Gongcong]

- SE_SESSION_REQUEST_TIMEOUT=30 this means queue request just alive within 30 seconds, otherwise it will fail In this case, Node start up just fast when all node images are pre-pulled on host. If a new host, pull image took time, it also fail. Can you also share code snippet that you start RemoteWebDriver? Is there capability set that mismatch for slot matching? for example, enable downloads manage but Node config didn't enable it.

hi，this is my connect code :
`serial_id = "172.16.1.128:6570"
logger.info(f"开始创建 WebDriver serial_id={serial_id}")
options = ChromeOptions()

# # WebView专用配置
options.enable_mobile(
    android_package="mark.via",
    device_serial=serial_id,
    android_activity="mark.via.Shell"
)

 添加WebView专用选项
options.add_experimental_option("androidUseRunningApp", True)
# options.add_experimental_option('androidDeviceSerial', serial_id)
options.add_experimental_option("androidProcess", "mark.via")
options.set_capability("browserVersion", "128.0.6613.81")
options.set_capability("platformName", "android")
 options.set_capability("se:serial_id", serial_id)

logger.info(f"Chrome 选项配置: {options.to_capabilities()}")

 连接到WebView节点
remote_url = "http://localhost:4444/wd/hub"
if not remote_url:
    raise ValueError("REMOTE_WEBDRIVER_URL 未配置")

logger.info(f"使用 RemoteWebDriver: {remote_url}")`

i set timeout = 300 ,also has same error. i create a node only has chromedriver that extend node-base, Is it a problem with my own node configuration?
this it docker file :
`FROM selenium/node-chrome:4.33.0-20250606

USER root

RUN apt-get update && apt-get install -y
ca-certificates
curl
wget
unzip
android-tools-adb
xvfb
fonts-liberation
&& apt-get clean
&& rm -rf /var/lib/apt/lists/*

ENV CHROMEDRIVER_VERSION=128.0.6613.0
RUN mkdir -p /opt/chromedriver
COPY node/chromedriver-128/chromedriver /opt/chromedriver/chromedriver
RUN chmod +x /opt/chromedriver/chromedriver

ENV PATH="/opt/chromedriver:${PATH}"
ENV DISPLAY=:99
ENV CHROMEDRIVER_BIN=/opt/chromedriver/chromedriver

RUN mkdir -p /tmp/.X11-unix
&& chmod 1777 /tmp/.X11-unix
&& mkdir -p /home/seluser/.android
&& chown -R seluser:seluser /home/seluser/.android

COPY node/node_config/chromedriver-node.toml /opt/selenium/chromedriver-node.toml

USER seluser

WORKDIR /home/seluser

HEALTHCHECK --interval=15s --timeout=30s --start-period=5s --retries=3
CMD curl -sSL http://localhost:5555/status || exit 1

COPY node/chromedriver-entrypoint.sh /opt/bin/chromedriver-entrypoint.sh
USER root
RUN chmod +x /opt/bin/chromedriver-entrypoint.sh
USER seluser

ENTRYPOINT ["/opt/bin/chromedriver-entrypoint.sh"] `

this is chromedriver-entrypoint.sh:

`!/bin/bash

set -e

export NODE_CONFIG_PATH=${NODE_CONFIG_PATH:-"/opt/selenium/chromedriver-node.toml"}
export SELENIUM_HUB_HOST=${SELENIUM_HUB_HOST:-"selenium-hub"}
export SELENIUM_HUB_PORT=${SELENIUM_HUB_PORT:-"4444"}
export NODE_PORT=${NODE_PORT:-"5555"}
export MAX_SESSIONS=${MAX_SESSIONS:-"3"}
export ENABLE_ADB=${ENABLE_ADB:-"true"}

log() {
echo "[$(date '+%Y-%m-%d %H:%M:%S')] ChromeDriver-Node: $1"
}

log "ChromeDriver Node 启动中..."

if [ ! -x "/opt/chromedriver/chromedriver" ]; then
log "错误: ChromeDriver 不存在或不可执行"
exit 1
fi

CHROMEDRIVER_VER=$(/opt/chromedriver/chromedriver --version 2>/dev/null || echo "unknown")
log "ChromeDriver 版本: $CHROMEDRIVER_VER"

log "ENABLE_ADB: $ENABLE_ADB"

if [ ! -f "$NODE_CONFIG_PATH" ]; then
log "错误: 节点配置文件不存在: $NODE_CONFIG_PATH"
exit 1
fi

log "使用配置文件: $NODE_CONFIG_PATH"

exec java -jar /opt/selenium/selenium-server.jar node
--config "$NODE_CONFIG_PATH"
--publish-events "tcp://selenium-hub:4442"
--subscribe-events "tcp://selenium-hub:4443"
--bind-bus false`

[Gongcong]

Dockerfile.chromedriver-node.txt

chromedriver-node.toml.txt

build-chromedriver-node.sh.txt

[Gongcong]

this is my docker connect log :

selenium-hub | 03:19:37.457 INFO [LocalDistributor.newSession] - Session request received by the distributor: selenium-hub | [Capabilities {browserName: chrome, browserVersion: 128.0.6613.0, goog:chromeOptions: {androidActivity: mark.via.Shell, androidDeviceSerial: 172.16.1.128:6570, androidPackage: mark.via, androidProcess: mark.via, androidUseRunningApp: true, args: [], extensions: []}, pageLoadStrategy: normal, platformName: android}] selenium-node-docker | 03:19:37.480 INFO [DockerSessionFactory.apply] - Starting session for Capabilities {browserName: chrome, browserVersion: 128.0.6613.0, goog:chromeOptions: {androidActivity: mark.via.Shell, androidDeviceSerial: 172.16.1.128:6570, androidPackage: mark.via, androidProcess: mark.via, androidUseRunningApp: true, args: [], extensions: []}, pageLoadStrategy: normal, platformName: ANDROID} selenium-node-docker | 03:19:37.481 INFO [DockerSessionFactory.apply] - Creating container... selenium-node-docker | 03:19:37.491 INFO [V141Docker.getImage] - Listing local images: Reference{domain='docker.io', name='library/selenium-chrome-node-128', tag='latest', digest='null', platform='linux/amd64} selenium-node-docker | 03:19:37.557 INFO [Container.<init>] - Created container 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a selenium-node-docker | 03:19:37.557 INFO [Container.start] - Starting container 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a selenium-node-docker | 03:19:37.662 INFO [Container.inspect] - Inspecting container 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a selenium-node-docker | 03:19:37.710 INFO [DockerSessionFactory.apply] - Waiting for server to start (container id: 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a, url http://172.18.0.5:4444/wd/hub) selenium-node-docker | 03:19:48.221 INFO [Container.stop] - Stopping container 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a selenium-node-docker | 03:19:48.224 WARN [DockerMessages.throwIfNecessary] - Unable to stop container: 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a selenium-node-docker | No such container: 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a selenium-node-docker | 03:19:48.224 WARN [Container.stop] - Unable to stop container: Unable to stop container: 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a selenium-node-docker | No such container: 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a selenium-node-docker | org.openqa.selenium.docker.DockerException: Unable to stop container: 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a selenium-node-docker | No such container: 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a selenium-node-docker | at org.openqa.selenium.docker.v1_41.DockerMessages.throwIfNecessary(DockerMessages.java:59) selenium-node-docker | at org.openqa.selenium.docker.v1_41.StopContainer.apply(StopContainer.java:49) selenium-node-docker | at org.openqa.selenium.docker.v1_41.V141Docker.stopContainer(V141Docker.java:125) selenium-node-docker | at org.openqa.selenium.docker.Container.stop(Container.java:56) selenium-node-docker | at org.openqa.selenium.grid.node.docker.DockerSessionFactory.apply(DockerSessionFactory.java:198) selenium-node-docker | at org.openqa.selenium.grid.node.docker.DockerSessionFactory.apply(DockerSessionFactory.java:87) selenium-node-docker | at org.openqa.selenium.grid.node.local.SessionSlot.apply(SessionSlot.java:151) selenium-node-docker | at org.openqa.selenium.grid.node.local.LocalNode.newSession(LocalNode.java:521) selenium-node-docker | at org.openqa.selenium.grid.node.NewNodeSession.execute(NewNodeSession.java:50) selenium-hub | 03:19:48.233 INFO [LocalDistributor$NewSessionRunnable.handleNewSessionRequest] - Retrying selenium-node-docker | at org.openqa.selenium.remote.http.Route$TemplatizedRoute.handle(Route.java:192) selenium-node-docker | at org.openqa.selenium.remote.http.Route.execute(Route.java:69) selenium-node-docker | at org.openqa.selenium.grid.security.RequiresSecretFilter.lambda$apply$0(RequiresSecretFilter.java:62) selenium-node-docker | at org.openqa.selenium.remote.tracing.SpanWrappedHttpHandler.execute(SpanWrappedHttpHandler.java:87) selenium-node-docker | at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63) selenium-node-docker | at org.openqa.selenium.remote.http.Route$CombinedRoute.handle(Route.java:361) selenium-node-docker | at org.openqa.selenium.remote.http.Route.execute(Route.java:69) selenium-node-docker | at org.openqa.selenium.grid.node.Node.execute(Node.java:296) selenium-node-docker | at org.openqa.selenium.remote.http.Route$CombinedRoute.handle(Route.java:361) selenium-node-docker | at org.openqa.selenium.remote.http.Route.execute(Route.java:69) selenium-node-docker | at org.openqa.selenium.remote.AddWebDriverSpecHeaders.lambda$apply$0(AddWebDriverSpecHeaders.java:35) selenium-node-docker | at org.openqa.selenium.remote.ErrorFilter.lambda$apply$0(ErrorFilter.java:44) selenium-node-docker | at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63) selenium-node-docker | at org.openqa.selenium.remote.ErrorFilter.lambda$apply$0(ErrorFilter.java:44) selenium-node-docker | at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63) selenium-node-docker | at org.openqa.selenium.netty.server.SeleniumHandler.lambda$channelRead0$0(SeleniumHandler.java:49) selenium-node-docker | at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) selenium-node-docker | at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) selenium-node-docker | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) selenium-node-docker | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) selenium-node-docker | at java.base/java.lang.Thread.run(Thread.java:1583) selenium-node-docker | 03:19:48.225 WARN [DockerSessionFactory.apply] - Unable to connect to docker server (container id: 798746f1615f58f51e462401d9324bae47698923296abc06a4e743c869c64d2a) selenium-hub | 03:19:52.456 INFO [LocalDistributor.newSession] - Session request received by the distributor: selenium-hub | [Capabilities {browserName: chrome, browserVersion: 128.0.6613.0, goog:chromeOptions: {androidActivity: mark.via.Shell, androidDeviceSerial: 172.16.1.128:6570, androidPackage: mark.via, androidProcess: mark.via, androidUseRunningApp: true, args: [], extensions: []}, pageLoadStrategy: normal, platformName: android}] selenium-node-docker | 03:19:52.462 INFO [DockerSessionFactory.apply] - Starting session for Capabilities {browserName: chrome, browserVersion: 128.0.6613.0, goog:chromeOptions: {androidActivity: mark.via.Shell, androidDeviceSerial: 172.16.1.128:6570, androidPackage: mark.via, androidProcess: mark.via, androidUseRunningApp: true, args: [], extensions: []}, pageLoadStrategy: normal, platformName: ANDROID} selenium-node-docker | 03:19:52.462 INFO [DockerSessionFactory.apply] - Creating container... selenium-node-docker | 03:19:52.464 INFO [V141Docker.getImage] - Listing local images: Reference{domain='docker.io', name='library/selenium-chrome-node-128', tag='latest', digest='null', platform='linux/amd64} selenium-node-docker | 03:19:52.516 INFO [Container.<init>] - Created container 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258 selenium-node-docker | 03:19:52.516 INFO [Container.start] - Starting container 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258 selenium-node-docker | 03:19:52.618 INFO [Container.inspect] - Inspecting container 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258 selenium-node-docker | 03:19:52.666 INFO [DockerSessionFactory.apply] - Waiting for server to start (container id: 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258, url http://172.18.0.5:4444/wd/hub) selenium-node-docker | 03:20:03.172 INFO [Container.stop] - Stopping container 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258 selenium-node-docker | 03:20:03.174 WARN [DockerMessages.throwIfNecessary] - Unable to stop container: 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258 selenium-node-docker | No such container: 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258 selenium-node-docker | 03:20:03.174 WARN [Container.stop] - Unable to stop container: Unable to stop container: 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258 selenium-node-docker | No such container: 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258 selenium-node-docker | org.openqa.selenium.docker.DockerException: Unable to stop container: 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258 selenium-node-docker | No such container: 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258 selenium-node-docker | at org.openqa.selenium.docker.v1_41.DockerMessages.throwIfNecessary(DockerMessages.java:59) selenium-node-docker | at org.openqa.selenium.docker.v1_41.StopContainer.apply(StopContainer.java:49) selenium-node-docker | at org.openqa.selenium.docker.v1_41.V141Docker.stopContainer(V141Docker.java:125) selenium-node-docker | at org.openqa.selenium.docker.Container.stop(Container.java:56) selenium-node-docker | at org.openqa.selenium.grid.node.docker.DockerSessionFactory.apply(DockerSessionFactory.java:198) selenium-node-docker | at org.openqa.selenium.grid.node.docker.DockerSessionFactory.apply(DockerSessionFactory.java:87) selenium-node-docker | at org.openqa.selenium.grid.node.local.SessionSlot.apply(SessionSlot.java:151) selenium-node-docker | at org.openqa.selenium.grid.node.local.LocalNode.newSession(LocalNode.java:521) selenium-node-docker | at org.openqa.selenium.grid.node.NewNodeSession.execute(NewNodeSession.java:50) selenium-node-docker | at org.openqa.selenium.remote.http.Route$TemplatizedRoute.handle(Route.java:192) selenium-node-docker | at org.openqa.selenium.remote.http.Route.execute(Route.java:69) selenium-node-docker | at org.openqa.selenium.grid.security.RequiresSecretFilter.lambda$apply$0(RequiresSecretFilter.java:62) selenium-node-docker | at org.openqa.selenium.remote.tracing.SpanWrappedHttpHandler.execute(SpanWrappedHttpHandler.java:87) selenium-node-docker | at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63) selenium-node-docker | at org.openqa.selenium.remote.http.Route$CombinedRoute.handle(Route.java:361) selenium-node-docker | at org.openqa.selenium.remote.http.Route.execute(Route.java:69) selenium-node-docker | at org.openqa.selenium.grid.node.Node.execute(Node.java:296) selenium-hub | 03:20:03.179 INFO [LocalDistributor$NewSessionRunnable.handleNewSessionRequest] - Retrying selenium-node-docker | at org.openqa.selenium.remote.http.Route$CombinedRoute.handle(Route.java:361) selenium-node-docker | at org.openqa.selenium.remote.http.Route.execute(Route.java:69) selenium-node-docker | at org.openqa.selenium.remote.AddWebDriverSpecHeaders.lambda$apply$0(AddWebDriverSpecHeaders.java:35) selenium-node-docker | at org.openqa.selenium.remote.ErrorFilter.lambda$apply$0(ErrorFilter.java:44) selenium-node-docker | at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63) selenium-node-docker | at org.openqa.selenium.remote.ErrorFilter.lambda$apply$0(ErrorFilter.java:44) selenium-node-docker | at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63) selenium-node-docker | at org.openqa.selenium.netty.server.SeleniumHandler.lambda$channelRead0$0(SeleniumHandler.java:49) selenium-node-docker | at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) selenium-node-docker | at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) selenium-node-docker | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) selenium-node-docker | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) selenium-node-docker | at java.base/java.lang.Thread.run(Thread.java:1583) selenium-node-docker | 03:20:03.174 WARN [DockerSessionFactory.apply] - Unable to connect to docker server (container id: 23053186ce10a7c8e9c5b0810822b85d606ce3c67dc192abcdc3e4354d38b258)