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
@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.
@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.
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.
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?
Moving ITM to 26 as I have no idea when the new podman will be release.
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?
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.
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