Bug 1298998

Summary:	[DOCS] Need to explain how to modify or alter images with S2I process
Product:	OpenShift Container Platform	Reporter:	Eric Rich <erich>
Component:	Documentation	Assignee:	Thien-Thi Nguyen <tnguyen>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Vikram Goyal <vigoyal>
Severity:	medium	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	urgent
Version:	3.1.0	CC:	amelicha, aos-bugs, erich, jokerman, mmccomas, vigoyal
Target Milestone:	---	Keywords:	NeedsTestCase
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-17 19:26:19 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:
Bug Depends On:
Bug Blocks:	1299000

Description Eric Rich 2016-01-15 16:11:21 UTC

Document URL: https://docs.openshift.com/enterprise/3.1/creating_images/index.html

Section Number and Name: NOT Defined

Describe the issue: Nowhere in the documentation does it explain how to add a RH provided RPM to an OSE image.

Suggestions for improvement: Define a new section that outlines modifying images.

Comment 2 Thien-Thi Nguyen 2016-01-29 02:32:55 UTC

AFAICT the recommended way to install RPMs is "yum install".  What am i missing?

Re project name being required for "docker tag" -- Eric could you please show a command (w/ output) where omitting the the project name results in failure?  Likewise, a command (again, w/ output) that demonstrates success when the project name is included?

Adding Eric as needinfo, for these questions.  Any other "project name for docker tag"-related information would be welcome, too.

Comment 3 Eric Rich 2016-01-29 11:57:04 UTC

(In reply to Thien-Thi Nguyen from comment #2)
> AFAICT the recommended way to install RPMs is "yum install".  What am i
> missing?
> 

But how is this done with the s2i process or using your code, etc. 

> Re project name being required for "docker tag" -- Eric could you please
> show a command (w/ output) where omitting the the project name results in
> failure?  

I do not explicitly have one more does the associated case. This is is simply a suggestion/comment from a customer. It lines up with what happens with the registry so it seems plausabe that this is the case. 

> Likewise, a command (again, w/ output) that demonstrates success
> when the project name is included?
> 
> Adding Eric as needinfo, for these questions.  Any other "project name for
> docker tag"-related information would be welcome, too.

For this I would check with engineering and we to make sure we have process and test to cover the use case we are documenting.

Comment 4 Thien-Thi Nguyen 2016-03-17 18:52:58 UTC

The necessity of including project name (as the "namespace" component of a pull spec) was documented as part of:

 https://bugzilla.redhat.com/show_bug.cgi?id=1299000

The other part of the BZ (interaction between s2i and "yum install") still remains.

Comment 5 Thien-Thi Nguyen 2016-03-17 19:26:19 UTC

Using "yum install" (for example) in a Dockerfile is documented:
- https://docs.openshift.com/enterprise/3.1/dev_guide/builds.html#docker-strategy-options
- https://docs.openshift.com/enterprise/3.1/dev_guide/builds.html#dockerfile-source

Moving this bug to CLOSED CURRENTRELEASE.

Comment 6 Red Hat Bugzilla 2023-09-14 03:16:13 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days