-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-arch build #1
Conversation
WalkthroughThis pull request introduces several changes, including the addition of a new Changes
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (4)
.github/workflows/multiarch-build.yaml (4)
3-9
: Optimize workflow triggers and fix schedule comment
- The workflow currently runs on all branches which could consume unnecessary GitHub Actions minutes. Consider limiting it to specific branches.
- The schedule comment mentions 5:30 but the cron expression shows 7:30 UTC.
on: push: branches: - - '**' + - 'master' + - 'develop' schedule: - # Every month's 2nd on 5:30 + # Every month's 2nd at 7:30 UTC - cron: '30 7 2 * *'🧰 Tools
🪛 yamllint
[error] 3-3: trailing spaces
(trailing-spaces)
[warning] 9-9: wrong indentation: expected 4 but found 2
(indentation)
18-21
: Enhance apt-get installation reliabilityThe package installation could be more robust by adding error handling and best practices.
- name: Install qemu dependency run: | - sudo apt-get update - sudo apt-get install -y qemu-user-static + sudo apt-get update && \ + DEBIAN_FRONTEND=noninteractive sudo apt-get install -y \ + qemu-user-static \ + --no-install-recommends && \ + sudo apt-get clean && \ + sudo rm -rf /var/lib/apt/lists/*
31-40
: Add error handling for push stepConsider adding error handling and retries for the push step to handle temporary registry issues.
- name: Push To quay.io id: push-to-quay uses: redhat-actions/push-to-registry@v2 if: github.ref == 'refs/heads/master' + continue-on-error: true + max-attempts: 3 with: image: ${{ steps.build-image.outputs.image }} tags: ${{ steps.build-image.outputs.tags }} registry: quay.io/wavesoftware username: ${{ secrets.QUAY_USER }} password: ${{ secrets.QUAY_PASSWORD }} +🧰 Tools
🪛 yamllint
[error] 40-40: no new line character at the end of file
(new-line-at-end-of-file)
1-40
: Fix YAML formatting issuesThe following formatting issues were detected:
- Remove trailing spaces
- Fix indentation (should be 4 spaces)
- Add newline at end of file
-name: Multiarch build +name: Multiarch build -on: +on: push: branches: - '**' schedule: - # Every month's 2nd on 5:30 - - cron: '30 7 2 * *' + # Every month's 2nd on 5:30 + - cron: '30 7 2 * *' jobs: multiarch-build: name: Build images runs-on: ubuntu-22.04 steps: - uses: actions/checkout@v4 # ... rest of file ... password: ${{ secrets.QUAY_PASSWORD }} +🧰 Tools
🪛 yamllint
[error] 3-3: trailing spaces
(trailing-spaces)
[warning] 9-9: wrong indentation: expected 4 but found 2
(indentation)
[error] 40-40: no new line character at the end of file
(new-line-at-end-of-file)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (4)
.editorconfig
(1 hunks).github/workflows/multiarch-build.yaml
(1 hunks)Containerfile
(1 hunks)README.md
(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- .editorconfig
🧰 Additional context used
🪛 yamllint
.github/workflows/multiarch-build.yaml
[error] 3-3: trailing spaces
(trailing-spaces)
[warning] 9-9: wrong indentation: expected 4 but found 2
(indentation)
[error] 40-40: no new line character at the end of file
(new-line-at-end-of-file)
🪛 Markdownlint
README.md
11-11: Expected: h2; Actual: h3
Heading levels should only increment by one level at a time
(MD001, heading-increment)
7-7: Expected: 0; Actual: 1
Unordered list indentation
(MD007, ul-indent)
8-8: Expected: 0; Actual: 1
Unordered list indentation
(MD007, ul-indent)
9-9: Expected: 0; Actual: 1
Unordered list indentation
(MD007, ul-indent)
14-14: null
Dollar signs used before commands without showing output
(MD014, commands-show-output)
11-11: Punctuation: ':'
Trailing punctuation in heading
(MD026, no-trailing-punctuation)
🔇 Additional comments (2)
Containerfile (2)
5-7
: LGTM on package installation practices
The installation follows container best practices:
- Uses --no-install-recommends to minimize image size
- Properly cleans up apt cache
- Combines RUN commands to reduce layers
5-5
: Consider security implications of ImageMagick installation
While the installation looks correct, ImageMagick requires additional security considerations:
- Consider restricting ImageMagick's capabilities through a custom policy.xml
- Consider pinning the version for better reproducibility and security tracking
Let's verify the ImageMagick installation across architectures and check its current version:
Summary by CodeRabbit
New Features
.editorconfig
file to enforce coding style guidelines.Containerfile
to includeimagemagick
installation.README.md
with a new section for pulling the Docker image and updated badges.Documentation
README.md
file.