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 1898911 - Empty cidfile after container creation
Summary: Empty cidfile after container creation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.3
Hardware: All
OS: Unspecified
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Jindrich Novy
QA Contact: Alex Jia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-18 10:10 UTC by Filip Januš
Modified: 2023-09-15 00:51 UTC (History)
18 users (show)

Fixed In Version: podman-2.2 or newer
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-16 14:21:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 9 Scott McCarty 2020-12-01 14:45:51 UTC 
Matt/Dan/Tom/All,
    Is there a way that we could roll forward to Podman 2.2.0 for the RHEL 8.3.1 release? I know it's late in the game, but my gut feeling says this is easier/safer/better than back porting. Is there anything that makes us nervous about supporting the 2.2.0 release for 12 weeks until we launch Podman 3.0 in RHEL 8.4?
Comment 19 Alex Jia 2021-01-13 11:56:58 UTC 
Can reproduce this bug on podman-2.1.1-2.module+el8.3.1+8289+097241fc.x86_64 w/
runc-1.0.0-68.rc92.module+el8.3.1+8289+097241fc.x86_64, and verified it on
podman-2.2.1-3.module+el8.3.1+9380+85743958.x86_64 w/
runc-1.0.0-69.rc92.module+el8.3.1+9380+85743958.x86_64

1. podman-2.1.1-2.module+el8.3.1+8289+097241fc.x86_64
[root@hpe-dl380pgen8-02-vm-8 ~]# podman run -i --cidfile /tmp/foobar --name myctr1 rhel7 /bin/sh
pwd
/
[root@ibm-x3650m4-01-vm-14 ~]# cat /tmp/foobar

NOTE: nothing in /tmp/foobar

2. podman-2.2.1-3.module+el8.3.1+9380+85743958.x86_64
[root@ibm-x3650m4-01-vm-14 rpms]# podman run -i --cidfile /tmp/cidfile --name myctr2 rhel7 /bin/sh
pwd
/

[root@ibm-x3650m4-01-vm-14 ~]# cat /tmp/cidfile
427e4b03313fe60c1ba066368af6c18bc189faaca570f483bfdfb44cbfa8afc6
Comment 21 errata-xmlrpc 2021-02-16 14:21:54 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 (Moderate: container-tools:rhel8 security, bug fix, and enhancement 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-2021:0531
Comment 22 Red Hat Bugzilla 2023-09-15 00:51:20 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days
Note You need to log in before you can comment on or make changes to this bug.