use ghcr image in addon development

[pepijndevos]

The docker hub images seem extremely outdated

Proposed change

Update docker images similar to #2134

Type of change

• Document existing features within Home Assistant
• Document new or changing features which there is an existing pull request elsewhere
• Spelling or grammatical corrections, or rewording for improved clarity
• Changes to the backend of this documentation
• Removed stale or deprecated documentation

Additional information

• This PR fixes or closes issue: fixes #
• Link to relevant existing code or pull request:

Summary by CodeRabbit

• Documentation
  • Updated base image references in add-on testing documentation to use GitHub Container Registry (ghcr.io) instead of Docker Hub
  • Replaced homeassistant base image URLs with corresponding ghcr.io URLs for multiple architectures

[coderabbitai]

📝 Walkthrough

Walkthrough

The documentation for add-ons testing has been updated to reflect a change in the source of base Docker images. The base images are now being referenced from the GitHub Container Registry (ghcr.io) instead of the previous Docker Hub location for Home Assistant. This update ensures that the documentation accurately represents the current image sourcing for different architectures (armhf, aarch64, amd64, and i386).

Changes

File	Change Summary
docs/add-ons/testing.md	Updated base Docker image references from homeassistant/[arch]-base:latest to ghcr.io/home-assistant/[arch]-base:latest for all supported architectures

Note: The changes are consistent across multiple architecture-specific base image references, including the BUILD_FROM build argument.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6a30092 and 3e9422f.

📒 Files selected for processing (1)

• docs/add-ons/testing.md (1 hunks)

🔇 Additional comments (3)

docs/add-ons/testing.md (3)

45-48: LGTM! Base image references updated correctly.

The base image references have been properly updated to use the GitHub Container Registry (ghcr.io) instead of Docker Hub, maintaining support for all architectures (armhf, aarch64, amd64, i386).

---

54-54: LGTM! Build argument example updated consistently.

The build argument example has been updated to use the new ghcr.io image source, maintaining consistency with the base images list above.

---

45-54: Verify image availability and documentation completeness.

Let's verify:

1. That these images exist in the GitHub Container Registry
2. That there are no remaining references to the old Docker Hub images in the documentation

✅ Verification successful

Documentation correctly references GHCR images and all architectures are available

The documentation has been properly updated to reference GitHub Container Registry (GHCR) images for all architectures, and no references to the old Docker Hub images remain. The image paths are correctly formatted as ghcr.io/home-assistant/{arch}-base:latest for all supported architectures (armhf, aarch64, amd64, i386).

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify image availability and documentation completeness

# Check if the images exist in GitHub Container Registry
for arch in armhf aarch64 amd64 i386; do
  echo "Checking ${arch} image..."
  curl -s -o /dev/null -w "%{http_code}" "https://ghcr.io/v2/home-assistant/${arch}-base/tags/list"
done

# Check for any remaining references to Docker Hub images
echo -e "\nChecking for remaining Docker Hub references..."
rg -i "homeassistant/[a-z0-9]+-base"

Length of output: 932

---

Script:

#!/bin/bash
# Check documentation files for any Docker-related content and Docker Hub references
echo "Checking documentation files..."
fd -e md -e mdx -x cat {} \; | grep -i "docker" -B2 -A2

# Check if images exist in Docker Hub (public API)
echo -e "\nChecking Docker Hub images..."
for arch in armhf aarch64 amd64 i386; do
  echo "Checking ${arch} image in Docker Hub..."
  curl -s "https://hub.docker.com/v2/repositories/homeassistant/${arch}-base/tags/"
done

Length of output: 70840

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.