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.
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 (Moderate: podman security and bug fix update), 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://access.redhat.com/errata/RHSA-2022:6119
Comment 12Red Hat Bugzilla
2023-09-15 01:55:51 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days
Test with podman-1.6.4-35.el7_9.x86_64 and the service file created already included the lines: # cat /etc/systemd/system/multi-user.target.wants/container-web1.service # container-web1.service # autogenerated by Podman 1.6.4 # Fri Jul 15 12:04:03 EDT 2022 [Unit] Description=Podman container-web1.service Documentation=man:podman-generate-systemd(1) Wants=network.target After=network-online.target And in the system after reboot the service are running as expected: [root@amd-dinar-04 ~]# curl localhost:7000 My test page [root@amd-dinar-04 ~]# systemctl status container-web1.service ● container-web1.service - Podman container-web1.service Loaded: loaded (/etc/systemd/system/container-web1.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2022-07-15 12:08:51 EDT; 3min 48s ago Docs: man:podman-generate-systemd(1) Process: 1263 ExecStart=/usr/bin/podman start web1 (code=exited, status=0/SUCCESS) Main PID: 2086 (conmon) CGroup: /system.slice/container-web1.service ‣ 2086 /usr/bin/conmon --api-version 1 -s -c a46b74713f2f312dbacceb44179fdbcc8acca714a0a0f61099d105337a989e70 -u a46b74713f2f312dbac... Jul 15 12:08:35 amd-dinar-04.khw1.lab.eng.bos.redhat.com systemd[1]: Starting Podman container-web1.service... Jul 15 12:08:48 amd-dinar-04.khw1.lab.eng.bos.redhat.com podman[1263]: 2022-07-15 12:08:48.195318141 -0400 EDT m=+9.185788230 system refresh Jul 15 12:08:51 amd-dinar-04.khw1.lab.eng.bos.redhat.com podman[1263]: 2022-07-15 12:08:51.160997719 -0400 EDT m=+12.151467611 container i...web1) Jul 15 12:08:51 amd-dinar-04.khw1.lab.eng.bos.redhat.com podman[1263]: 2022-07-15 12:08:51.327818516 -0400 EDT m=+12.318288433 container s...web1) Jul 15 12:08:51 amd-dinar-04.khw1.lab.eng.bos.redhat.com podman[1263]: web1 Jul 15 12:08:51 amd-dinar-04.khw1.lab.eng.bos.redhat.com systemd[1]: Started Podman container-web1.service. Hint: Some lines were ellipsized, use -l to show in full. So move it to Verified.