Skip to content

[Speedtest] Fix image repository path in docker-compose.yml #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
finallyjay merged 1 commit into from
Jun 10, 2026
Merged

[Speedtest] Fix image repository path in docker-compose.yml #29

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion speedtest/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
services:
speedtest:
image: lscr.io/linuxserver/speedtest-tracker:latest
image: linuxserver/speedtest-tracker:latest

@coderabbitai coderabbitai Bot Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

LinuxServer.io official recommendation for Docker image registry lscr.io vs Docker Hub 2026

💡 Result:

As of June 2026, LinuxServer.io recommends the use of lscr.io for pulling their container images [1][2]. What is lscr.io lscr.io is not a traditional container registry itself but rather a load-balancer, vanity URL, and telemetry platform provided in collaboration with Scarf [1][2][3]. It acts as a gateway that transparently redirects pull requests to their primary backend registry, which is currently the GitHub Container Registry (ghcr.io) [1][3]. Why LinuxServer.io recommends lscr.io LinuxServer.io encourages users to switch to lscr.io for several technical and operational reasons: Future-proofing: Because lscr.io is a redirection service, LinuxServer.io can change their underlying backend registry (e.g., from GHCR to another provider) without requiring users to update their docker-compose files or run commands [1]. Improved Analytics: The platform provides centralized, accurate telemetry on image usage. This data helps the project maintainers better understand which images and tags are popular, allowing them to focus their engineering efforts more effectively compared to the fragmented data provided by platforms like Docker Hub or GHCR [1][3]. Standardization: It serves as the primary, consistent registry name used across all their official documentation, sample Docker CLI commands, and compose files [2][3]. Relationship with Docker Hub and other registries LinuxServer.io continues to push images to multiple registries, including Docker Hub and GitHub Container Registry (GHCR) [4]. While they recommend lscr.io for its flexibility and analytics, they do not plan to deprecate direct access to Docker Hub or GHCR [4]. You can continue to use those registries directly if you prefer, as they will remain functional [1]. Important Considerations: Blocklists: Because lscr.io gathers usage metrics via Scarf, some overzealous privacy-focused blocklists may block it [3]. If you experience connection issues (e.g., "no such host" errors), you may need to allowlist gateway.scarf.sh in your network security software [3]. Consistency: If you are using their documentation, you will find lscr.io consistently promoted as the standard path for deploying their containers [2][3].

Citations:

Use lscr.io for LinuxServer images (avoid switching to Docker Hub without rationale)

In speedtest/docker-compose.yml the image at line 3 was changed from lscr.io/linuxserver/speedtest-tracker:latest to linuxserver/speedtest-tracker:latest. LinuxServer.io’s current guidance recommends using lscr.io as the standard/published pull path (gateway/future-proofing/consistency), so this change moves away from their recommended practice.

  • If Docker Hub is intentional, document the registry strategy and ensure rate-limit mitigation (e.g., Docker Hub auth / reduced pull frequency).
  • Otherwise, revert to lscr.io/linuxserver/speedtest-tracker:latest.
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@speedtest/docker-compose.yml` at line 3, The docker-compose image line was
changed to use Docker Hub; restore the LinuxServer canonical registry by
reverting the image value "image: linuxserver/speedtest-tracker:latest" back to
"image: lscr.io/linuxserver/speedtest-tracker:latest" unless using Docker Hub is
intentional—if intentional, add documentation on the registry decision and
include Docker Hub rate-limit mitigation (auth or reduced pulls) in the repo
documentation or compose configuration.

container_name: speedtest
hostname: speedtest
restart: unless-stopped
Expand Down