Remove sitespeed from the docker compose file (#3020)

* Remove sitespeed from the docker compose file

* Docs cleanup

docker/docker-compose.yml

@@ -1,11 +1,5 @@
 version: '3'
 services:
-    sitespeed.io:
-      image: sitespeedio/sitespeed.io
-      command: -V
-      shm_size: 1g
-      volumes:
-            - ./sitespeed-result/:/sitespeed.io/sitespeed-result
     grafana:
       image: grafana/grafana:7.0.0
       depends_on:

docs/documentation/sitespeed.io/performance-dashboard/index.md

@@ -26,7 +26,7 @@ You need [Docker](https://docs.docker.com/engine/installation/) and [Docker Comp
 
 1. Download our Docker compose file: <code>curl -O https://raw.githubusercontent.com/sitespeedio/sitespeed.io/master/docker/docker-compose.yml</code>
 2. Run: <code>docker-compose up -d</code> (make sure you run the latest [Docker compose](https://docs.docker.com/compose/install/) version)
-3. Run sitespeed to get some metrics: <code> docker-compose run sitespeed.io https://www.sitespeed.io/ --graphite.host=graphite</code>
+3. Run sitespeed to get some metrics: <code> docker run --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io:{% include version/sitespeed.io.txt %} --graphite.host=127.0.0.1</code>
 4. Access the dashboard: http://127.0.0.1:3000 (if you use docker machine you need to get the ip with `docker-machine ip`)
 5. When you are done you can shut down and remove all the Docker containers by running <code>docker-compose stop && docker-compose rm</code>. Container data will be kept.
 6. To start from scratch, also remove the Graphite and Grafana data volumes by running `docker volume rm performancedashboard_graphite performancedashboard_grafana`.
@@ -137,14 +137,10 @@ To run this in production (=not on your local dev machine) you should make some
 ## Memory & CPU
 How large will your instances need to be? You need to have enough memory for Chrome/Firefox (yep they can really use a lot of memory for some sites). Before we used a $80 instance on Digital Ocean (8GB memory, 4 Core processors) but we switched to use AWS c5.large for dashboard.sitespeed.io. The reason is that the metrics are so more stable on AWS than Digital Ocean. We have tried out most cloud providers and AWS gave us the most stable metrics.
 
-If you test a lot a pages (100+) in the same run, your NodeJS process can run out of memory (default memory for NodeJS is 1.76 GB). You can change and increase by setting MAX_OLD_SPACE_SIZE like this in your compose file:
-
-```yaml
-services:
-    sitespeed.io:
-      environment:
-        - MAX_OLD_SPACE_SIZE=3072
+If you test a lot a pages (100+) in the same run, your NodeJS process can run out of memory (default memory for NodeJS is 1.76 GB). You can change and increase by setting MAX_OLD_SPACE_SIZE:
 
+```bash
+docker run -e MAX_OLD_SPACE_SIZE=4096 --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io:{% include version/sitespeed.io.txt %} https://www.sitespeed.io/
 ```
 
 ## Cost