Chromedriver docker container is not pinned

[mathieuhelie]

This is the actual issue behind blueimp/chromedriver#3

When the chromedriver image is updated on dockerhub it is automatically released to all users of this repo, even if the change is not backwards-compatible with the current pinned version of the nightwatch container.

[blueimp]

At the moment it is very unlikely that I will add tagged versions of the Chromedriver Docker image.

The reason for this is that it would be very difficult to properly express what a version stands for.
There are multiple changing parts in the Chromedriver image:

1. The Chrome version
2. The Chromedriver version
3. The Docker image configuration

I will try to keep changes to the Docker image configuration to a minimum, but also won't guarantee so.

My recommendation for anyone using the Chromedriver image for critical infrastructure is to create a fork of the repo and you own Docker automated build.