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 2090920 - Podman load keeps stale files in TMPDIR
Summary: Podman load keeps stale files in TMPDIR
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Yuhui Jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-26 22:40 UTC by mangesh.panche
Modified: 2023-08-11 13:54 UTC (History)
15 users (show)

Fixed In Version: podman-4.2.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 09:15:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers common pull 1044 0 None Merged libimage: load: close reader 2022-09-06 19:17:03 UTC
Github containers podman issues 14287 0 None closed Podman does not cleanup the temporary files after loading images 2022-09-06 19:17:03 UTC
Red Hat Issue Tracker RHELPLAN-123515 0 None None None 2022-05-26 22:46:24 UTC
Red Hat Product Errata RHSA-2022:7457 0 None None None 2022-11-08 09:16:27 UTC

Description mangesh.panche 2022-05-26 22:40:31 UTC 
Description of problem:
When command podman load -i <tar file> is executed, it creates temporary files (docker-tar*) in /var/tmp or directory configured in TMPDIR, but does not cleanup these files at the end. Due to this the filesystem keeps on filling on each docker load.

Version-Release number of selected component (if applicable):
4.0.2

How reproducible:
Easily reproducible

Steps to Reproduce:
1. Load docker image from the tar file
# docker load -i <tar file>
2. Check /var/tmp or directory configured in TMPDIR for files with pattern docker-tar*

Actual results:
# ls -al docker-tar*
-rw-------. 1 root root 5299626496 May 18 15:15 docker-tar505846964

Expected results:
No docker-tar* files present in the temporary directory after command finished executing.


Additional info:
The issue is fixed in podman mainline. Needs to be ported to 4.0.
https://github.com/containers/common/pull/1044
Comment 1 Tom Sweeney 2022-05-27 00:24:19 UTC 
@mangesh.panche I just wanted to verify versions that you reported.  You're saying you'd like this backported to Podman 4.0, however, you reported this against RHEL 8.4?  RHEL 8.4 had Podman v3.0.1 in it.  Did you just select the wrong RHEL release?

This will be fixed in Podman 4.1.1 which will be delivered in RHEL 8.6.0.2 in early August. Will that be suitable?  I'm not sure we'll be able to fix this prior.
Comment 2 mangesh.panche 2022-05-27 21:19:30 UTC 
@tsweeney We are currently using 8.4 but will move to 8.6, hence the request to port the change to Podman 4.0.
The timelines looks good to me.
Comment 3 Tom Sweeney 2022-05-27 21:43:05 UTC 
As this is acceptable for a 8.6.0.2 release, and it's fixed in Podman v4.1 which will be delivered then, I'm setting this to POST and assigning to @jnovy for any further BZ or packaging needs.
Comment 4 Jindrich Novy 2022-05-30 07:32:20 UTC 
Targeting this one at 8.7.0 in order to not to miss QE. https://github.com/containers/common/pull/1044 is not present in any released version of podman. Can mark this MODIFIED once released + built in RHEL.

Can we get qa ack please?
Comment 5 Jindrich Novy 2022-05-30 07:33:21 UTC 
Moving ITM to 26 as I have no idea when the new podman will be release.
Comment 13 mangesh.panche 2022-08-31 03:34:55 UTC 
Following up for the fix on RHEL 8.6 as confirmed earlier. Please let us know, when would we get this fix on RHEL 8.6?
Comment 15 Derrick Ornelas 2022-09-06 19:17:04 UTC 
Hi Mangesh, this fix will be part of podman v4.2 shipping with RHEL 8.7. Currently, there are no plans to backport this to podman v4.1.1. If you feel this issue impacts your use-case enough to warrant a more expedited fix please let your support representative know. One thing to note is that, based on the current release schedule, such a fix would be delivered roughly two weeks before 8.7 GA.
Comment 20 errata-xmlrpc 2022-11-08 09:15:47 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-2022:7457
Note You need to log in before you can comment on or make changes to this bug.