Docker - Selenium gid

0

Witam
Mam problem z spięciem w selenium grid hub z kontenerem firefox. Cały czas kontener firefox informuje że nie może połączyć się z hub. Wszzedłem do środka kontenera i pingnołem adres na jaki łączy się firefix i normalnie leciał ping. Proszę o pomoc w rozwiązaniu problemu.

logi z HUB:

021-12-02 11:34:58,642 INFO Included extra file "/etc/supervisor/conf.d/selenium-grid-hub.conf" during parsing
2021-12-02 11:34:58,643 INFO supervisord started with pid 8
2021-12-02 11:34:59,649 INFO spawned: 'selenium-grid-hub' with pid 10
11:34:59.875 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
2021-12-02 11:34:59,877 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
11:34:59.878 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
11:34:59.928 INFO [BoundZmqEventBus.<init>] - XPUB binding to [binding to tcp://*:4442, advertising as tcp://172.18.0.2:4442], XSUB binding to [binding to tcp://*:4443, advertising as tcp://172.18.0.2:4443]
11:34:59.959 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://172.18.0.2:4442 and tcp://172.18.0.2:4443
11:34:59.971 INFO [UnboundZmqEventBus.<init>] - Sockets created
11:35:00.977 INFO [UnboundZmqEventBus.<init>] - Event bus ready
11:35:01.360 INFO [Hub.execute] - Started Selenium Hub 4.1.0 (revision 87802e897b): http://172.18.0.2:4444

log z Firefox:

2021-12-02 11:34:58,684 INFO Included extra file "/etc/supervisor/conf.d/selenium-debug.conf" during parsing
2021-12-02 11:34:58,684 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
2021-12-02 11:34:58,685 INFO supervisord started with pid 9
2021-12-02 11:34:59,687 INFO spawned: 'xvfb' with pid 11
2021-12-02 11:34:59,689 INFO spawned: 'fluxbox' with pid 12
2021-12-02 11:34:59,690 INFO spawned: 'vnc' with pid 13
2021-12-02 11:34:59,691 INFO spawned: 'selenium-node' with pid 14
2021-12-02 11:34:59,727 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-12-02 11:34:59,727 INFO success: fluxbox entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-12-02 11:34:59,727 INFO success: vnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-12-02 11:34:59,727 INFO success: selenium-node entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
Connecting to the Hub using the host hub and port 4444
11:35:00.183 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, revision: e82be7d358
11:35:00.236 INFO [GridLauncherV3.lambda$buildLaunchers$7] - Launching a Selenium Grid node on port 5555
2021-12-02 11:35:00.280:INFO::main: Logging initialized @209ms to org.seleniumhq.jetty9.util.log.StdErrLog
11:35:00.388 INFO [WebDriverServlet.<init>] - Initialising WebDriverServlet
11:35:00.430 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 5555
11:35:00.431 INFO [GridLauncherV3.lambda$buildLaunchers$7] - Selenium Grid node is up and ready to register to the hub
11:35:00.450 INFO [SelfRegisteringRemote$1.run] - Starting auto registration thread. Will try to register every 5000 ms.
11:35:00.559 WARN [SelfRegisteringRemote.registerToHub] - Error getting the parameters from the hub. The node may end up with wrong timeouts.Failed to connect to hub/172.18.0.2:4444
11:35:00.559 INFO [SelfRegisteringRemote.registerToHub] - Registering the node to the hub: http://hub:4444/grid/register
11:35:00.566 INFO [SelfRegisteringRemote$1.run] - Couldn't register this node: Error sending the registration request: Failed to connect to hub/172.18.0.2:4444
11:35:05.637 INFO [SelfRegisteringRemote$1.run] - Couldn't register this node: The hub is down or not responding: The hub responded with 404
11:35:10.647 INFO [SelfRegisteringRemote$1.run] - Couldn't register this node: The hub is down or not responding: The hub responded with 404

docker-compose.yml:

  hub:
    image: selenium/hub
    container_name: hub
    ports:
      - 4444:4444

  firefox:
    image: selenium/node-firefox-debug
    container_name: firefox
    ports:
      - 32775:5900
    environment:
      - HUB_HOST=hub
      - HUB_PORT=4444

  chrome:
    image: selenium/node-chrome-debug
    container_name: selenium-chrome
    ports:
      - 32776:5900
    environment:
      - HUB_HOST=hub
      - HUB_PORT=4444

Gdzie popełniam błąd ??

1 użytkowników online, w tym zalogowanych: 0, gości: 1