Update Chrome Version

[ALegchilov]

Hey Maciej,
I tried to use latest chrome and hub images in aet-swarm.yml, but it doesn't work. I see 'Unknown error' in report.
What else should I do? Could you support?

[malaskowski]

hi @ALegchilov ,
What version of hub images did you try?
AET supports only Selenium 3.x. The latest 4.x will not work.
Some time ago I did give a try 3.141.59 and it was working fine (at least on my local setup). However, if you look at the AET code: https://github.com/wttech/aet/blob/master/osgi-dependencies/selenium/pom.xml#L37 you will see the 3.8.1 reference (that's the client's side responsible for communication with the SGrid Hub).

For troubleshooting, the best start is to look at logs. You can see logs of each service individually using docker CLI (docker service log).
Hope this helps.

[ALegchilov]

I was using 4.x hub version, however the purpose was just to take advantage of latest chrome.
Is it possible to use latest chrome along with basic selenium hub (v3.14)?
If I just update selenium/node-chrome:103.0 it leads to errors in conteiners.

2022-07-18 10:26:49,210 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing 2022-07-18 10:26:49,213 INFO RPC interface 'supervisor' initialized 2022-07-18 10:26:49,213 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2022-07-18 10:26:49,213 INFO supervisord started with pid 10 2022-07-18 10:26:50,221 INFO spawned: 'xvfb' with pid 12 2022-07-18 10:26:50,226 INFO spawned: 'vnc' with pid 13 2022-07-18 10:26:50,229 INFO spawned: 'novnc' with pid 14 2022-07-18 10:26:50,233 INFO spawned: 'selenium-node' with pid 15 2022-07-18 10:26:50,254 INFO success: selenium-node entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) SE_EVENT_BUS_HOST not set, exiting! 2022-07-18 10:26:50,585 INFO exited: selenium-node (exit status 1; not expected) 2022-07-18 10:26:51,272 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-07-18 10:26:51,272 INFO success: vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-07-18 10:26:51,272 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

[malaskowski]

Selenium 4.x will not work for sure with AET at the moment (selenium/node-chrome:103.0 runs on Selenium 4.x).

You may try the latest 3.x version. To be fair, versioning/tagging of https://hub.docker.com/u/selenium images it quite difficult to follow (some versions refer to the version of Selenium Webdriver, some to the version of browsers).
The most clear approach for me wat to follow the tag/version of Selenium. You can check on GitHub https://github.com/SeleniumHQ/docker-selenium/releases to see what's inside each version (what browsers etc.).

It looks that https://github.com/SeleniumHQ/docker-selenium/releases/tag/3.141.59-20210929 is the latest 3.x. No newer version of 3.x were released after this one. It contains chrome 94.0.

If you need a newer chrome, probably the easiest way is to build your custom selenium/node-chrome that base on the Selenium 3.x and upgrades the browser (fortunately https://github.com/SeleniumHQ/docker-selenium sources are open).

Another way would be upgrading AET to the 4.x version of Selenium and use the official images from Selenium (however, that might be quite big amount of work). For this path you must contact with the current AET project team on https://github.com/wttech/aet .

[ALegchilov]

Thank you for so detailed explaination, Maciej.