Add Support for ARM64

[ankit16-19]

Description

Enter a meaningful description here of the changes, including any relevant links

Checklist

• Documentation Updated
• sbt scalafmtAll Run (and optionally sbt scalafmtSbt)
• At least one approval from a codeowner

Summary by CodeRabbit

• Refactor
  • Enhanced Docker workflows to improve image building and deployment processes using updated actions and environment variables.
• Chores
  • Updated actions/checkout to version 3 in Docker release workflow for enhanced performance and reliability.

[coderabbitai]

Walkthrough

The recent updates focus on enhancing Docker workflows across multiple YAML files. Key improvements include the introduction of environment variables for better configuration, and the adoption of Docker-specific actions to streamline the processes of setting up QEMU, Buildx, and automating Docker image builds and pushes.

Changes

File Path	Changes Summary
.github/workflows/docker-alpha.yml	Major overhaul including new environment variables and restructuring with Docker-specific actions for setup and deployment.
.github/workflows/docker-beta.yml .github/workflows/release-docker.yml	Added environment variables, updated steps and actions for Docker setup and image processing, including automated builds and pushes.

🐰✨🎉
In the land of code and nightly builds,
A rabbit hopped, pushing updates with glee.
Docker files align, with new scripts so fine,
"Let's celebrate," he chirps, "for our containers are free!"
🚀🐇💻

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 71365e6 and 536659a.

Files selected for processing (3)

• .github/workflows/docker-alpha.yml (1 hunks)
• .github/workflows/docker-beta.yml (1 hunks)
• .github/workflows/release-docker.yml (1 hunks)

Additional comments not posted (12)

.github/workflows/docker-beta.yml (4)

7-10: Ensure that the environment variables APP_NAME, DOCKER_FILE, and DOCKER_PLATFORMS are correctly used in the Docker commands.

---

24-33: The Docker Metadata action setup looks correct. Verify that the tags configuration (type=sha and beta) aligns with the project's Docker image versioning strategy.

---

34-35: The setup for QEMU is crucial for ARM64 emulation. Ensure that the version v2.1.0 of docker/setup-qemu-action supports all required features for ARM64.

---

42-50: The Docker build and push action is configured to use the context and Dockerfile specified in the environment variables. Ensure that the push: true setting is intended for the beta branch, as this will push images to DockerHub.

.github/workflows/docker-alpha.yml (4)

7-10: Ensure that the environment variables APP_NAME, DOCKER_FILE, and DOCKER_PLATFORMS are correctly used in the Docker commands.

---

25-33: The Docker Metadata action setup looks correct. Verify that the tags configuration (type=sha and alpha) aligns with the project's Docker image versioning strategy.

---

35-36: The setup for QEMU is crucial for ARM64 emulation. Ensure that the version v2.1.0 of docker/setup-qemu-action supports all required features for ARM64.

---

43-51: The Docker build and push action is configured to use the context and Dockerfile specified in the environment variables. Ensure that the push: true setting is intended for the alpha branch, as this will push images to DockerHub.

.github/workflows/release-docker.yml (4)

7-10: Ensure that the environment variables APP_NAME, DOCKER_FILE, and DOCKER_PLATFORMS are correctly used in the Docker commands.

---

26-35: The Docker Metadata action setup looks correct. Verify that the tags configuration (type=sha, type=semver,pattern={{version}}, and latest) aligns with the project's Docker image versioning strategy.

---

37-38: The setup for QEMU is crucial for ARM64 emulation. Ensure that the version v2.1.0 of docker/setup-qemu-action supports all required features for ARM64.

---

45-53: The Docker build and push action is configured to use the context and Dockerfile specified in the environment variables. Ensure that the push: true setting is intended for the release branch, as this will push images to DockerHub.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[Misyuk-T]

👏 Awesome work. Looking forward to its completion!

[coderabbitai]

Actionable comments posted: 0

Out of diff range and nitpick comments (3)

.github/workflows/docker-beta.yml (1)

37-41: The Buildx setup is configured with debug flags. Consider if this is appropriate for a production environment, as verbose logging might expose sensitive information.

.github/workflows/docker-alpha.yml (1)

38-41: The Buildx setup is configured with debug flags. Consider if this is appropriate for a production environment, as verbose logging might expose sensitive information.

.github/workflows/release-docker.yml (1)

40-43: The Buildx setup is configured with debug flags. Consider if this is appropriate for a production environment, as verbose logging might expose sensitive information.