NO-JIRA: hack/build-image.sh: Update Dockerfile reference

[DavidHurta]

The file named Dockerfile was removed in the [1] commit as the file was unused. Update the outdated reference to point at the sole existing Dockerfile file in the repository.

[openshift-ci-robot]

@DavidHurta: This pull request explicitly references no jira issue.

Details

In response to this:

The file named Dockerfile was removed in the [1] commit as the file was unused. Update the outdated reference to point at the sole existing Dockerfile file in the repository.

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

Walkthrough

The build script hack/build-image.sh was modified to use Dockerfile.rhel instead of Dockerfile when invoking the podman build command. All other build parameters, including the image tag and --no-cache flag, remain unchanged.

Changes

Cohort / File(s)	Summary
Build script configuration hack/build-image.sh	Changed podman build invocation to reference Dockerfile.rhel instead of Dockerfile

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between d4cb3b0 and 41f5edb.

📒 Files selected for processing (1)

• hack/build-image.sh (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**

⚙️ CodeRabbit configuration file

-Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity.

Files:

• hack/build-image.sh

🔇 Additional comments (1)

hack/build-image.sh (1)

25-25: Reference update is correct; no dangling references exist.

The change from Dockerfile to Dockerfile.rhel is correct. Dockerfile.rhel is the only Dockerfile in the repository, and no other references to the removed Dockerfile remain in build scripts or related configuration files.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[DavidHurta]

/verified by @DavidHurta

[openshift-ci-robot]

@DavidHurta: This PR has been marked as verified by @DavidHurta.

Details

In response to this:

/verified by @DavidHurta

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

[wking]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DavidHurta, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [DavidHurta,wking]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 8bfba29 and 2 for PR HEAD 41f5edb in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 76ea813 and 1 for PR HEAD 41f5edb in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD d245c43 and 0 for PR HEAD 41f5edb in total

[openshift-ci-robot]

/hold

Revision 41f5edb was retested 3 times: holding

[openshift-ci]

@DavidHurta: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/okd-scos-images	41f5edb	link	true	/test okd-scos-images

Full PR test history. Your PR dashboard.

Details

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