Fix unavailable image references (#42)

[joshdev8]

Problem

A fresh docker compose up -d fails because four services reference images that don't exist in any registry. docker compose config still passes (it only validates syntax/interpolation, not image availability), so the pre-flight check in the issue template gives a false green. Reported in #42.

Verification

Checked each against its registry (Docker Hub public API / GHCR):

Current (404 — never existed)	Fix (verified live)
watchlistarr/watchlistarr	nylonee/watchlistarr
cleanarr/cleanarr	selexin/cleanarr
requestrr/requestrr	thomst08/requestrr
ghcr.io/aetaric/checkrr:latest	ghcr.io/aetaric/checkrr:latest-amd64

All three Docker Hub replacements have a latest tag, consistent with the untagged/latest convention the rest of the stack uses (so Watchtower keeps them current).

checkrr note: it publishes no multi-arch manifest — every tag is architecture-suffixed, which is the actual reason bare :latest 404s. Pinned to latest-amd64 with a comment telling arm64 users to swap to latest-arm64v8.

Testing

docker compose config -q parses OK and config --images now resolves all four to the corrected references.

Fixes #42

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated container image sources for Watchlistarr, Cleanarr, and Requestrr.
  • Switched Checkrr to its AMD64-specific latest image tag.
  • Added documentation clarifying Checkrr image tagging behavior.

[coderabbitai]

📝 Walkthrough

Walkthrough

Docker Compose image references were updated for Watchlistarr, Checkrr, Cleanarr, and Requestrr. Checkrr now uses the latest-amd64 tag with inline tagging documentation.

Changes

Container image availability

Layer / File(s)	Summary
Update service image references docker-compose.yml	Watchlistarr, Cleanarr, and Requestrr now use alternate image repositories, while Checkrr uses ghcr.io/aetaric/checkrr:latest-amd64 with comments explaining its architecture-specific tagging.

Estimated code review effort: 1 (Trivial) | ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: fixing unavailable Docker image references.
Linked Issues check	✅ Passed	The PR updates the four unavailable image references called out in #42, matching the issue's goal of making the compose stack start.
Out of Scope Changes check	✅ Passed	The changes stay within scope by adjusting image tags and adding a related note, with no unrelated service or config edits.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/dead-images

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

docker-compose.yml (1)

333-338: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Make the Checkrr architecture tag configurable.

The default remains hard-coded to latest-amd64, so ARM64 users must edit the tracked compose file before docker compose up -d works. Prefer an environment override with the amd64 tag as the default.

Suggested change

-    image: ghcr.io/aetaric/checkrr:latest-amd64
+    image: ghcr.io/aetaric/checkrr:${CHECKRR_IMAGE_TAG:-latest-amd64}

Document CHECKRR_IMAGE_TAG=latest-arm64v8 for ARM64 deployments.

🤖 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 `@docker-compose.yml` around lines 333 - 338, Update the Checkrr image
reference in the checkrr service to support environment substitution, defaulting
to latest-amd64 when CHECKRR_IMAGE_TAG is unset. Document
CHECKRR_IMAGE_TAG=latest-arm64v8 for ARM64 deployments without changing the
default behavior.

🤖 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.

Nitpick comments:
In `@docker-compose.yml`:
- Around line 333-338: Update the Checkrr image reference in the checkrr service
to support environment substitution, defaulting to latest-amd64 when
CHECKRR_IMAGE_TAG is unset. Document CHECKRR_IMAGE_TAG=latest-arm64v8 for ARM64
deployments without changing the default behavior.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6a83b88f-51fa-4101-b0d6-c4e814e25c5d

📥 Commits

Reviewing files that changed from the base of the PR and between 9e5f15b and 784a0fb.

📒 Files selected for processing (1)

• docker-compose.yml

[joshdev8]

Addressed this in a follow-up PR (#46) since this one was already merged. checkrr's tag is now ${CHECKRR_IMAGE_TAG:-latest-amd64}, so arm64 users set CHECKRR_IMAGE_TAG=latest-arm64v8 in .env instead of editing the tracked compose file — consistent with how GRAFANA_PORT/LOCAL_NETWORK already work. Default is unchanged.