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: CHANGELOG.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,28 @@ Note sha256 digests are generated after pushing the image to the registry theref
4
4
5
5
Note image ids also change after scm-source.json has being updated which triggers a cyclic problem so value TBD will be set here and updated in the [release][] page by navigating into any release tag.
6
6
7
+
## 2.47.1a (2015-07-30)
8
+
+ Upgrade selenium from 2.46.0 to 2.47.1 (Leo Gallucci)
9
+
+ Upgrade chrome stable to 44.0.2403.125
10
+
+ Add -e MEM_JAVA to allow to pass custom values like "1024m".
Copy file name to clipboardExpand all lines: README.md
+39-19Lines changed: 39 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Note SeleniumHQ/docker-selenium project is more useful for building selenium gri
19
19
In general: add `sudo` only if needed in your environment and `--privileged` if you really need it.
20
20
21
21
sudo docker run --privileged -p 4444:24444 -p 5920:25900 \
22
-
-e VNC_PASSWORD=hola elgalu/selenium:2.46.0-06
22
+
-e VNC_PASSWORD=hola elgalu/selenium:2.47.1a
23
23
24
24
### Non-privileged
25
25
### Run
@@ -31,7 +31,7 @@ If your setup is correct, privileged mode and sudo should not be necessary:
31
31
-e SCREEN_WIDTH=1920 -e SCREEN_HEIGHT=1080 \
32
32
-e VNC_PASSWORD=hola \
33
33
-e SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa.pub)" \
34
-
elgalu/selenium:2.46.0-06
34
+
elgalu/selenium:2.47.1a
35
35
36
36
Make sure `docker run` finishes with **selenium all done and ready for testing** else you won't be able to start your tests. To perform this check programatically please use this command where `ch` is the name of the container:
37
37
@@ -96,7 +96,7 @@ You can lunch a grid only container via environment variables:
The important part above is `-e CHROME=false -e FIREFOX=false` which tells the docker image not run run default chorme and firefox nodes turning the container into a grid-only one.
102
102
@@ -112,7 +112,7 @@ You can lunch a node only container via environment variables:
112
112
-p 25550:25550 -p 25551:25551 \
113
113
-e GRID=false -e CHROME=true -e FIREFOX=true \
114
114
-v $(pwd)/videos:/videos \
115
-
elgalu/selenium:2.46.0-06
115
+
elgalu/selenium:2.47.1a
116
116
117
117
The important part above is `-e GRID=false` which tells the container to be a node-only node, this this case with 2 browsers `-e CHROME=true -e FIREFOX=true` but could be just 1.
118
118
@@ -137,9 +137,9 @@ There are also additional steps you can take to ensure you're using the correct
137
137
138
138
You can simply verify that image id is indeed the correct one.
if docker inspect -f='{{.Id}}' elgalu/selenium:2.46.0-06 |grep ${IMGID} &> /dev/null; then
140
+
# e.g. full image id for tag 2.47.1a
141
+
export IMGID=TBD
142
+
if docker inspect -f='{{.Id}}' elgalu/selenium:2.47.1a |grep ${IMGID} &> /dev/null; then
143
143
echo "Image ID tested ok"
144
144
else
145
145
echo "Image ID doesn't match"
@@ -149,8 +149,8 @@ You can simply verify that image id is indeed the correct one.
149
149
150
150
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:
You can find all digests sha256 and image ids per tag in the [CHANGELOG](./CHANGELOG.md) so as of now you just need to trust the sha256 in the CHANGELOG. Bullet proof is to fork this project and build the images yourself if security is a big concern.
@@ -272,7 +272,7 @@ If you git clone this repo locally, i.e. cd into where the Dockerfile is, you ca
272
272
273
273
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:
274
274
275
-
docker pull elgalu/selenium:2.46.0-06
275
+
docker pull elgalu/selenium:2.47.1a
276
276
277
277
#### 2. Use this image
278
278
@@ -334,10 +334,30 @@ All output is sent to stdout so it can be inspected by running:
334
334
$ docker logs -f <container-id|container-name>
335
335
```
336
336
337
-
Container leaves a few logs files to see what happened:
337
+
Powered by Supervisor, the container leaves many logs;
0 commit comments