Bug 1403669

Summary:	Unable to upload custom docker image to the repository in the satellite
Product:	Red Hat Satellite	Reporter:	Giridhar <gkonda>
Component:	Container Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.5	CC:	bbuckingham, mhrivnak
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-13 19:15:03 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:

Description Giridhar 2016-12-12 06:57:40 UTC

Description of problem:
It is possible to upload a custom docker image in the repository in RH satellite 6.1 but it's not available in RH satellite 6.2

Version-Release number of selected component (if applicable):
6.2

How reproducible:
Always

Steps to Reproduce:
1.click on content -> product -> new product -> fill the details and save
2.click on the created product -> create a repository -> fill the details and save
3.click on the created repository and there is an option available to upload custom images into the repository in satellite 6.1 but the same feature isn't available in 6.2

Actual results:
There is no option available to upload the custom docker image

Expected results:
There should be an option available to upload the custom docker images

Additional info:

Comment 1 Michael Hrivnak 2016-12-13 19:15:03 UTC

Thanks for this feedback. At the moment, it is not possible to support upload of v2 content (manifests and blobs), because the "docker save" feature of the docker command has not caught up to the maturity of their v2 API.

In 6.1, we depended on docker's ability to "docker save" v1 content into a tarball. Since v1 content support has been dropped across the ecosystem, Satellite 6.2 also stopped supporting v1 content, and only works with v2 content.

With v2, the discussion is still unsettled about how docker will handle the "save" use case:

https://github.com/docker/distribution/issues/727

So for now, doing a "sync" from another registry is the only way to get docker v2 content into Satellite.