2.48.2b: Update image id and digest

Author: elgalu

CHANGELOG.md

@@ -11,7 +11,7 @@ How to get container versions
     google-chrome-stable --version && echo "\n"
     sc | grep build && BrowserStackLocal -version
 
-## 2.48.2b (2015-10-TBD)
+## 2.48.2b (2015-11-04)
  + Upgrade to Chrome to 46.0.2490.80
  + Upgrade to Firefox to 42.0 and fix mozilla.org => firefox ftp links
  + Upgrade to ubuntu:wily-20151019
@@ -27,8 +27,8 @@ How to get container versions
   + Python: 2.7.10
   + Sauce Connect 4.3.11, build 1757 2b421bb
   + BrowserStack Local version 4
-  + Image ID: TBD
-  + Digest: sha256:TBD
+  + Image ID: 4e3f3d0129a13bef199e336493bc1edaf321a4d388acac3abbc33600f70471d6
+  + Digest: sha256:156b394b944203b95d7d813e1f82022c8cf7714da3c8196fd6833033e10ac13f
 
 ## 2.48.2a (2015-10-20)
  + Upgrade to Selenium 2.48.2

README.md

@@ -209,7 +209,7 @@ There are also additional steps you can take to ensure you're using the correct
 You can simply verify that image id is indeed the correct one.
 
     # e.g. full image id for tag 2.48.2b
-    export IMGID=TBD
+    export IMGID=4e3f3d0129a13bef199e336493bc1edaf321a4d388acac3abbc33600f70471d6
     if docker inspect -f='{{.Id}}' elgalu/selenium:2.48.2b |grep ${IMGID} &> /dev/null; then
         echo "Image ID tested ok"
     else
@@ -221,7 +221,7 @@ You can simply verify that image id is indeed the correct one.
 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:
 
     # e.g. sha256 for tag 2.48.2b
-    export SHA=TBD
+    export SHA=156b394b944203b95d7d813e1f82022c8cf7714da3c8196fd6833033e10ac13f
     docker pull elgalu/selenium@sha256:${SHA}
 
 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.

scm-source.json

@@ -1,6 +1,6 @@
 {
     "url": "https://github.com/elgalu/docker-selenium",
-    "revision": "0ef85940e84cbd656e3e0b81ba551245686a9de5",
+    "revision": "d8d4622c03f3aeb283b694003727ae37ac415e2a",
     "author": "lgallucci",
     "status": ""
 }