-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: Dynamic Grid setup fails when the docker images are missing locally #11342
Comments
@krmahadevan, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
After pulling the images manually I still cannot get any seession(as described in SeleniumHQ/docker-selenium#1719): selenium-node-docker-1 | 09:18:15.188 INFO [Docker.getImage] - Obtaining image: selenium/standalone-chrome:4.7.0-20221202 |
@victortanase because the fix has not been released. Probably on Monday or Tuesday. |
@diemol Hello! Just encountered this issue - any plans to release today? :) |
@diemol I have the same issue when the fix will be merged? |
Thank you, the issue was because of platformName capability not set configured in steretotype, so I fixed it. 2023-01-10 21:05:03 20:05:03.342 WARN [SeleniumSpanExporter$1.lambda$export$1] - Unable to create session: Could not start a new session. Could not start a new session. non-positive contentLength: 0 selenium-hub logs
node-docker logs
Any idea when will this fix be available? or we have to wait for newer version of selenium to be released and then for new docker image to be created to be able to use Dynamic grid? |
What happened?
When we attempt at following the documentation of Dynamic Grid the docker node does not come up and crashes.
How can we reproduce the issue?
Ensure that you dont have any of the selenium related docker container images in your machine by running
docker container prune
to prune the images being used by stopped containersdocker rmi $(docker images | grep selenium | awk '{print $3}')
clean up all selenium imagesCreate a docker-compose file named
docker-compose-v3-dynamic-grid.yml
that looks like below:In the same directory create a toml configuration file named
config.toml
with its contents as below:Setup socat forwarding (I am on Mac and so I installed
socat
and run the following command,socat -4 TCP-LISTEN:2375,fork UNIX-CONNECT:/var/run/docker.sock
Now bring up the nodes by running
docker-compose -f docker-compose-v3-dynamic-grid.yml up
Operating System
macOS
Selenium version
Java 4.6.0
What are the browser(s) and version(s) where you see this issue?
Not relevant
What are the browser driver(s) and version(s) where you see this issue?
Not relevant
Are you using Selenium Grid?
4.6.0
The text was updated successfully, but these errors were encountered: