Skip to content

Make checkrr architecture tag configurable via CHECKRR_IMAGE_TAG#46

Merged
joshdev8 merged 1 commit into
mainfrom
fix/checkrr-configurable-tag
Jul 14, 2026
Merged

Make checkrr architecture tag configurable via CHECKRR_IMAGE_TAG#46
joshdev8 merged 1 commit into
mainfrom
fix/checkrr-configurable-tag

Conversation

@joshdev8

Copy link
Copy Markdown
Owner

Context

Follow-up to a CodeRabbit nitpick on #44: checkrr's tag was hard-coded to latest-amd64 (checkrr publishes no multi-arch image), so arm64 users had to edit the tracked docker-compose.yml before docker compose up -d would work.

Change

Make the tag an env override with the amd64 tag as the default:

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

This matches the ${VAR:-default} pattern already used for GRAFANA_PORT and LOCAL_NETWORK. Added CHECKRR_IMAGE_TAG=latest-amd64 to .env.example with a note that arm64 hosts set it to latest-arm64v8. Default behavior is unchanged — amd64 users need to do nothing.

Testing

docker compose config --images verified in three cases:

  • default (.env.example value) → latest-amd64
  • CHECKRR_IMAGE_TAG=latest-arm64v8latest-arm64v8
  • var removed entirely → falls back to latest-amd64

🤖 Generated with Claude Code

checkrr has no multi-arch image, so the tag was hard-coded to
latest-amd64, forcing arm64 users to edit the tracked compose file.
Use ${CHECKRR_IMAGE_TAG:-latest-amd64} instead — matching the
${VAR:-default} pattern already used for GRAFANA_PORT and LOCAL_NETWORK
— and document CHECKRR_IMAGE_TAG=latest-arm64v8 in .env.example for
arm64 deployments. Default behavior is unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@joshdev8, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d39206df-8e74-44b0-8a34-531c6a771922

📥 Commits

Reviewing files that changed from the base of the PR and between b878018 and 18e356b.

📒 Files selected for processing (2)
  • .env.example
  • docker-compose.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/checkrr-configurable-tag

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

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

@joshdev8
joshdev8 merged commit 3508bad into main Jul 14, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant