test(integration): Update busybox and alpine:3 to use the mirror to avoid docker rate hub limit errors

[menahyouyeah]

Fixes: #nnn
Related: Relevant tracking issues, for context
Merge before/after: Dependent or prerequisite PRs

Description
Update busybox and alpine:3 to use the mirror to avoid docker rate hub limit errors

[gemini-code-assist]

Summary of Changes

Hello @menahyouyeah, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the reliability of integration tests and examples by modifying their Dockerfiles to pull alpine:3 and busybox base images from mirror.gcr.io/library/ instead of directly from Docker Hub. This strategic shift is intended to circumvent Docker Hub's rate limiting, thereby preventing build failures and ensuring consistent performance for image acquisition within the development and testing workflows.

Highlights

• Docker Image Mirroring: Updated numerous Dockerfiles across integration tests and examples to use mirror.gcr.io/library/ for alpine:3 and busybox base images.
• Rate Limit Mitigation: This change directly addresses and aims to prevent Docker Hub rate limit errors that can occur during image pulls, ensuring more reliable builds.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates numerous Dockerfiles to use a GCR mirror for alpine and busybox base images, which is a great move to avoid Docker Hub rate limits and improve CI stability. The changes are consistent and correct across all files. I've added a couple of suggestions to further improve build reproducibility by pinning the base image versions to specific tags instead of floating ones. Overall, this is a solid and necessary change.

[gemini-code-assist]

For better reproducibility of builds, it's a good practice to pin the base image to a specific version instead of using a floating tag like :3. This prevents unexpected changes or breakages when a new version is released under the 3 tag. I'd suggest using a more specific version, for example 3.18. This comment applies to all other Dockerfiles in this PR that use alpine:3.

FROM mirror.gcr.io/library/alpine:3.18

[gemini-code-assist]

To ensure reproducible builds, it's recommended to pin the busybox image to a specific version instead of relying on the implicit latest tag. This will prevent your builds from breaking unexpectedly when a new latest is pushed. I'd suggest using a specific tag, for example 1.36. This comment applies to all other Dockerfiles in this PR that use busybox.

FROM mirror.gcr.io/library/busybox:1.36 as builder