Skip to content

Commit 72c7454

Browse files
author
rubytester
committed
Merge pull request SeleniumHQ#63 from SeleniumHQ/complete_pull4
complete base readme I missed for standalone debug
2 parents 10ca2c1 + c64b1dd commit 72c7454

File tree

1 file changed

+18
-2
lines changed

1 file changed

+18
-2
lines changed

README.md

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,9 @@ Images included:
1515
- __selenium/node-chrome__: Selenium node with Chrome installed, needs to be connected to a Selenium Hub
1616
- __selenium/node-firefox__: Selenium node with Firefox installed, needs to be connected to a Selenium Hub
1717
- __selenium/standalone-chrome__: Selenium standalone with Chrome installed
18-
- __selenium/standalone-firefox__: Selenium standalone with Firefox
18+
- __selenium/standalone-firefox__: Selenium standalone with Firefox installed
19+
- __selenium/standalone-chrome-debug__: Selenium standalone with Chrome installed and runs a VNC server
20+
- __selenium/standalone-firefox-debug__: Selenium standalone with Firefox installed and runs a VNC server
1921
- __selenium/node-chrome-debug__: Selenium node with Chrome installed and runs a VNC server, needs to be connected to a Selenium Hub
2022
- __selenium/node-firefox-debug__: Selenium node with Firefox installed and runs a VNC server, needs to be connected to a Selenium Hub
2123

@@ -25,8 +27,14 @@ Images included:
2527

2628
``` bash
2729
$ docker run -d -p 4444:4444 selenium/standalone-chrome:2.45.0
30+
# OR
31+
$ docker run -d -p 4444:4444 selenium/standalone-firefox:2.45.0
2832
```
2933

34+
Note: only one standalone image can run on port 4444 at a time.
35+
36+
To inspect visually what the browser is doing use the `standalone-chrome-debug` or `standalone-firefox-debug` images. [See debugging section for more...](#debugging)
37+
3038
### Selenium Grid Hub
3139

3240
``` bash
@@ -84,13 +92,21 @@ $ FF=$(docker run --rm --name=fx \
8492

8593
## Debugging
8694

87-
In the event you wish to visually see what the browser is doing you will want to run the selenium/node-chrome-debug and selenium/node-firefox-debug images.
95+
In the event you wish to visually see what the browser is doing you will want to run the `debug` variant of node or standalone images.
8896

8997
``` bash
9098
$ docker run -d -P --link selenium-hub:hub selenium/node-chrome-debug:2.45.0
9199
$ docker run -d -P --link selenium-hub:hub selenium/node-firefox-debug:2.45.0
92100
```
93101

102+
And for standalone:
103+
104+
``` bash
105+
$ docker run -d -p 4444:4444 selenium/standalone-chrome-debug:2.45.0
106+
# OR
107+
$ docker run -d -p 4444:4444 selenium/standalone-firefox-debug:2.45.0
108+
```
109+
94110
You can acquire the port that the VNC server is exposed to by running:
95111

96112
``` bash

0 commit comments

Comments
 (0)