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

Pruning should keep layers referenced by other images #16656

Merged
merged 2 commits into from
Oct 4, 2017

Conversation

dmage
Copy link
Contributor

@dmage dmage commented Oct 3, 2017

legionus and others added 2 commits October 3, 2017 15:40
Layers in images are not unique. If the pruning process does not add
all the images to the graph, it loses information about the links between
these images and layers. So, the layers that still have links can be deleted.

Signed-off-by: Gladkov Alexey <[email protected]>
@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Oct 3, 2017
@dmage dmage added the kind/bug Categorizes issue or PR as related to a bug. label Oct 3, 2017
@bparees
Copy link
Contributor

bparees commented Oct 3, 2017

/lgtm

I've opened the backport bugs for this as well:
https://bugzilla.redhat.com/show_bug.cgi?id=1498123
https://bugzilla.redhat.com/show_bug.cgi?id=1498124

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 3, 2017
@openshift-merge-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees, dmage

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

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 3, 2017
@bparees
Copy link
Contributor

bparees commented Oct 3, 2017

/retest

@openshift-merge-robot
Copy link
Contributor

Automatic merge from submit-queue (batch tested with PRs 16644, 16649, 16656, 16651, 16663).

@openshift-merge-robot openshift-merge-robot merged commit b9adeba into openshift:master Oct 4, 2017
rdoproject pushed a commit to rdo-infra/rdo-container-registry that referenced this pull request Nov 6, 2017
This commits allows to deploy the RDO registry with OpenShift 3.7.

It currently uses the "rdo-test" branch because there is still one unmerged
pull request upstream that hasn't merged yet upstream.

Delta from OpenShift 3.5 that is interesting to us:

- Significant improvements for registry and image pruning see [1][2][3][4]
- docker-registry can now use reencrypt routes [5]
- Metrics and logging were deployed by default in 3.5, this is no longer the
  case in 3.7, avoiding an unnecessary impact on performance. [6]
- We're now deploying a persistent volume for the docker-registry service on
  the local filesystem.

[1]: openshift/origin#13671
[2]: openshift/origin#16717
[3]: openshift/origin#16656
[4]: openshift/origin#17020
[5]: openshift/origin#14249
[6]: openshift/openshift-ansible@660bafe

Change-Id: I5c364a1aab883b6af061051bf190ce857bf2e1f9
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. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. priority/P1 size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants