It can happen due to various issues, could be due to insufficient memory or hub and node versions are not correct, check configuration again if nodes are registered with the hub or not. Try to use docker compose with correct configuration to setup grid with latest hub and node images
since selenium 4 is now officially the new version docker, uses grid 4. so registering the node with the line from the video doesn't seem to connect. it keeps on loading and then gives error. can you look into it?
Hi @Karan , for selenium grid 4, configuring hub and node is somewhat different than what we did in the video of Selenium grid 3. Here we need to setup environment by setting up bus events, subscribe port and publish event port i.e. tcp port 4442 and port 4443. If u r using selenium/hub image 4th version then u will required to use 4th versions of the node images as well. Set==> SE_EVENT_BUS_PUBLISH_PORT , SE_EVENT_BUS_SUBSCRIBE_PORT , SE_EVENT_BUS_HOST while creating and registering the Node containers to the Hub Container. If you miss any one of the above environment setting then you won't be able to link nodes with Hub I am going to add a separate video in the same series soon...
Hello I found the "selenium/node-opera-debug" and "selenium/node-firefox-debug" and "selenium/node-chrome-debug" the Greated column in Docker shows "3 years ago". Is that ok?
Images might not be updated but that won't be issue u can still run the automation it will work fine. You can use selenium/node-chrome instead as both images are merged now
for me the chromenode is not able to connect the network ,I had done the same process as you shown it starting container of chrome but not connecting to the grid network
Hi, is there any way we can create a replica set so that the containers could scale as per the requirement? Example: My test cases are more and I want to launch more containers, can I do that?
Auto scaling of the containers not possible with docker compose... For now u can create multiple containers at the beginning only with docker compose scale cmd. Idle containers don't take memory or cpu utilisation will be normal.
Currently i am running trying to setup as shown in video but when running this command docker run -d -p 4446:5900 -net gridnetwork -e HUB_HOST=seleniumHub -name chromNode selenium/node-chrome-debug error is coming -> " Couldn't register this node: Error sending the registration request: The hub responded with 404 " using (Docker version 23.0.5, build bc4487a) in MacBook Air (M1, 2020)
For me the node containers are getting exited just after creating it or restarting it.please suggest
It can happen due to various issues, could be due to insufficient memory or hub and node versions are not correct, check configuration again if nodes are registered with the hub or not. Try to use docker compose with correct configuration to setup grid with latest hub and node images
since selenium 4 is now officially the new version docker, uses grid 4. so registering the node with the line from the video doesn't seem to connect. it keeps on loading and then gives error. can you look into it?
Hi @Karan , for selenium grid 4, configuring hub and node is somewhat different than what we did in the video of Selenium grid 3.
Here we need to setup environment by setting up bus events, subscribe port and publish event port i.e. tcp port 4442 and port 4443.
If u r using selenium/hub image 4th version then u will required to use 4th versions of the node images as well. Set==> SE_EVENT_BUS_PUBLISH_PORT , SE_EVENT_BUS_SUBSCRIBE_PORT , SE_EVENT_BUS_HOST while creating and registering the Node containers to the Hub Container. If you miss any one of the above environment setting then you won't be able to link nodes with Hub
I am going to add a separate video in the same series soon...
please add videos in selenium 4 how to register the grid and the video it?
What if I'll be using same machine for hub and node? Thanks
There won't be any issues as long as you are using docker or VM on same machine...
Hello I found the "selenium/node-opera-debug" and "selenium/node-firefox-debug" and "selenium/node-chrome-debug" the Greated column in Docker shows "3 years ago". Is that ok?
Images might not be updated but that won't be issue u can still run the automation it will work fine.
You can use selenium/node-chrome instead as both images are merged now
for me the chromenode is not able to connect the network ,I had done the same process as you shown it starting container of chrome but not connecting to the grid network
Try to remove network and create a new one.. Both hub node should use same network...
Hi, is there any way we can create a replica set so that the containers could scale as per the requirement? Example: My test cases are more and I want to launch more containers, can I do that?
Auto scaling of the containers not possible with docker compose... For now u can create multiple containers at the beginning only with docker compose scale cmd. Idle containers don't take memory or cpu utilisation will be normal.
any idea on how to use the selenium grid extension for docker?
need to check , not sure about extension for docker
U shown only for the linux node. What if we meet to add windows node. Can it be added in same network gridnetwork
The node machine is linux. Selenium will run on it
Currently i am running trying to setup as shown in video but when running this command docker run -d -p 4446:5900 -net gridnetwork -e HUB_HOST=seleniumHub -name chromNode selenium/node-chrome-debug error is coming -> " Couldn't register this node: Error sending the registration request: The hub responded with 404 "
using (Docker version 23.0.5, build bc4487a) in MacBook Air (M1, 2020)
same bro in my case -d and -p is showing errors
node-chrome-debug is deprecated . use node-chrome