Closed land0r closed 10 months ago
I don't think this is an issue from these images. You need to check why the container you are running with tests cannot connect back to the host. Am I missing something?
@diemol thank you! I will check the config files and docker network with those containers again. And then let you know tomorrow. So, do you think that this is only the reason?
@diemol okay, so the problem was with the docker network. I have to add Seleniarm container to the docker network where we have the nginx container and then modify hosts file for accessing the domain from the nginx container inside the Seleniarm container. You were right, thanks a lot! Sorry for the false alarm, but I didn't find any documentation about that on the main page of the repo
It is tricky to document every single use case. We have examples with docker-compose and others. This issue lays more in the "how to use docker" section.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
What happened?
While running acceptance tests inside another Docker container, I faced connection issues. The tests could not establish a connection to the Selenium server on port 4444 inside the SeleniARM Docker container, resulting in the following error:
Command used to start Selenium Grid with Docker
Relevant log output
Operating System
MacBook Apple M1 Pro, MacOS Sonoma 14.0 (23A344)
Docker Selenium version (tag)
4.10.0 (revision c14d967899)