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

Bug 1889865: Avoid duplicate registry binaries across downstream image layers. #535

Conversation

benluddy
Copy link
Contributor

@benluddy benluddy commented Dec 8, 2020

The registry binaries are copied from the build stage to an
intermediate directory because the downstream image builder overwrites
the destination directory when the source is a glob pattern. The
existing COPY and RUN (mv) commands both add a layer to the image, so
a copy of each binary lives in each layer.

To avoid this, symlinks are created from /bin to the intermediate
directory instead of moving the binaries from the intermediate
directory to /bin.

The registry binaries are copied from the build stage to an
intermediate directory because the downstream image builder overwrites
the destination directory when the source is a glob pattern. The
existing COPY and RUN (mv) commands both add a layer to the image, so
a copy of each binary lives in each layer.

To avoid this, symlinks are created from /bin to the intermediate
directory instead of moving the binaries from the intermediate
directory to /bin.
@openshift-ci-robot
Copy link

@benluddy: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Avoid duplicate registry binaries across downstream image layers.

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/test-infra repository.

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy

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 Dec 8, 2020
@benluddy benluddy changed the title Avoid duplicate registry binaries across downstream image layers. Bug 1889865: Avoid duplicate registry binaries across downstream image layers. Dec 8, 2020
@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. label Dec 8, 2020
@openshift-ci-robot
Copy link

@benluddy: This pull request references Bugzilla bug 1889865, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.z) matches configured target release for branch (4.6.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1883560 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1883560 targets the "4.7.0" release, which is one of the valid target releases: 4.7.0
  • bug has dependents

In response to this:

Bug 1889865: Avoid duplicate registry binaries across downstream image layers.

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/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Dec 8, 2020
@exdx
Copy link
Member

exdx commented Dec 9, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 9, 2020
@jwforres jwforres added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jan 27, 2021
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 5b65363 into operator-framework:release-4.6 Jan 28, 2021
@openshift-ci-robot
Copy link

@benluddy: All pull requests linked via external trackers have merged:

Bugzilla bug 1889865 has been moved to the MODIFIED state.

In response to this:

Bug 1889865: Avoid duplicate registry binaries across downstream image layers.

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/test-infra repository.

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. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants