Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The RHEL base image CMD and Labels should be set up by default to run systemd inside the container following the instructions in : http://developers.redhat.com/blog/2016/09/13/running-systemd-in-a-non-privileged-container/
This would allow layered images to behave by default as a RHEL admin would expect from an existing system.
At the same time, it would not affect any existing layered builds that oververite CMD.
I think we could do this, except for one big issue. Currently in order to get systemd to stop correctly inside of a container, you need to send a different stop signal.SIGRTMIN+3, where normal containers are stopped using SIGTERM.
We could change the json file of the base image to use the SIGRTMIN+3 stop signal by default, but then any containers based off of it, would need to use
STOPSIGNAL SIGTRM
Sending SIGRTMIN+3 to a process seems to kill it fine, but I think we would need to worry about this causing problems.
Setting the CMD=/bin/init should be fine, because most people who build non systemd containers would override the CMD field.
I don't think we should be making fundamental changes like this *first* in RHEL.
These types of things should go upstream (Fedora/CentOS) first, and specifically in this case I really think it warrants some public discussion.
It's definitely going to break some of my workflows; I often do `docker run --rm -ti rhel7` type things for a quick shell. Obviously, appending /bin/bash there isn't hard.
But it's also different from the Fedora/CentOS base images. I'm very sure I'm not the only person who will find this confusing.
I agree, Lets not ship this until we understand the ramifications of the change.
Comment 7Frantisek Kluknavsky
2016-10-21 17:17:18 UTC
reverted
Comment 8Frantisek Kluknavsky
2018-04-16 17:54:28 UTC
rhel-server-docker will continue to run bash by default. A different image, rhel7-init-docker, built on top of rhel-server-docker, will run systemd by default.