chore(deps): update registry.redhat.io/ubi9/ubi-minimal docker tag to v9.8-1782366411#235
Conversation
… v9.8-1782366411 Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe Dockerfile runtime stage base image tag was updated to a newer ChangesRuntime base image update
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Dockerfile`:
- Line 32: The runtime base image is pinned to a specific UBI-minimal build tag,
which conflicts with the container policy for Red Hat images. Update the FROM
instruction in the Dockerfile to use a floating
registry.redhat.io/ubi9/ubi-minimal tag instead of the exact versioned tag,
keeping the change limited to the base image reference.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 927c678e-1dd9-4174-8320-d7e5f68a6803
📒 Files selected for processing (1)
Dockerfile
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
openshift/lightspeed-agentic-sandbox(manual)
|
|
||
|
|
||
| FROM registry.redhat.io/ubi9/ubi-minimal:9.8-1782191395 | ||
| FROM registry.redhat.io/ubi9/ubi-minimal:9.8-1782366411 |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
Use a floating Red Hat tag for the runtime base image.
Line 32 pins UBI to a specific build tag, but this repo’s container policy requires floating tags for Red Hat images. Switch to a floating UBI-minimal tag per policy.
As per path instructions: “Red Hat images: use floating tags (Red Hat manages updates)”.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@Dockerfile` at line 32, The runtime base image is pinned to a specific
UBI-minimal build tag, which conflicts with the container policy for Red Hat
images. Update the FROM instruction in the Dockerfile to use a floating
registry.redhat.io/ubi9/ubi-minimal tag instead of the exact versioned tag,
keeping the change limited to the base image reference.
Source: Path instructions
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
1 similar comment
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@red-hat-konflux: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This PR contains the following updates:
9.8-1782191395→9.8-1782366411Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
To execute skipped test pipelines write comment
/ok-to-test.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.