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.

Bug 1120206

Summary: Installer changes required for package: systemd-container
Product: Red Hat Enterprise Linux 7 Reporter: Eng Ops Maitai User <engops-maitai>
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: dwalsh, engops-maitai, mbanas, vpavlin, walters
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-19.31.92-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 14:02:03 UTC Type: ---
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: 1114029    
Attachments:
Description Flags
patch so --dirinstall will work none

Comment 3 Daniel Walsh 2014-09-02 23:24:32 UTC
systemd-container should only be used within docker images, it should never be used on bare metal systems.

Comment 4 Colin Walters 2014-09-16 21:19:54 UTC
I'm not aware of any installer changes necessary for this.  The main thing we need to prevent is anaconda somehow seeing systemd-container in the yum repositories used for regular installations.

I think it's in RHEL Extras, so as long as the installation target doesn't include that, Anaconda should be fine.

Comment 5 Colin Walters 2014-09-16 21:20:57 UTC
Oh, but maybe this is about the opposite use case, where someone was hitting issues building a Docker container using ImageFactory (which uses Anaconda)?

Comment 7 Brian Lane 2014-09-18 18:43:46 UTC
There's a bug in --dirinstall that needs to be fixed (I'll attach a patch). With that fix I've tested a minimal kickstart using fakesystemd or systemd-container, and as long as you don't include kickstart commands that trigger calls to systemctl a -anaconda --dirinstall --text --kickstart=... works fine.

Don't include firstboot or services and it will work fine. If there are specific problems, please add them to this bug and I'll take a look at them.

Comment 8 Brian Lane 2014-09-18 18:44:12 UTC
Created attachment 939010 [details]
patch so --dirinstall will work

Comment 12 errata-xmlrpc 2015-03-05 14:02:03 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0312.html

Comment 13 Red Hat Bugzilla 2023-09-14 02:11:35 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days