Skip to content
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

OCPBUILD-174: Clean Up Containerfiles #414

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

adambkaplan
Copy link
Contributor

Remove previous "dev"/rhel7 Dockerfiles, and replace them with an equivalent Containerfile based on ubi9. The Containerfile uses the suffix .ubi as opposed to a specific UBI/RHEL version number to support future upgrades to ubi10 and beyond. The Containerfile uses UBI images from registry.access.redhat.com, which does not require a pull secret. This makes it easy for any contributor to pick up and build.

Created a separate Containerfile for OCP builds (.ocp), copying the current contents of Dockerfile.rhel8. This Containerfile uses images from the OpenShift CI system, which are only available to Red Hat employees. The .rhel8 suffix was removed because it is a source of confusion for new contributors; OCP is currently based on RHEL9 images, and will switch to ubi10 at some point in the future.

Remove previous "dev"/rhel7 Dockerfiles, and replace them with an
equivalent `Containerfile` based on ubi9. The `Containerfile` uses the
suffix `.ubi` as opposed to a specific UBI/RHEL version number to
support future upgrades to ubi10 and beyond. The Containerfile uses UBI
images from `registry.access.redhat.com`, which does not require a pull
secret. This makes it easy for any contributor to pick up and build.

Created a separate Containerfile for OCP builds (`.ocp`), copying the
current contents of `Dockerfile.rhel8`. This `Containerfile` uses
images from the OpenShift CI system, which are only available to Red
Hat employees. The `.rhel8` suffix was removed because it is a source
of confusion for new contributors; OCP is currently based on RHEL9
images, and will switch to ubi10 at some point in the future.

Signed-off-by: Adam Kaplan <[email protected]>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 6, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 6, 2024

@adambkaplan: This pull request references OCPBUILD-174 which is a valid jira issue.

In response to this:

Remove previous "dev"/rhel7 Dockerfiles, and replace them with an equivalent Containerfile based on ubi9. The Containerfile uses the suffix .ubi as opposed to a specific UBI/RHEL version number to support future upgrades to ubi10 and beyond. The Containerfile uses UBI images from registry.access.redhat.com, which does not require a pull secret. This makes it easy for any contributor to pick up and build.

Created a separate Containerfile for OCP builds (.ocp), copying the current contents of Dockerfile.rhel8. This Containerfile uses images from the OpenShift CI system, which are only available to Red Hat employees. The .rhel8 suffix was removed because it is a source of confusion for new contributors; OCP is currently based on RHEL9 images, and will switch to ubi10 at some point in the future.

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.

Copy link
Contributor

openshift-ci bot commented Dec 6, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 6, 2024
The `tree` package is not available in UBI's default package repos
(BaseOS, AppStream). This package was added explicitly in OCP 3.10,
as a means of ensuring that all OCP images declared their package
dependencies up front, versus inheriting them from a common base image.
Prior to this change in openshift/origin [1], the `builder` image was
based off of a common "control plane" image, which probably had package
dependencies that are not relevant to container image builds.

It does not appear that `tree` is needed by this container image or its
dependencies (s2i, buildah). Removing it reduces skew between the `ubi`
image for local development, and the `ocp` image for CI and release.

[1] openshift/origin@4333db3

Signed-off-by: Adam Kaplan <[email protected]>
@adambkaplan
Copy link
Contributor Author

/retest

Unit test should pass now that #412 merged.

Copy link
Contributor

openshift-ci bot commented Dec 13, 2024

@adambkaplan: The following tests 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/e2e-aws-ovn-proxy 927b1da link false /test e2e-aws-ovn-proxy
ci/prow/okd-scos-e2e-aws-ovn 927b1da link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-builds-techpreview 927b1da link false /test e2e-aws-ovn-builds-techpreview
ci/prow/security 927b1da link false /test security
ci/prow/e2e-aws-ovn-builds 927b1da link true /test e2e-aws-ovn-builds

Full PR test history. Your PR dashboard.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants