Warning: fopen(/tmp/SghXTngBZPli-OhHugp.tmp): failed to open stream: Disk quota exceeded in /home/executea/public_html/blog/wp-admin/includes/class-wp-filesystem-ftpext.php on line 139
Warning: unlink(/tmp/SghXTngBZPli-OhHugp.tmp): No such file or directory in /home/executea/public_html/blog/wp-admin/includes/class-wp-filesystem-ftpext.php on line 142
In our last post on docker compose, we discussed what docker compose is and how to work with docker compose in much greater working detail.
In this post we will go a step further to configure selenium grid with docker compose. We have also discussed about configuring and working with Selenium Grid using Docker in greater detail in our executeautomation, please go ahead and read the article from here
Here is the complete video to configure and work with Docker compose for Selenium grid
Thanks for reading the post and watching the video!!!
Please leave your comments and let me know if there is anything I should update in this post.
Thanks,
Karthik KK
Post Author:
Karthik kk
5 Replies to “Setting Selenium grid with Docker compose”
Thank you for sharing such a nice and interesting blog with us. Hope it might be much useful for us. keep on updating…!!
This video is really helpful, using this video I prepare yml file but I am getting Error :-[31mERROR[0m: yaml.scanner.ScannerError: mapping values are not allowed here
in “.\docker-compose.yml”, line 8, column 14
My yml file code is :-
Thank you for sharing such a nice and interesting blog with us. Hope it might be much useful for us. keep on updating…!!
This video is really helpful, using this video I prepare yml file but I am getting Error :-[31mERROR[0m: yaml.scanner.ScannerError: mapping values are not allowed here
in “.\docker-compose.yml”, line 8, column 14
My yml file code is :-
seleniumhub:
image: selenium/hub
ports:
4444:4444
chromenode:
image: selenium/node-chrome
ports:
-5555
links:
-seleniumhub
Please review and provide solution
Indentation is very important in yml file, please see the video where I have indentation in it.
Thanks,
Karthik KK
Do we need to provide chromedriver exe path when we execute our test on docker node chrome debug image?
Like System.setProperty(“webdriver.chrome.driver”, “/Users/nn/Library/AutomationSetUp/chromedriver”);
Or it’s not required?
Like these lines are enough:
DesiredCapabilities cap = DesiredCapabilities.firefox();
cap.setCapability(“version”, “”);
cap.setPlatform(Platform.LINUX);
driver = new RemoteWebDriver(new URL(“http://localhost:4444/wd/hub”), cap);
Please confirm.
Thanks!
For Chrome docker node image you dont really have to give chromedriver in code, since it will be there within the image if I am not mistaken