A docker version of LibreSpeed is available here: GitHub Packages
To download LibreSpeed from the docker repo, use this command:
docker pull ghcr.io/librespeed/speedtest
You will now have a new docker image called librespeed/speedtest
.
To start the container using docker compose the following configuration can be used:
version: '3.7'
services:
speedtest:
container_name: speedtest
image: ghcr.io/librespeed/speedtest:latest
restart: always
environment:
MODE: standalone
#TITLE: "LibreSpeed"
#TELEMETRY: "false"
#ENABLE_ID_OBFUSCATION: "false"
#REDACT_IP_ADDRESSES: "false"
#PASSWORD:
#EMAIL:
#DISABLE_IPINFO: "false"
#DISTANCE: "km"
#WEBPORT: 80
ports:
- "80:80" # webport mapping (host:container)
Please adjust the environment variables according to the intended operating mode.
If you want to install LibreSpeed on a single server, you need to configure it in standalone mode. To do this, set the MODE
environment variable to standalone
.
The test can be accessed on port 80.
Here's a list of additional environment variables available in this mode:
TITLE
: Title of your speed test. Default value:LibreSpeed
TELEMETRY
: Whether to enable telemetry or not. If enabled, you maybe want your data to be persisted. See below. Default value:false
ENABLE_ID_OBFUSCATION
: When set to true with telemetry enabled, test IDs are obfuscated, to avoid exposing the database internal sequential IDs. Default value:false
REDACT_IP_ADDRESSES
: When set to true with telemetry enabled, IP addresses and hostnames are redacted from the collected telemetry, for better privacy. Default value:false
PASSWORD
: Password to access the stats page. If not set, stats page will not allow accesses.EMAIL
: Email address for GDPR requests. Must be specified when telemetry is enabled.IPINFO_APIKEY
: API key for ipinfo.io. Optional, but required if you expect to serve a large number of testsDISABLE_IPINFO
: If set to true, ISP info and distance will not be fetched from ipinfo.io. Default: value:false
DISTANCE
: WhenDISABLE_IPINFO
is set to false, this specifies how the distance from the server is measured. Can be eitherkm
for kilometers,mi
for miles, or an empty string to disable distance measurement. Default value:km
WEBPORT
: Allows choosing a custom port for the included web server. Default value:80
. Note that you will have to expose it through docker with the -p argument
If telemetry is enabled, a stats page will be available at http://your.server/results/stats.php
, but a password must be specified.
Default DB driver is sqlite. The DB file is written to /database/db.sql
.
So if you want your data to be persisted over image updates, you have to mount a volume with -v $PWD/db-dir:/database
.
This command starts LibreSpeed in standalone mode, with the default settings, on port 80:
docker run -e MODE=standalone -p 80:80 -it ghcr.io/librespeed/speedtest
This command starts LibreSpeed in standalone mode, with telemetry, ID obfuscation and a stats password, on port 86:
docker run -e MODE=standalone -e TELEMETRY=true -e ENABLE_ID_OBFUSCATION=true -e PASSWORD="yourPasswordHere" -e WEBPORT=86 -p 86:86 -v $PWD/db-dir/:/database -it ghcr.io/librespeed/speedtest
For multiple servers, you need to set up 1+ LibreSpeed backends, and 1 LibreSpeed frontend.
In backend mode, LibreSpeed provides only a test point with no UI. To do this, set the MODE
environment variable to backend
.
The following backend files can be accessed on port 80: garbage.php
, empty.php
, getIP.php
Here's a list of additional environment variables available in this mode:
IPINFO_APIKEY
: API key for ipinfo.io. Optional, but required if you expect to serve a large number of tests
This command starts LibreSpeed in backend mode, with the default settings, on port 80:
docker run -e MODE=backend -p 80:80 -it ghcr.io/librespeed/speedtest
In frontend mode, LibreSpeed serves clients the Web UI and a list of servers. To do this:
- Set the
MODE
environment variable tofrontend
- Create a servers.json file with your test points. The syntax is the following:
Note: if a server only supports HTTP or HTTPS, specify the protocol in the server field. If it supports both, just use
[ { "name": "Friendly name for Server 1", "server" :"//server1.mydomain.com/", "dlURL" :"garbage.php", "ulURL" :"empty.php", "pingURL" :"empty.php", "getIpURL" :"getIP.php" }, { "name": "Friendly name for Server 2", "server" :"https://server2.mydomain.com/", "dlURL" :"garbage.php", "ulURL" :"empty.php", "pingURL" :"empty.php", "getIpURL" :"getIP.php" }, ...more servers... ]
//
. - Mount this file to
/servers.json
in the container (example at the end of this file)
The test can be accessed on port 80.
Here's a list of additional environment variables available in this mode:
TITLE
: Title of your speedtest. Default value:LibreSpeed
TELEMETRY
: Whether to enable telemetry or not. Default value:false
ENABLE_ID_OBFUSCATION
: When set to true with telemetry enabled, test IDs are obfuscated, to avoid exposing the database internal sequential IDs. Default value:false
REDACT_IP_ADDRESSES
: When set to true with telemetry enabled, IP addresses and hostnames are redacted from the collected telemetry, for better privacy. Default value:false
PASSWORD
: Password to access the stats page. If not set, stats page will not allow accesses.EMAIL
: Email address for GDPR requests. Must be specified when telemetry is enabled.DISABLE_IPINFO
: If set to true, ISP info and distance will not be fetched from ipinfo.io. Default: value:false
DISTANCE
: WhenDISABLE_IPINFO
is set to false, this specifies how the distance from the server is measured. Can be eitherkm
for kilometers,mi
for miles, or an empty string to disable distance measurement. Default value:km
WEBPORT
: Allows choosing a custom port for the included web server. Default value:80
This command starts LibreSpeed in frontend mode, with a given servers.json
file, and with telemetry, ID obfuscation, and a stats password:
docker run -e MODE=frontend -e TELEMETRY=true -e ENABLE_ID_OBFUSCATION=true -e PASSWORD="yourPasswordHere" -v $(pwd)/servers.json:/servers.json -p 80:80 -it ghcr.io/librespeed/speedtest
In dual mode, LibreSpeed operates as a standalone server that can also connect to other test points. To do this:
- Set the
MODE
environment variable todual
- Follow the
servers.json
instructions for the frontend mode - The first server entry should be the local server, using the server endpoint address that a client can access.