Ivan Krutov

@denispnz you may have a self-signed certificate with Root CA preinstalled on your workstation but obviously missing inside Selenoid images. Take a look at this page: https://stackoverflow.com/questions/24507078/how-to-deal-with-certificates-using-selenium

@ashanirmala7 e.g. S3 bucket in public cloud?

@ashanirmala7 you can deploy an S3-compatible storage with [minio](https://github.com/minio/minio).

@desislava453 any error messages when getting `504`?

@megolee Selenoid is just a Selenium API and does not know whether your test is passing or failing. Marking tests as passed or failed is test framework responsibility.

@megolee the only feature Selenoid provides is `name` capability. This allows to mark any browser session being executed with custom label (e.g. test case name). https://aerokube.com/selenoid/latest/#_custom_test_name_name

@deepticake using `selenoid/chrome:latest` is a bad idea - to have a stable cluster use tagged images, e.g. `selenoid/chrome:76.0`.

@deepticake you have to restart Selenoid after changing config file and pull respective image.

@deepticake could be a Chromedriver \ client issue then. Selenoid just proxies everything to Chromedriver. This Java test passed while we were building the image: https://github.com/aerokube/selenoid-container-tests/blob/master/src/test/java/com/aerokube/selenoid/TestCookies.java

@deepticake 1) This outdated Dockerfile still exists because of a bug in Docker Hub preventing us from deleting it. Correct driver versions are here: https://aerokube.com/selenoid/latest/#_browser_image_information 2) DBUS is not needed...