ci: add cache to docker build

[WasinWatt]

Summary by CodeRabbit

• Chores
  • Updated the build pipeline to leverage enhanced caching for Docker operations, streamlining the process and improving overall build efficiency.

[coderabbitai]

Walkthrough

The pull request updates the GitHub Actions workflow in the Docker build process by introducing two new parameters, "cache-from" and "cache-to", within the "Build and push" step of the "opinitd" job. These parameters are configured to use GitHub Actions cache (type=gha) to manage Docker layer caching. The change focuses solely on improving caching for optimized build times, without altering other parts of the workflow or export declarations.

Changes

File(s)	Change Summary
.github/workflows/docker.yml	Added "cache-from" and "cache-to" parameters in the "Build and push" step of the "opinitd" job to cache Docker layers.

Sequence Diagram(s)

sequenceDiagram
    participant GHA as GitHub Actions
    participant Build as Build Step (opinitd)
    participant Cache as GitHub Cache (type=gha)
    participant DockerHub as Docker Registry

    GHA->>Build: Trigger "opinitd" job
    Build->>Cache: Retrieve cached layers (cache-from)
    Build->>DockerHub: Build Docker image using cached layers
    DockerHub-->>Build: Image built response
    Build->>Cache: Push updated layers (cache-to)

Loading

Poem

I'm a rabbit in a code-filled glen,
Caching Docker layers with a hop now and then.
"Cache-from" and "cache-to" make builds sleek and bright,
Carrots of code crunching through day and night.
With a skip and a hop, our workflow's just right! 🐇

---

📜 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 5a0c7d7 and b6df019.

📒 Files selected for processing (1)

• .github/workflows/docker.yml (1 hunks)

🔇 Additional comments (2)

.github/workflows/docker.yml (2)

71-72: Add GitHub Actions Cache for Docker Builds
The new parameters "cache-from: type=gha" and "cache-to: type=gha" have been correctly added to the "Build and push" step. These parameters will enable Docker layer caching using GitHub Actions cache to optimize build times.

---

63-70: Verify Cache Integration with Docker Build Parameters
Ensure that the added caching parameters integrate as expected with the docker/build-push-action@v5. It may be worthwhile to confirm that the caching keys and defaults are appropriate for your build environment. If additional cache configuration (such as cache modes or keys) is needed, consider updating these parameters accordingly.

---

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