Update docker instructions in the README

README.md

@@ -10,12 +10,12 @@ Whatever it is, the SSL exporter gives you visibility over those dimensions at t
     make
     ./ssl_exporter <flags>
 
-### Docker
-    make all docker
-    docker run -p 9219:9219 ssl-exporter:master <flags>
-
 Similarly to the blackbox_exporter, visiting [http://localhost:9219/probe?target=https://example.com](http://localhost:9219/probe?target=https://example.com) will return certificate metrics for example.com. The ```ssl_https_connect_success``` metric indicates if the probe has been successful.
 
+## Docker
+    docker pull ribbybibby/ssl-exporter
+    docker run -p 9219:9219 ssl-exporter:latest <flags>
+
 ## Flags
     ./ssl_exporter --help
  * __`--tls.insecure`:__ Skip certificate verification (default false). This is insecure but does allow you to collect metrics in the case where a certificate has expired. That being said, I feel that it's more important to catch verification failures than it is to identify an expired certificate, especially as the former includes the latter.
@@ -80,4 +80,4 @@ Identify instances that have failed to create a valid SSL connection:
 I've only exported a subset of the information you could extract from a certificate. It would be simple to add more, for instance organisational information, if there's a need.
 
 ## Acknowledgements
-The overall structure and implementation of this exporter is based on the [consul_exporter](https://github.com/prometheus/consul_exporter). The probing functionality borrows from the blackbox_exporter.
+The overall structure and implementation of this exporter is based on the [consul_exporter](https://github.com/prometheus/consul_exporter). The probing functionality borrows from the blackbox_exporter.