Latest browser with Selenium 3 grid

[Abhijith Jeevaraj]

Hey, we are unable to use the selenium 4 grid due to stability issue and therefore have to revert back to selenium 3 grid.
Does anyone have a way to run the latest dockerized chrome browser on the selenium 3 grid since they stopped publishing those docker images. Has anyone generated a docker image that supports Selenium 3 grid. Any help is appreciated!

[⇜Krishnan Mahadevan⇝]

Hey, we are unable to use the selenium 4 grid due to stability issue and therefore have to revert back to selenium 3 grid.

While someone helps you out with the rest of your question, I am curious to know what stability issues you are experiencing? I think it would be good if you could please highlight them so that they can be addressed in the Grid4.

Does anyone have a way to run the latest dockerized chrome browser on the selenium 3 grid since they stopped publishing those docker images.

You want to run a Selenium 4 Node (that contains the latest chrome browser) against a Selenium 3 Hub ? I don't think that it's possible because the underlying architectures are different and the Node basically has newer ways of registering itself which the Selenium 3 Hub is not aware of (They are now event based which uses a Message queue for these things which wasn't the case in Grid3).

Has anyone generated a docker image that supports Selenium 3 grid. Any help is appreciated!

Here's how you go about doing it.

1. Clone the repo https://github.com/SeleniumHQ/docker-selenium
2. Checkout the tag "3.141.59-20210929" using the command "git checkout tags/3.141.59-20210929 -b experiment"
3. Build the image locally by running the command : "docker build -t selenium/node-chrome:local-build ."  (When you do this, the dockerfile that is available in the codebase will ensure that it picks the latest ChromeDriver and chrome browser that is available as of today)
4. If you have an intranet docker registry in your company, then you would also need to have the above built image to be published there, else your executions in your laptop will work fine,but the executions will fail when running on CI.

Here's a docker-compose file that I used to start the Hub and node

YAML

# To execute this docker-compose yml file use `docker-compose up -d`
# To stop the execution, hit Ctrl+C, and then `docker-compose down -v`
version: "3"
services:
  chrome:
    image: selenium/node-chrome:local-build
    shm_size: 2gb
    depends_on:
      - selenium-hub
    environment:
      - HUB_HOST=selenium-hub
  selenium-hub:
    image: selenium/hub:3.141.59
    container_name: selenium-hub
    ports:
      - "4444:4444"

Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/

My Technical Scribblings @ https://rationaleemotions.com/

On Fri, Oct 28, 2022 at 10:48 AM 'Abhijith Jeevaraj' via Selenium Users <seleniu...@googlegroups.com> wrote:

Hey, we are unable to use the selenium 4 grid due to stability issue and therefore have to revert back to selenium 3 grid.
Does anyone have a way to run the latest dockerized chrome browser on the selenium 3 grid since they stopped publishing those docker images. Has anyone generated a docker image that supports Selenium 3 grid. Any help is appreciated!

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/1f1dd8cc-e4c8-469e-86d6-5a0763435cb9n%40googlegroups.com.

[Abhijith Jeevaraj]

Thank you for the quick response and suggestions. I will try to build the docker image locally with those steps.

As for the stability issues, we have been observing the following issues with Selenium 4 grid which are currently preventing us from migrating to Grid 4 from Grid 3.
- Security scans causing the grid to break - #1646

- Memory leaks in grid components - #1694

- Random START_MAP error - #1507

These issues make it impossible for us to have a stable Selenium 4 grid up and therefore we are now exploring options.