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-Atomic	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	high
Version:	7.8	CC:	bkelly, dwalsh, kdwivedi, mharri, rhel-docs
Target Milestone:	rc	Keywords:	Documentation, Extras
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:	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.