[CI] Add workflow to synchronize ubuntu base image

[hlts2]

Description

Sometimes we have docker rate limit issues when building locally.
When that problem occurs, I have implemented a way to build using ghcr's base image.

Related Issue

Versions

• Go Version: 1.22.3
• Rust Version: 1.77.2
• Docker Version: 20.10.8
• Kubernetes Version: v1.30.0
• NGT Version: 2.2.1

Checklist

• I have read the CONTRIBUTING document and completed our CLA agreement.
• I have checked open Pull Requests for the similar feature or fixes?

Special notes for your reviewer

Summary by CodeRabbit

• New Features

  • Introduced a GitHub Actions workflow for automated Docker image builds.
  • Added Dockerfile support for building custom Ubuntu-based images.

• Chores

  • Updated Makefile with new Docker-related targets and variables for enhanced container management.

[coderabbitai]

Warning

Rate limit exceeded

@hlts2 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 0 minutes and 54 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 0a6576f and d7365c0.

Walkthrough

Walkthrough

This update introduces a new GitHub Actions workflow for building a Docker image named buildbase, along with new Dockerfiles and Makefile adjustments to facilitate this process. The workflow is configured to trigger on pushes and pull requests, and it supports multiple platforms. The Makefile and related scripts now include targets for building and naming Docker containers, enhancing the project's CI/CD capabilities with refined Docker functionalities.

Changes

File	Summary of Changes
.github/workflows/dockers-buildbase-image.yml	Added a new GitHub Actions workflow for building the buildbase Docker image, with triggers for various Git events.
Makefile	Introduced a new variable BUILDBASE_IMAGE and enhanced Docker-related functionality.
Makefile.d/docker.mk	Added new phony targets for building and naming buildbase and ci containers.
dockers/ubuntu/Dockerfile	New Dockerfile setting Ubuntu as the base image with licensing information.
dockers/base/Dockerfile	New Dockerfile specifying ubuntu:devel as the base image for target platforms.
dockers/buildbase/Dockerfile	New Dockerfile defining a build stage using an Ubuntu image, with relevant licensing details.

---

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.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

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.

[vdaas-ci]

[CHATOPS:HELP] ChatOps commands.

• 🙆‍♀️ /approve - approve
• 🍱 /format - format codes and add licenses
• ✅ /gen-test - generate test codes
• 🏷️ /label - add labels
• 🔚 2️⃣ 🔚 /label actions/e2e-deploy - run E2E deploy & integration test

[cloudflare-workers-and-pages]

Deploying vald with    Cloudflare Pages

Latest commit:	d7365c0
Status:	✅  Deploy successful!
Preview URL:	https://b5c65540.vald.pages.dev
Branch Preview URL:	https://fix-ci-sync-ubuntu-devel-ima.vald.pages.dev

View logs

[coderabbitai]

Actionable comments posted: 1

Outside diff range, codebase verification and nitpick comments (1)

.github/workflows/dockers-image-sync.yaml (1)

21-23: Review concurrency settings.

The concurrency group expression works correctly for pull request events but fails for push events to the main branch. The expression does not evaluate correctly, resulting in an incorrect group string.

• File: .github/workflows/dockers-image-sync.yaml
• Lines: 21-23

Please review and correct the expression for push events to the main branch.

Analysis chain

Review concurrency settings.

The concurrency settings are designed to prevent duplicate runs, which is a good practice. However, verify that the expression used for the group key is correct and effective in all scenarios, especially in non-pull request events.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the correctness of the concurrency group expression.

# Test: Check the expression logic by simulating different GitHub event contexts.
echo "Simulating pull request event:"
echo "group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref != 'refs/heads/main' && github.ref || github.sha }}-${{ github.event_name }}"

echo "Simulating push event to main branch:"
echo "group: ${{ github.workflow }}-${{ github.ref != 'refs/heads/main' && github.ref || github.sha }}-${{ github.event_name }}"

Length of output: 567

---

Script:

#!/bin/bash
# Description: Verify the correctness of the concurrency group expression by simulating GitHub Actions environment.

# Simulate GitHub Actions environment variables for a pull request event
GITHUB_WORKFLOW="test-workflow"
GITHUB_EVENT_PULL_REQUEST_NUMBER="123"
GITHUB_REF="refs/pull/123/merge"
GITHUB_SHA="abcdef123456"
GITHUB_EVENT_NAME="pull_request"

echo "Simulating pull request event:"
group=$(echo "${GITHUB_WORKFLOW}-${GITHUB_EVENT_PULL_REQUEST_NUMBER:-${GITHUB_REF} != 'refs/heads/main' && ${GITHUB_REF} || ${GITHUB_SHA}}-${GITHUB_EVENT_NAME}")
echo "group: $group"

# Simulate GitHub Actions environment variables for a push event to the main branch
GITHUB_REF="refs/heads/main"
GITHUB_SHA="abcdef123456"
GITHUB_EVENT_NAME="push"

echo "Simulating push event to main branch:"
group=$(echo "${GITHUB_WORKFLOW}-${GITHUB_REF} != 'refs/heads/main' && ${GITHUB_REF} || ${GITHUB_SHA}-${GITHUB_EVENT_NAME}")
echo "group: $group"

Length of output: 986

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a9a9a2f and deea187.

Files selected for processing (1)

• .github/workflows/dockers-image-sync.yaml (1 hunks)

Additional comments not posted (2)

.github/workflows/dockers-image-sync.yaml (2)

16-20: Confirm the trigger configuration.

The workflow is configured to trigger on pull requests and run daily at 1 AM. Ensure this aligns with the project's needs for image synchronization frequency and trigger conditions.

---

47-59: Secure Docker logins.

The workflow logs into DockerHub and GitHub Container Registry using secrets, which is secure. However, ensure that these secrets are properly managed and rotated regularly to maintain security.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between deea187 and 869d0a5.

Files selected for processing (1)

• .github/workflows/dockers-image-sync.yaml (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/dockers-image-sync.yaml

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 869d0a5 and 48706c8.

Files selected for processing (1)

• .github/workflows/dockers-image-sync.yaml (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/dockers-image-sync.yaml

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 48706c8 and 300b9fd.

Files selected for processing (1)

• .github/workflows/dockers-image-sync.yaml (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/dockers-image-sync.yaml

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 300b9fd and 3eac5a2.

Files selected for processing (1)

• .github/workflows/dockers-image-sync.yaml (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/dockers-image-sync.yaml

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3eac5a2 and b2943d2.

Files selected for processing (1)

• .github/workflows/dockers-image-sync.yaml (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/dockers-image-sync.yaml

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b2943d2 and 957c5a0.

Files selected for processing (1)

• .github/workflows/dockers-image-sync.yaml (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/dockers-image-sync.yaml

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 60e79da and 0a6576f.

Files selected for processing (1)

• .github/workflows/dockers-buildbase-image.yml (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/dockers-buildbase-image.yml

[hlts2]

@coderabbitai review

[coderabbitai]

Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.