[Speedtest] Fix image repository path in docker-compose.yml#29
Conversation
📝 WalkthroughWalkthroughThe speedtest service Docker image reference in ChangesSpeedtest service image update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
This PR updates the Speedtest Tracker service’s Docker image reference to use the simplified linuxserver/... image name in the speedtest/docker-compose.yml, aligning it with how other services in this repository reference LinuxServer images.
Changes:
- Switched the
speedtestservice image fromlscr.io/linuxserver/speedtest-tracker:latesttolinuxserver/speedtest-tracker:latest.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with 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.
Inline comments:
In `@speedtest/docker-compose.yml`:
- 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.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 33a02553-7268-461d-baad-a79cfdd9089e
📒 Files selected for processing (1)
speedtest/docker-compose.yml
| services: | ||
| speedtest: | ||
| image: lscr.io/linuxserver/speedtest-tracker:latest | ||
| image: linuxserver/speedtest-tracker:latest |
There was a problem hiding this comment.
🧩 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:
- 1: https://www.linuxserver.io/blog/wrap-up-warm-for-the-winter
- 2: https://www.linuxserver.io/blog/docker-tags-so-many-tags-so-little-time
- 3: https://docs.linuxserver.io/FAQ/
- 4: https://discourse.linuxserver.io/t/which-container-registry-to-use-for-docker-pulls/3495
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.
This pull request makes a minor update to the
speedtest/docker-compose.ymlfile, changing the image reference for thespeedtestservice to use a simplified image name.Summary by CodeRabbit