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

Use CentOS 7 base for CI images. #347

Merged
merged 2 commits into from
Sep 27, 2018

Conversation

dgoodwin
Copy link
Contributor

Automated Release Tooling recommends basing images on CentOS 7 in their Policies and Standards doc.

Also will be helpful for Hive team as we expect we may need to layer on top of this image and may need some more robust tools than scratch provides.

@openshift-bot openshift-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 27, 2018
@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 27, 2018
@openshift-bot openshift-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 27, 2018
@@ -6,7 +6,7 @@ WORKDIR /go/src/github.com/openshift/installer
COPY . .
RUN hack/build.sh && hack/get-terraform.sh

FROM scratch
FROM centos:7
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is effectively what's happening in production, although it's "whatever the OpenShift base layer is" their and not explicitly "CentOS 7". The image I was building for testing openshift/release#1677 is registry.svc.ci.openshift.org/wking-next-gen-installer/stable:installer in case you want to poke around (I think that is public?). The policy doc has:

Do not ask to have your image based of scratch, busybox, alpine, etc. The request will be denied.

I've dropped an internal comment asking why they forbid scratch, and until then, meh, I'm fine either way ;).

Previously was failing fast due to attempts to write to / as UID 1000,
which will not work.

Instead create /output, change ownership, and use for WORKDIR.
@dgoodwin
Copy link
Contributor Author

@wking added commit to get running as UID 1000 to work. Afraid I was not able to have it compatible with using scratch, COPY'ing /output from the build container ends up owned by root. Docker added COPY with --chown in 1.17 but we don't ship that nor does buildah support it yet. Might be possible in future.

@wking
Copy link
Member

wking commented Sep 27, 2018

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 27, 2018
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

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

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 27, 2018
@openshift-merge-robot openshift-merge-robot merged commit a56116a into openshift:master Sep 27, 2018
@dgoodwin dgoodwin deleted the centos-ci-image branch September 27, 2018 18:12
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. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants