You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 30, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+20-15Lines changed: 20 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,20 +19,24 @@
19
19
20
20
Note [SeleniumHQ/docker-selenium](https://github.com/SeleniumHQ/docker-selenium) project is more useful for building selenium grids while this one focuses on building disposable standalone seleniums with [video recording support](./docs/videos.md) and both browsers on the same container. It also adds some other features like [customizing the screen size](#screen-size) and [ssh access](#ssh) that can be particularly useful for tunneling support.
21
21
22
+
### Purpose
23
+
24
+
The purpose of this project is to have [Selenium][] running as simple and as fast as possible.
25
+
22
26
### Run
23
27
24
28
1. Pull the image and run the container
25
29
26
-
docker pull elgalu/selenium:2.53.0i
30
+
docker pull elgalu/selenium:2.53.0j
27
31
28
32
docker run --rm -ti --name=grid -p 4444:24444 -p 5900:25900 \
2. Wait until the grid starts properly before starting the tests _(Optional but recommended)_
32
36
33
37
docker exec grid wait_all_done 30s
34
38
35
-
After this, Selenium should be up and running at `http://localhost:4444/wd/hub`. Open the url in your browser to confirm it is running.
39
+
After this, [Selenium][] should be up and running at `http://localhost:4444/wd/hub`. Open the url in your browser to confirm it is running.
36
40
If you are using Mac (OSX) or [Microsoft Windows](https://docs.docker.com/engine/installation/windows/)`localhost` won't work! Find out the correct IP through `boot2docker ip` or `docker-machine ip default`.
37
41
38
42
**Notes:**
@@ -61,7 +65,7 @@ You can also ssh into the machine as long as `SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa
61
65
docker run --rm -ti --name=grid -p=4444:24444 -p=5900:25900 -p=22222:22222 \
62
66
-e SSHD=true \
63
67
-e SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa.pub)" \
64
-
-v /dev/shm:/dev/shm elgalu/selenium:2.53.0i
68
+
-v /dev/shm:/dev/shm elgalu/selenium:2.53.0j
65
69
66
70
Then
67
71
@@ -72,7 +76,7 @@ Include `-X` in ssh command if you want to redirect the started GUI programs to
72
76
docker run --rm -ti --name=grid -p=4444:24444 -p=5900:25900 -p=22222:22222 \
73
77
-e SSHD=true -e SSHD_X11FORWARDING=yes \
74
78
-e SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa.pub)" \
75
-
-v /dev/shm:/dev/shm elgalu/selenium:2.53.0i
79
+
-v /dev/shm:/dev/shm elgalu/selenium:2.53.0j
76
80
77
81
Then
78
82
@@ -90,12 +94,12 @@ Supervisor exposes an http server but is not enough to bind the ports via `docke
90
94
### Screen size
91
95
You can set a custom screen size at docker run time by providing `SCREEN_WIDTH` and `SCREEN_HEIGHT` environment variables:
92
96
93
-
docker pull elgalu/selenium:2.53.0i
97
+
docker pull elgalu/selenium:2.53.0j
94
98
95
99
docker run -d --name=grid -p 4444:24444 -p 5900:25900 \
96
100
-v /dev/shm:/dev/shm -e VNC_PASSWORD=hola \
97
101
-e SCREEN_WIDTH=1920 -e SCREEN_HEIGHT=1480 \
98
-
elgalu/selenium:2.53.0i
102
+
elgalu/selenium:2.53.0j
99
103
100
104
docker exec grid wait_all_done 10s
101
105
@@ -153,7 +157,7 @@ You need to pass the environment variable `-e NOVNC=true` in order to start the
153
157
154
158
docker run --rm -ti --name=grid -p 4444:24444 -p 5900:25900 \
If the VNC password was randomly generated find out with
159
163
@@ -226,9 +230,9 @@ There are also additional steps you can take to ensure you're using the correct
226
230
227
231
You can simply verify that image id is indeed the correct one.
228
232
229
-
# e.g. full image id for tag 2.53.0i
233
+
# e.g. full image id for tag 2.53.0j
230
234
export IMGID="<<Please see CHANGELOG.md>>"
231
-
if docker inspect -f='{{.Id}}' elgalu/selenium:2.53.0i |grep ${IMGID} &> /dev/null; then
235
+
if docker inspect -f='{{.Id}}' elgalu/selenium:2.53.0j |grep ${IMGID} &> /dev/null; then
232
236
echo "Image ID tested ok"
233
237
else
234
238
echo "Image ID doesn't match"
@@ -238,7 +242,7 @@ You can simply verify that image id is indeed the correct one.
238
242
239
243
Given docker.io currently allows to push the same tag image twice this represent a security concern but since docker >= 1.6.2 is possible to fetch the digest sha256 instead of the tag so you can be sure you're using the exact same docker image every time:
@@ -373,7 +377,7 @@ If you git clone this repo locally, i.e. cd into where the Dockerfile is, you ca
373
377
374
378
If you prefer to download the final built image from docker you can pull it, personally I always prefer to build them manually except for the base images like Ubuntu 14.04.2:
375
379
376
-
docker pull elgalu/selenium:2.53.0i
380
+
docker pull elgalu/selenium:2.53.0j
377
381
378
382
### 2. Use this image
379
383
@@ -482,3 +486,4 @@ Powered by Supervisor, the container leaves many logs;
0 commit comments