mirror
/
sitespeed.io
mirror of https://github.com/sitespeedio/sitespeed.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
sitespeed.io/docs/documentation/sitespeed.io/docker/index.md

6.4 KiB
Raw Blame History

layout title description keywords nav image twitterdescription
default Use Docker to run sitespeed.io. With Docket you get a prebuilt container with sitespeed.io, Firefox, Chrome and XVFB. docker, documentation, web performance, sitespeed.io documentation https://www.sitespeed.io/img/sitespeed-2.0-twitter.png Use Docker to run sitespeed.io.

Documentation / Docker

Docker

{:.no_toc}

  • Lets place the TOC here {:toc}

Containers

Docker is the preferred installation method because you get everything for free :)

It also contains FFMpeg, Imagemagick so we can record a video and get metrics like SpeedIndex using VisualMetrics.

Structure

The structure looks like this:

NodeJS with Ubuntu 16 -> VisualMetrics dependencies -> Firefox/Chrome/xvfb -> sitespeed.io

The first container installs NodeJS (latest LTS) on Ubuntu 16. The next one adds the dependencies (FFMpeg, ImageMagick and some Python libraries) needed to run VisualMetrics. Then we install specific version of Firefox, Chrome and then xvfb. It's important to lock down the browsers to specific versions because it has been a real mess using Firefox the last half year (to be fair Chrome/Selenium have also had issues in the past). Then in last step, we add sitespeed and tag it to the sitespeed.io version number.

Running in Docker

The simplest way to run using Firefox:

$ docker run --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io -b firefox https://www.sitespeed.io/

That will map the current directory inside Docker and output the result directory there.

If you wanna use Chrome:

$ docker run --shm-size=1g --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io -b chrome https://www.sitespeed.io/

Note: The shm-size increases the memory for the GPU (default is 64mb and that is too small) see https://github.com/elgalu/docker-selenium/issues/20.

If you want to feed sitespeed with a list of URLs in a file (here named myurls.txt), add the file to your current directory and do like this:

docker run --shm-size=1g --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io myurls.txt -b chrome

In the real world you should always specify the exact version (tag) of the Docker container to make sure you use the same version everytime (else you will download the latest tag, meaning you can have major changes between test runs without you even knowing). Specify the tag after the container name(X.Y.Z) in this example. The tag/version number will be the same number as the sitespeed.io release:

docker run --shm-size=1g --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io:X.Y.Z https://www.sitespeed.io/ -b chrome

More about volumes

If you want to feed sitespeed.io with a file with URLs or if you want the HTML result, you should setup a volume. Sitespeed.io will do all the work inside the container in a directory located /sitespeed.io. To setup your current working directory add the -v "$(pwd)":/sitespeed.io to your parameter list. Using "$(pwd)" will default to the root user directory. In order to specify the location, simply define an absolute path: -v /Users/user/path:/sitespeed.io

If you run on Windows, it could be that you need to map a absolute path. If you have problems on Windows please check https://docs.docker.com/docker-for-windows/.

Update (download a newer sitespeed.io)

Updating to a newer version is easy, change X.Y.Z to the version you want to use:

docker pull sitespeedio/sitespeed.io:X.Y.Z

Or alternatively pull the latest version:

docker pull sitespeedio/sitespeed.io

And then change your start script (or where you start your container) to use the new version number.

If you don't use version number (you should!) then just pull the container and your next run will use the latest version.

Synchronize docker machines time with host

If you want to make sure your container have the time as the host, you can do that by adding -v /etc/localtime:/etc/localtime:ro (but you need to be on Linux).

Full example:

$ docker run --rm -v "$(pwd)":/sitespeed.io -v /etc/localtime:/etc/localtime:ro sitespeedio/sitespeed.io -b firefox https://www.sitespeed.io/

Access localhost

If you run a server local on your machine and want to access it with sitespeed.io you can do that on your Mac by using the Docker fixed ip 192.168.65.1:

$ docker run --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io -b firefox http://192.168.65.1:4000/

Troubleshooting

Inspect the container

In 4.0 we autostart sitespeed.io. If you wanna check what's in the container, you can do that by changing the entry point.

docker run -it --entrypoint bash sitespeedio/sitespeed.io:4.0.0

Visualize your test in XVFB

The docker containers have x11vnc installed which enables visualization of the test running inside Xvfb. To view the tests, follow these steps:

  • You will need to run the sitespeed.io image by exposing a PORT for vnc server . By default, it is 5900. If you plan to change your port for VNC server, then you need to expose that port.
docker run --shm-size=512m --privileged --rm -v "$(pwd)":/sitespeed.io -p 5900:5900 sitespeedio/sitespeed.io https://www.sitespeed.io/ -b chrome
  • Find the container id of the docker container for sitespeed by running:
docker ps
  • Enter into your running docker container for sitespeed.io by executing:
docker exec -it <container-id> bash
  • Find the Xvfb process using ps -ef. It should be using DISPLAY=:99.
  • Run
x11vnc -display :99 -storepasswd

Enter any password. This will start your VNC server which you can use by any VNC client to view:

  • Download VNC client like RealVNC
  • Enter VNC server : 0.0.0.0:5900
  • When prompted for password, enter the password you entered while creating the vnc server.
  • You should be able to view the contents of Xvfb.