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
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
* google-chrome-stable
6
6
* google-chrome-beta
7
7
* google-chrome-unstable
8
-
* firefox stable latest 17 versions
8
+
* firefox stable latest 18 versions
9
9
* VNC access (useful for debugging the container)
10
10
* mkv video recording
11
11
* fluxbox or openbox (lightweight window managers)
@@ -20,7 +20,7 @@ Note SeleniumHQ/docker-selenium project is more useful for building selenium gri
20
20
In general add `sudo` only if needed in your environment and `--privileged` or `-v /dev/shm:/dev/shm` if you really need it like when [Chrome crashes](https://github.com/elgalu/docker-selenium/issues/20) during your high gpu intensive tests.
21
21
22
22
docker run --rm --name=grid -p 4444:24444 -p 5920:25900 \
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 `grid` is the name of the container:
26
26
@@ -83,7 +83,7 @@ You need to pass the environment variable `-e NOVNC=true` in order to start the
83
83
84
84
docker run --rm --name=grid -p 4444:24444 -p 5920:25900 \
85
85
-e NOVNC=true \
86
-
elgalu/selenium:2.47.1l
86
+
elgalu/selenium:2.47.1m
87
87
88
88
If the VNC password was randomly generated find out with
89
89
@@ -96,7 +96,7 @@ If the VNC password was randomly generated find out with
96
96
You can launch a grid only container via environment variables:
97
97
98
98
docker run --rm --name=hub -p 4444:24444 -p 5930:25900 \
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
@@ -110,7 +110,7 @@ You can lunch a node only container via environment variables:
110
110
-e SELENIUM_HUB_PORT=4444 \
111
111
-e SELENIUM_NODE_HOST=docker.host \
112
112
-e GRID=false -e CHROME=true -e FIREFOX=true \
113
-
elgalu/selenium:2.47.1l
113
+
elgalu/selenium:2.47.1m
114
114
115
115
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.
116
116
@@ -124,7 +124,7 @@ Start the grid with Chrome and Firefox
if docker inspect -f='{{.Id}}' elgalu/selenium:2.47.1l |grep ${IMGID} &> /dev/null; then
186
+
# e.g. full image id for tag 2.47.1m
187
+
export IMGID=TBD
188
+
if docker inspect -f='{{.Id}}' elgalu/selenium:2.47.1m |grep ${IMGID} &> /dev/null; then
189
189
echo "Image ID tested ok"
190
190
else
191
191
echo "Image ID doesn't match"
@@ -195,8 +195,8 @@ You can simply verify that image id is indeed the correct one.
195
195
196
196
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.
@@ -324,7 +324,7 @@ If you git clone this repo locally, i.e. cd into where the Dockerfile is, you ca
324
324
325
325
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