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

Bug 1585289

Summary:	Containers should be started with --init option
Product:	OpenShift Container Platform	Reporter:	Rob Cernich <rcernich>
Component:	Containers	Assignee:	Jhon Honce <jhonce>
Status:	CLOSED DUPLICATE	QA Contact:	DeShuai Ma <dma>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, dwalsh, jokerman, mmccomas, mpatel
Target Milestone:	---
Target Release:	---
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:	2018-06-01 20:44:58 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 Rob Cernich 2018-06-01 18:12:56 UTC

Description of problem:
Processes are not reaped properly from container running within OpenShift.


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


How reproducible:
Always


Steps to Reproduce:
1.  Start a pod
2.  Browse to Terminal tab for pod
3.  Execute command, e.g. ls
4.  Browse to a different page, without typing "exit"
5.  Browse back to Terminal tab for pod
6.  Execute "ps" - notice the additional sh process
7.  Repeat steps 4-6 and notice the number of processes growing.

Actual results:
Processes continue to accumulate.


Expected results:
Processes are properly reaped.


Additional info:
Running docker with --init option appears to be the documented solution.

Workaround:
Containers can use dummy-init as an entry point if there's a critical need, in lieu of a proper fix to the container runtime in OpenShift.

Comment 2 Jhon Honce 2018-06-01 20:44:58 UTC


*** This bug has been marked as a duplicate of bug 1561195 ***