🐋 LinuxServer.io Docker image now available!

[alexjustesen]

🐋 LinuxServer image now available!

I recently wrapped up testing (#837) with @thespad and the fantastic people over at @linuxserver have published their Speedtest Tracker image!

There are a bunch of benefits to the new image but the highlights are:

1. 3-4x faster page loads, depending on the host device.
2. The image is HALF the size, down from ~298MB to ~154MB. This is largely due to a switch to an Alpine Linux base from Ubuntu.
3. Directory and file permissions are now set correctly, this means I'm bringing back sqlite as the default database on new installs.
4. Less on my plate allowing me to spend more time on core application features.

🖼️ Using the new image

Most importantly the new image is a drop-in replacement to the old one. To switch all you have to do is replace the image:

image: lscr.io/linuxserver/speedtest-tracker:latest

or with a specific version:

image: lscr.io/linuxserver/speedtest-tracker:0.20.0

Further image documentation and supported architectures can be found on their GitHub repo.

🧪 Verified running on

My home lab is limited but verified working on the following systems:

• Synology NAS (DS920+)
• Unraid NAS (using the template)
• RPI 4b+ Docker Swarm node

📃 To-dos

I have some outstanding tasks that I still need to do, below is a list that'll get checked off over time as I roll through the rest of the updates.

• Update the docs
• Revert back to sqlite as the default database for new installs
• Revert back to file as the default cache driver for new installs Keeping database as the default cache driver as this aligns with Laravel 11 standard.
• Update the Unraid plugin template lsio added theirs to Unraid CA
• Add notification to admin panel to update the image #1379
• Stop building my own image

[mmomjian]

@alexjustesen when using the LSIO Docker container, I get the following error:

[2024-02-19 17:37:16] production.ERROR: SQLSTATE[08006] [7] connection to server at "postgres.domain" (100.64.x.x), port 5430 failed: could not open certificate file "/root/.postgresql/postgresql.crt": Permission denied

Are you able to confirm that this isn't due to a recent change in the underlying image, and if so, is there a way to specify sslmode=no-verify to allow an SSL connection without certificates? Unsure if this should be directed to this project or the LSIO image.

The directory /root/.postgresql doesn't exist in either Docker image as far as I can tell.

[thespad]

Not tested but you should be able to set it with DB_SSLMODE, that said it looks like the deault is already prefer which shouldn't try and verify the certs.

[mmomjian]

I just tried DB_SSLMODE=require and DB_SSLMODE=no-verify, same issue. I opened an issue on the LSIO repo as well with more details at link. Cheers!

[mmomjian]

@alexjustesen @thespad the LSIO image has a new key path due to the (much appreciated) switch to Nginx and faster HTTP response. Perhaps this can be documented somewhere? I can already tell that the Web UI is much faster to respond!

/etc/ssl/web/ssl.crt -> /config/keys/cert.crt

/etc/ssl/web/ssl.key -> /config/keys/cert.key

The solution for the Postgres SSL error is to specify HOME=/config in Docker compose.

[luckman212]

Is SQLite the default already in the latest LSCR image? I am planning to rebuild my container today since 0.16 made a mess of things and I don't feel like fixing database issues.

If SQLite isn't the default yet, what's the easiest way to roll out a new container based on this with a SQLite backend?

[alexjustesen]

Is SQLite the default already in the latest LSCR image? I am planning to rebuild my container today since 0.16 made a mess of things and I don't feel like fixing database issues.

If SQLite isn't the default yet, what's the easiest way to roll out a new container based on this with a SQLite backend?

Not yet, but I did update the docs for setting sqlite as your database.

Only DB_ variable you need is DB_CONNECTION and set it to sqlite and then follow the install steps for creating the DB file.

[thespad]

sqlite is the default in so much as it's in our example compose/run because it's the simplest to set up (and it's what our CI tests use).

So if you just copy/paste them as-is you'll get sqlite.

[alexjustesen]

sqlite is the default in so much as it's in our example compose/run because it's the simplest to set up (and it's what our CI tests use).

So if you just copy/paste them as-is you'll get sqlite.

He's probably talking about https://docs.speedtest-tracker.dev/getting-started/installation/installation, which I can't update because GitBook is throwing an error when adding a new tab 🤦‍♂️