docker build was using the cached version of the our base image, selenium/standalone-chrome, every single time. The last time it was updated on our machine was chrome 69, over a year ago.
This is fixed by running docker pull selenium/standalone-$BROWSER before docker build.
Also adding the --rm flag to docker run, which should remove the container after the run completes (so we have fewer dangling images taking up disk space)
docker build
was using the cached version of the our base image, selenium/standalone-chrome, every single time. The last time it was updated on our machine was chrome 69, over a year ago.This is fixed by running
docker pull selenium/standalone-$BROWSER
beforedocker build
.Also adding the --rm flag to
docker run
, which should remove the container after the run completes (so we have fewer dangling images taking up disk space)