Bug 1393132 - [RFE] OpenShift provided images need to use systemd (init system)
Summary: [RFE] OpenShift provided images need to use systemd (init system)
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: ---
: ---
Assignee: Tom Sweeney
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-08 23:06 UTC by Eric Jones
Modified: 2019-12-16 07:20 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-12 13:54:36 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Eric Jones 2016-11-08 23:06:12 UTC
- What is the nature and description of the request? 
There are situations in which having the container running with a systemd entrypoint so it can run with an init system. 

[0] http://developers.redhat.com/blog/2016/09/13/running-systemd-in-a-non-privileged-container/

- Why does the customer need this? (List the business requirements here) 
To be able to kill zombie processes and other such benefits

- Is there already an existing RFE upstream or in Red Hat Bugzilla?
I was unable to find anything

Comment 9 Eric Rich 2018-03-12 13:54:36 UTC
This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.


Note You need to log in before you can comment on or make changes to this bug.