Currently facing an issue while setting up selenium 4 grid using the docker-compose file provided below. The error message "Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure" is being encountered, requiring assistance to resolve.
Docker-compose file:
# To execute this docker-compose yml file use `docker-compose -f docker-compose-v3-full-grid.yml up`
# Add the `-d` flag at the end for detached execution
# To stop the execution, hit Ctrl+C, and then `docker-compose -f docker-compose-v3-full-grid.yml down`
version: "3"
services:
selenium-event-bus:
image: selenium/event-bus:4.0.0-20211013
container_name: selenium-event-bus
ports:
- "4442:4442"
- "4443:4443"
- "5557:5557"
selenium-sessions:
image: selenium/sessions:4.0.0-20211013
container_name: selenium-sessions
ports:
- "5556:5556"
depends_on:
- selenium-event-bus
environment:
- SE_EVENT_BUS_HOST=selenium-event-bus
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
...
chrome:
image: selenium/node-chrome:4.0.0-20211013
shm_size: 2gb
depends_on:
- selenium-event-bus
environment:
- SE_EVENT_BUS_HOST=selenium-event-bus
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
ports:
- "6900:5900"
Run command:
mvn clean install
Executing this command triggers one cucumber test scenario via the test runner specified in testing.xml file.
Setup seems to be nearing completion as indicated by the logs below:
...LOG SNIPPET...
Error logs during test execution:
...ERROR LOGS SNIPPET...
Furthermore, when attempting to access the hub URL, the following message is displayed: https://i.stack.imgur.com/4OWDx.png
The issue pertains to how the remote driver object is initialized:
case CHROME:
ChromeOptions options = getChromeOptions();
try {
driver = new RemoteWebDriver(new URL("http://localhost:4444"), options);
} catch (MalformedURLException e) {
e.printStackTrace();
}
Laptop configuration: Mac m1 512GB
Seeking advice on resolving the encountered issue effectively.