Bug 1745889

Summary:	[DOCS] docker.io not usable as a private registry
Product:	OpenShift Online	Reporter:	Brendan Mchugh <bmchugh>
Component:	Documentation	Assignee:	Ashley Hardin <ahardin>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Vikram Goyal <vigoyal>
Severity:	high	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	unspecified
Version:	3.x	CC:	aos-bugs, jokerman
Target Milestone:	---
Target Release:	3.x
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:	2020-01-13 20:57:18 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 Brendan Mchugh 2019-08-27 07:12:07 UTC

Document URL: 
https://docs.openshift.com/online/dev_guide/managing_images.html#allowing-pods-to-reference-images-from-other-secured-registries

Section Number and Name: 
Allowing Pods to Reference Images from Other Secured Registries

Describe the issue: 
A scenario that comes up often is users wanting to use "docker.io" as a private registry, however this no longer works with OpenShift Online due to the following bug which has been CLOSED WONTFIX. [1]

Suggestions for improvement: 
Add a specific note/warning stating that "docker.io" cannot be used as a private registry with OpenShift Online.

Additional information: 
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1561989

Comment 3 Ashley Hardin 2020-01-06 21:10:35 UTC

WIP: https://github.com/openshift/openshift-docs/pull/18851

Comment 4 Ashley Hardin 2020-01-13 20:57:18 UTC

Published content: https://docs.openshift.com/online/pro/dev_guide/managing_images.html#allowing-pods-to-reference-images-from-other-secured-registries