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
+12-12Lines changed: 12 additions & 12 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` 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 -p 4444:24444 -p 5920:25900 -v /dev/shm:/dev/shm \
23
-
-e VNC_PASSWORD=hola elgalu/selenium:2.47.1h
23
+
-e VNC_PASSWORD=hola elgalu/selenium:2.47.1i
24
24
25
25
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:
26
26
@@ -85,7 +85,7 @@ You can launch 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.
91
91
@@ -101,7 +101,7 @@ You can lunch a node only container via environment variables:
101
101
-p 25550:25550 -p 25551:25551 \
102
102
-e GRID=false -e CHROME=true -e FIREFOX=true \
103
103
-v $(pwd)/videos:/videos \
104
-
elgalu/selenium:2.47.1h
104
+
elgalu/selenium:2.47.1i
105
105
106
106
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.
107
107
@@ -142,9 +142,9 @@ There are also additional steps you can take to ensure you're using the correct
142
142
143
143
You can simply verify that image id is indeed the correct one.
if docker inspect -f='{{.Id}}' elgalu/selenium:2.47.1h |grep ${IMGID} &> /dev/null; then
145
+
# e.g. full image id for tag 2.47.1i
146
+
export IMGID=TBD
147
+
if docker inspect -f='{{.Id}}' elgalu/selenium:2.47.1i |grep ${IMGID} &> /dev/null; then
148
148
echo "Image ID tested ok"
149
149
else
150
150
echo "Image ID doesn't match"
@@ -154,8 +154,8 @@ You can simply verify that image id is indeed the correct one.
154
154
155
155
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.
@@ -283,7 +283,7 @@ If you git clone this repo locally, i.e. cd into where the Dockerfile is, you ca
283
283
284
284
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