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
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -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` if you really need it.
21
21
22
22
sudo docker run --privileged -p 4444:24444 -p 5920:25900 \
23
-
-e VNC_PASSWORD=hola elgalu/selenium:2.47.1e
23
+
-e VNC_PASSWORD=hola elgalu/selenium:2.47.1f
24
24
25
25
### Non-privileged
26
26
### Run
@@ -32,7 +32,7 @@ If your setup is correct, privileged mode and sudo should not be necessary:
32
32
-e SCREEN_WIDTH=1920 -e SCREEN_HEIGHT=1080 \
33
33
-e VNC_PASSWORD=hola \
34
34
-e SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa.pub)" \
35
-
elgalu/selenium:2.47.1e
35
+
elgalu/selenium:2.47.1f
36
36
37
37
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:
38
38
@@ -97,7 +97,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.
103
103
@@ -113,7 +113,7 @@ You can lunch a node only container via environment variables:
113
113
-p 25550:25550 -p 25551:25551 \
114
114
-e GRID=false -e CHROME=true -e FIREFOX=true \
115
115
-v $(pwd)/videos:/videos \
116
-
elgalu/selenium:2.47.1e
116
+
elgalu/selenium:2.47.1f
117
117
118
118
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.
119
119
@@ -138,9 +138,9 @@ There are also additional steps you can take to ensure you're using the correct
138
138
139
139
You can simply verify that image id is indeed the correct one.
if docker inspect -f='{{.Id}}' elgalu/selenium:2.47.1e |grep ${IMGID} &> /dev/null; then
141
+
# e.g. full image id for tag 2.47.1f
142
+
export IMGID=TBD
143
+
if docker inspect -f='{{.Id}}' elgalu/selenium:2.47.1f |grep ${IMGID} &> /dev/null; then
144
144
echo "Image ID tested ok"
145
145
else
146
146
echo "Image ID doesn't match"
@@ -150,8 +150,8 @@ You can simply verify that image id is indeed the correct one.
150
150
151
151
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.
@@ -279,7 +279,7 @@ If you git clone this repo locally, i.e. cd into where the Dockerfile is, you ca
279
279
280
280
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