Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1191688

Summary: [RFE] Unable to import images missing the 'repositories' file
Product: [Retired] Pulp Reporter: Brenton Leanhardt <bleanhar>
Component: docker-supportAssignee: pulp-bugs
Status: CLOSED UPSTREAM QA Contact: pulp-qe-list
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.4.0CC: bleanhar, mhrivnak, sdodson
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-19 01:21:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brenton Leanhardt 2015-02-11 18:24:50 UTC
Description of problem:

While pushing OpenShift images to registry.access.redhat.com we noticed that Pulp requires a valid 'repositories' file in the image tar.  It seems with RHEL 7's version of docker that if a save is passed an image ID instead of tag the repositories file will be missing.

In our case we actually prefer to run docker save with an ID to avoid any possible race condition of the tag being updated just before docker save is run.  Could Pulp support this use case?

Comment 1 Michael Hrivnak 2015-02-11 18:54:23 UTC
That sounds reasonable. We initially went with the expectation that an entire repo would be "docker save"d so that tags would be preserved from docker to pulp. As long as you're happy to re-create the tags in pulp, we can certainly do this.

Do you happen to have any idea how "docker save" will work with the new manifest data model? If it changes behavior substantially from what docker does currently, it might make sense to target this RFE for that new format.

Comment 2 Brenton Leanhardt 2015-02-11 19:11:48 UTC
In our case we were planning to recreate the tags in pulp since the environment they came from used tags that didn't follow the formal guidelines for registry.access.redhat.com.

Unfortunately I don't know anything about the new manifest data model.  I'm a developer on the OpenShift team working with release engineering to publish images for the first time. :)

Comment 3 Brian Bouterse 2015-02-19 01:21:36 UTC
Moved to https://pulp.plan.io/issues/290