Bug 1171842 - [RFE] Need a way to remove docker images that are untagged and are not used by other images
Summary: [RFE] Need a way to remove docker images that are untagged and are not used b...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: docker-support
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: pulp-bugs
QA Contact: pulp-qe-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-08 18:03 UTC by David Davis
Modified: 2015-02-28 23:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-19 01:20:42 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 276 0 None None None Never

Description David Davis 2014-12-08 18:03:57 UTC
We have a feature request to support the removal of orphaned docker images (ones that don't have tags or aren't used as layers by other images) in Katello so we'd like a command and API call to remove these images.

http://projects.theforeman.org/issues/7811

Comment 1 Michael Hrivnak 2015-01-06 18:26:56 UTC
Pulp doesn't have API endpoints that implement workflows for specific content types. We might add a command to our CLI to do something like this, but I don't think it makes sense to have it as part of our content-agnostic REST API.

I recommend that katello proceeds with this in the web UI. Looking at any specific repo, it should be straight-forward to identify layers that are not tagged nor referenced by another layer in the repo, and offer to remove them from the repo with the normal unit remove operation.

This whole workflow is subject to change once the v2 registry API and "manifest" concepts are fully integrated into docker.

Comment 2 Brian Bouterse 2015-02-19 01:20:42 UTC
Moved to https://pulp.plan.io/issues/276


Note You need to log in before you can comment on or make changes to this bug.