* Don't run as root in Docker
This updates the start.sh script to create a group and user with the same GID
and UID as the working directory (normally /sitespeed.io), then use that for
running `node`. This fixes the issue of report files being owned by root.
This uses "chroot" to switch the new user instead of "su" because of the
signal handling issues mentioned at https://github.com/tianon/gosu.
I tested this with the following script:
#!/bin/bash
set -e
docker build -t sitespeedio/sitespeed.io:test .
docker run --rm -v "$PWD:/sitespeed.io" sitespeedio/sitespeed.io:test -b chrome --outputFolder chrome-result -n 1 https://www.example.com
docker run --rm -v "$PWD:/sitespeed.io" sitespeedio/sitespeed.io:test -b firefox --outputFolder firefox-result -n 1 https://www.example.com
docker run --cap-add=NET_ADMIN --rm -v "$PWD:/sitespeed.io" -e REPLAY=true sitespeedio/sitespeed.io:test --outputFolder wpr-result -n 1 -b chrome https://www.example.com
ls *result
* Allow "sudo ip" and "sudo route"
* - fixed some problems with selenium-docker failing in case for a lot off scenarios in one docker contained without rebutting
* Fixed some problems with selenium-docker failing in case for a lot off scenarios in one docker contained without rebutting
Mason Malone
soulgalore
Gideon Pyzer
Vitaliy Honcharenko
Peter Hedenskog