The Hub receives a test to be executed along with information on which browser and 'platform' where the test should be run. The hub will use this information and delegate to a node that can service those needs.
dnguyen3/selenium-hub Dockerfile
$ docker run -d -p 4444:4444 --name selenium-hub dnguyen3/selenium-hub:latest
Once the hub is up and running will want to launch nodes that can run tests. Please run the below commands 3 times for each browser.
$ docker run -d --link selenium-hub:hub dnguyen3/selenium-node-chrome
$ docker run -d --link selenium-hub:hub dnguyen3/selenium-node-firefox
If you want to debug the headless browsers, you can run the following nodes:
$ docker run -d -P -p 5900:5900 --link selenium-hub:hub dnguyen3/selenium-node-chrome-debug
$ docker run -d -P -p 5901:5900 --link selenium-hub:hub dnguyen3/selenium-node-chrome-debug
$ docker run -d -P -p 5902:5900 --link selenium-hub:hub dnguyen3/selenium-node-chrome-debug
$ docker run -d -P -p 5903:5900 --link selenium-hub:hub dnguyen3/selenium-node-chrome-debug
$ docker run -d -P -p 5904:5900 --link selenium-hub:hub dnguyen3/selenium-node-chrome-debug
$ docker run -d -P -p 5950:5900 --link selenium-hub:hub dnguyen3/selenium-node-firefox-debug
$ docker run -d -P -p 5951:5900 --link selenium-hub:hub dnguyen3/selenium-node-firefox-debug
$ docker run -d -P -p 5952:5900 --link selenium-hub:hub dnguyen3/selenium-node-firefox-debug
$ docker run -d -P -p 5953:5900 --link selenium-hub:hub dnguyen3/selenium-node-firefox-debug
$ docker run -d -P -p 5954:5900 --link selenium-hub:hub dnguyen3/selenium-node-firefox-debug
Content type
Image
Digest
Size
138 MB
Last updated
almost 10 years ago
docker pull dnguyen3/selenium-hub