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 1768866

Summary: "podman start --attach" in the example unit file has been criticized by podman developers as something wrong
Product: Red Hat Enterprise Linux 7 Reporter: Alexander E. Patrakov <patrakov>
Component: doc-RHEL-AtomicAssignee: Vikram Goyal <vigoyal>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact: Vikram Goyal <vigoyal>
Priority: high    
Version: 7.8CC: bkelly, dwalsh, kdwivedi, mharri, rhel-docs
Target Milestone: rcKeywords: Documentation, Extras
Target Release: ---Flags: pm-rhel: mirror+
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: 2021-05-05 07:30:33 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 Alexander E. Patrakov 2019-11-05 12:34:39 UTC
Document URL: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/managing_containers/running_containers_as_systemd_services_with_podman

Section Number and Name: 4.1. Starting Containers with systemd

Describe the issue: Podman developer Matt Heon said: "Looking at your unit files, I don't think they operate as advertised (`start --attach` can exit while the container is still running, so tracking it is not a reliable way of tracking the container)", see https://lists.podman.io/archives/list/podman@lists.podman.io/message/7M6P2RZGLKDZOTW5KCM3SL23CESSO7RO/

Suggestions for improvement: Reproduce what the current podman writes with `podman generate systemd`.

Additional information: I am not a user of RHEL 7, just copy-pasted the unit from the documentation while on Fedora 31 and got corrected.

Comment 5 RHEL Program Management 2021-05-05 07:30:33 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.