How to Install Speedtest Tracker on CasaOS Today

The 2023 CasaOS Speedtest Tracker discussion is outdated at the container-image level. The old thread debated henrywhitaker3/speedtest-tracker tags, but the maintained project now uses the LinuxServer.io image lscr.io/linuxserver/speedtest-tracker:latest.

If you are installing Speedtest Tracker on CasaOS or another Docker host today, use the current project documentation rather than reproducing the old latest versus dev workaround. The current image expects persistent configuration and an APP_KEY, and it supports scheduled tests directly.

What Changed Since the Original CasaOS Tutorial?

The original forum discussion is valuable because it captures the use case: automatically recording internet speed can help prove recurring ISP problems. It also correctly warns that scheduled tests consume bandwidth. What aged out is the software packaging.

The maintained Speedtest Tracker Docker Compose guide now uses LinuxServer's image and documents SQLite, MariaDB, MySQL and PostgreSQL options. The LinuxServer image is available for x86-64 and ARM64.

A Current Docker Compose Baseline

services:
  speedtest-tracker:
    image: lscr.io/linuxserver/speedtest-tracker:latest
    container_name: speedtest-tracker
    restart: unless-stopped
    ports:
      - "8080:80"
    environment:
      - PUID=1000
      - PGID=1000
      - APP_KEY=your-generated-key
      - APP_URL=http://your-server:8080
      - DB_CONNECTION=sqlite
    volumes:
      - /path/to/speedtest-tracker/data:/config

Generate and protect the application key as described by the current project. Keep /config on persistent storage so results and settings survive container recreation. If port 8080 is already used, change only the host side of the mapping.

The LinuxServer Speedtest Tracker image documentation also explains PUID/PGID, image updates and the current environment variables.

Scheduled Tests Still Consume Real Bandwidth

A community reply estimated roughly 25–50 MB per test in 2023, but that number should not be treated as a fixed current requirement. A speed test intentionally transfers enough data to measure the connection, so usage changes with provider, link speed, test duration and server selection.

On metered internet, begin with a conservative schedule and measure actual daily usage before increasing frequency. On an always-on low-power home server, the application itself is light; the network tests, not the dashboard, are usually the more important operational cost.

If You Still Run the Old Image

Do not overwrite the old container before locating its persistent data. Export or back up the configuration and database first, then build a clean current deployment and verify historical-data migration separately. Moving from an abandoned image to a maintained image is an application migration, not merely a tag change.

Frequently Asked Question

Does Speedtest Tracker use a lot of internet data?

It can. Each scheduled test sends and receives real traffic to measure throughput. The exact amount is not fixed, so users with data caps should measure their own usage and avoid unnecessarily frequent schedules.