OKD-322: Update Dockerfile to work on CentOS/RHEL 10

[jatinsu]

Starting with version OKD version 4.22, we are attempting to use CentOS 10 base images. The builder fails to build on CentOS 10 since runc isn't a available package on CentOS 10. For more context this is the build log (Red Hat VPN required to view the build log)

[openshift-ci-robot]

@jatinsu: This pull request references OKD-322 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Starting with version OKD version 4.22, we are attempting to use CentOS 10 base images. The builder fails to build on CentOS 10 since runc isn't a available package on CentOS 10. For more context this is the build log (Red Hat VPN required to view the build log)

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jatinsu
Once this PR has been reviewed and has the lgtm label, please assign bparees for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[jatinsu]

/retest-required

[openshift-ci]

@jatinsu: 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/security	0f3110b	link	false	/test security

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.