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.
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.
22
22
@@ -34,10 +34,10 @@ You can also configure [xvfb](https://docs.travis-ci.com/user/gui-and-headless-b
34
34
35
35
1. Pull the image and run the container
36
36
37
-
docker pull elgalu/selenium:2.53.0l
37
+
docker pull elgalu/selenium:2.53.0o
38
38
39
39
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)_
43
43
@@ -62,7 +62,7 @@ This image is designed to run one test on each docker container but if you still
62
62
docker run --rm -ti --name=grid -p 4444:24444 -p 5900:25900 \
63
63
-v /dev/shm:/dev/shm -e VNC_PASSWORD=hola \
64
64
-e MAX_INSTANCES=20 -e MAX_SESSIONS=20 \
65
-
elgalu/selenium:2.53.0l
65
+
elgalu/selenium:2.53.0o
66
66
67
67
The drawback is that all tests will run on the same desktop meaning the video recording will only capture the browser in the foreground but it's in the roadmap to make all this transparent, see issues [#78](https://github.com/elgalu/docker-selenium/issues/78) and [#77](https://github.com/elgalu/docker-selenium/issues/77).
68
68
@@ -84,7 +84,7 @@ You can also ssh into the machine as long as `SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa
84
84
docker run --rm -ti --name=grid -p=4444:24444 -p=5900:25900 -p=22222:22222 \
85
85
-e SSHD=true \
86
86
-e SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa.pub)" \
87
-
-v /dev/shm:/dev/shm elgalu/selenium:2.53.0l
87
+
-v /dev/shm:/dev/shm elgalu/selenium:2.53.0o
88
88
89
89
Then
90
90
@@ -95,7 +95,7 @@ Include `-X` in ssh command if you want to redirect the started GUI programs to
95
95
docker run --rm -ti --name=grid -p=4444:24444 -p=5900:25900 -p=22222:22222 \
96
96
-e SSHD=true -e SSHD_X11FORWARDING=yes \
97
97
-e SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa.pub)" \
98
-
-v /dev/shm:/dev/shm elgalu/selenium:2.53.0l
98
+
-v /dev/shm:/dev/shm elgalu/selenium:2.53.0o
99
99
100
100
Then
101
101
@@ -113,12 +113,12 @@ Supervisor exposes an http server but is not enough to bind the ports via `docke
113
113
### Screen size
114
114
You can set a custom screen size at docker run time by providing `SCREEN_WIDTH` and `SCREEN_HEIGHT` environment variables:
115
115
116
-
docker pull elgalu/selenium:2.53.0l
116
+
docker pull elgalu/selenium:2.53.0o
117
117
118
118
docker run -d --name=grid -p 4444:24444 -p 5900:25900 \
119
119
-v /dev/shm:/dev/shm -e VNC_PASSWORD=hola \
120
120
-e SCREEN_WIDTH=1920 -e SCREEN_HEIGHT=1480 \
121
-
elgalu/selenium:2.53.0l
121
+
elgalu/selenium:2.53.0o
122
122
123
123
docker exec grid wait_all_done 10s
124
124
@@ -176,7 +176,7 @@ You need to pass the environment variable `-e NOVNC=true` in order to start the
176
176
177
177
docker run --rm -ti --name=grid -p 4444:24444 -p 5900:25900 \
If the VNC password was randomly generated find out with
182
182
@@ -249,9 +249,9 @@ There are also additional steps you can take to ensure you're using the correct
249
249
250
250
You can simply verify that image id is indeed the correct one.
251
251
252
-
# e.g. full image id for tag 2.53.0l
252
+
# e.g. full image id for tag 2.53.0o
253
253
export IMGID="<<Please see CHANGELOG.md>>"
254
-
if docker inspect -f='{{.Id}}' elgalu/selenium:2.53.0l |grep ${IMGID} &> /dev/null; then
254
+
if docker inspect -f='{{.Id}}' elgalu/selenium:2.53.0o |grep ${IMGID} &> /dev/null; then
255
255
echo "Image ID tested ok"
256
256
else
257
257
echo "Image ID doesn't match"
@@ -261,7 +261,7 @@ You can simply verify that image id is indeed the correct one.
261
261
262
262
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:
@@ -396,7 +396,7 @@ If you git clone this repo locally, i.e. cd into where the Dockerfile is, you ca
396
396
397
397
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:
0 commit comments