Bug 2170459

Summary:	[RFE] add docker as content type possibility for RHUI ACS
Product:	Red Hat Satellite	Reporter:	Stefan Nemeth <snemeth>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	dalley, damoore, iballou, ipanova
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Stefan Nemeth 2023-02-16 12:42:51 UTC

Description of problem:

Rhui4 can also host docker images, however alternative content source only supports yum as content type for repositories

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

6.13

How reproducible:

100%

Steps to Reproduce:
1.content -> alternative content soucrces -> add
2.choose rhuui
3.there is only "yum" content type

Actual results:

not possible to choose docker option

Expected results:

have docker option for acs

Additional info:

Comment 1 Brad Buckingham 2023-02-16 13:51:53 UTC

Ian,

Is this supported by Pulp or would changes first need to be made there?

Thanks!

Comment 2 Ian Ballou 2023-02-16 19:18:28 UTC

Hi Brad, this is not yet supported by Pulp and would need support from them first. As such, I'll stick this on the Pulp component.

Comment 3 Daniel Alley 2023-02-23 04:09:05 UTC

I can't really visualize what ACS would look like with a container registry, do you think that sounds plausible Ina?

Comment 4 Ina Panova 2023-02-28 17:21:20 UTC

Well. It is doable but there will be some limitations. File protocol will not work. If we want to re-use things as they are designed today than one would need to create an ACS with no 'paths' and a remote pointing to a valid registry.It means that 'path' will be retrieved from the container remote object ( registry url + upstream-repo fields). As a result of 'refresh' action there will always be created one hidden repo per ACS. If we want to have a similar behavior as in RPM, where one can specify multiple paths( aka hidden repos) in ACS then changes would be needed to the ContainerRemote.