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 2102381 - podman image failed with ERRO[0000] Unmounting /home/maor/.local/share/containers/storage/overlay/XX/merged: invalid argument
Summary: podman image failed with ERRO[0000] Unmounting /home/maor/.local/share/contai...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.6
Hardware: All
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-06-29 20:02 UTC by Jihoon Kim
Modified: 2022-11-08 09:34 UTC (History)
12 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:16:44 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers storage pull 1217 0 None Merged overlay driver: fix incorrect path of link dir 2022-08-26 10:50:55 UTC
Red Hat Issue Tracker RHELPLAN-126666 0 None None None 2022-06-29 20:17:16 UTC
Red Hat Product Errata RHSA-2022:7457 0 None None None 2022-11-08 09:17:17 UTC

Description Jihoon Kim 2022-06-29 20:02:32 UTC 
Description of problem:

Podman image failed with:

$ podman images -a
ERRO[0014] Unmounting /home/mdflickner/.local/share/containers/storage/overlay/2a6e21de446758b5d2fbb58d1ed8f560eb74e183c79463e40d098a1b0befe100/merged: invalid argument
Error: error retrieving size of image "caff249570b526005b8756aceea20b411c2a9fcb45ed61420f499775cab46a2f": you may need to remove the image to resolve the error: size/digest of layer with ID "2a6e21de446758b5d2fbb58d1ed8f560eb74e183c79463e40d098a1b0befe100" could not be calculated: creating overlay mount to 2a6e21de446758b5d2fbb58d1ed8f560eb74e183c79463e40d098a1b0befe100/merged, mount_data="lowerdir=7E4ZL3TYLFXJRVV5MVYU74EYPD/../diff1:l/SYTFWP4GNFLJPMKMFOCS6AWVQ7:l/AFYE47LSZ76XH6Y27C2IZZLJZ7:l/FRVWUBSYBFOMMTUOMTMCFLWIVN:l/D4JPUBSSRUYJQVC374YXTLDUOQ:l/C64IEUKTSAZXRQ2ZAOOOWATIET:l/4YUC633PKYUV2BO3VZGFRD7CCB:l/ZQPNJKGJMBERKZPLZYNI4GJMIU:l/JIBVJZJ7V2VLPJFUKDKTC7HCMM:l/S43EBB4KPYA4W27KE3MZBZGGKC:l/HB37LHCHDV6N6CXHOKZD6RJHC5:l/5R7PDRHSL5O7TX6CSNSXEWIGJD:l/QZAUUH23FNBRO5INLNDBL6FNYX:l/IPGTSYMB6WPNLHC7MI5WSOGRS5:l/A3SPSPTRBWSVQMDLFAFKN4ETZV:l/A2BWBTXTBNXF2EAEWW2PMNDG6K:l/4VSUZWMXTEHDYTWWQW7QIE2IXB:l/EXWDKVMOL7FUXHOOGZ5ZSBYLFP:l/VF5PFEI65LBH5GGACYFPDXFOYU:l/5Z45YQ64GSI52PCWBF54MRPY3D:l/BBBZESKPQ2PGCVIM4QM5C4Z4TG:l/BNK45K2HJAA37D46ZDEKO356PI:l/Y6HQ4L5CELCYQCDCFEVNJ4LDY3:l/LDHRCRW3Y7JN7DGUVGZXLRZ6HY:l/IAHF77GAI7JSANMHTGJNKTNOX5:l/227G5ZFUHNGGH2VGU4JC5VFOTE:l/KZ2YAGMLUDZYQG3SA44737GNTR:l/OFEZBYDNPXSQNMQMU7Z4VKSYZY:l/CTJK6URNW7P5P3GPXGCNOHOCII:l/A3C3O7MP6KQNIKCJ3MZWMYVI2T:l/X4LYY75FR5WI2WPQIMFH6DIWFS:l/3OTJ4KQZBVVXMCWAUR326TJE5A:l/AUK6PNZYRWFLSEQYJADJRY4ZZP:l/ZODBYJLX62WCOPS5P5APSH4PGJ:l/IFZPZEINRLSO35E7J74JJLPJ7Y:l/TWR4RDSUBGXUQBVHU2FHNXJ6HT:l/MVA7SJG2XB46GD2THQ2YGSYQAF:l/KCYIWKQVDPHU7CR7RYIZAEPGCB:l/PIMNESUHA4WEPJZRGDVNBS6E6Z:l/F5RVCYKT5DKPG3JL5EYO7I3N33:l/XKCMQW2DZG3TXDX6QKOL7GY3PY:l/LW5YFH3FGL2H7CTXZIZNTF6O6B:l/MOQUJWLRXTFFBG3YDZEKDNTFXZ:l/B3E3LEPUIZRAVP75CYRE2PIBMI:l/CO7SGQG7T65XEWHQMXZ6KTEIAW:l/LKFC6INA7G22P6YFAELLAKRENK:l/POXVX7XCIR6CETEUDOFB2AW7NL:l/POBRCE7C6DIBZHKF4FALNY6K4Z:l/LDWPJLZXQQYJPEJYZCYLND5ZIG:l/7VMJH6J4EJ6APRXGM3VFIFJTFR:l/PPO5MJXZO7ZMAQVNLHQ55ZWDXY:l/GUFYG337C7UPFPZP3FYFKNPI6E:l/3NDRFEBNAUQTVETBFTTO34EE4I:l/PRZQ5USPKXARXRN3HGNTB3GGFL:l/52I4KF2TAMPHRNWPDQJCZSSCR5,upperdir=2a6e21de446758b5d2fbb58d1ed8f560eb74e183c79463e40d098a1b0befe100/diff,workdir=2a6e21de446758b5d2fbb58d1ed8f560eb74e183c79463e40d098a1b0befe100/work": mountfrom re-exec error: exit status 1: output: no such file or directory


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

  podman-4.0.2-6.module+el8.6.0+14877+f643d2d6.x86_64 

How reproducible:

It seems the customer is hitting the same issue as described in the following upstream:

    https://github.com/containers/storage/issues/1216

1. Customer has a custom image that includes 49 layers

2. When the customer launches a container using the custom image with "--userns keep-id" flag, they received the error message shown in the Description.

3. However, the container runs fine. Only `podman ps` returns the error message.

4. When customer stopped the container and removed the image, podman image return the proper output.
Comment 2 Charlie Doern 2022-07-05 13:39:25 UTC 
if the version here is 4.0.2, the upstream fix would not be visible (unless backported) but seems to have resolved the problem. @gscrivan am I interpreting this correctly?
Comment 3 Giuseppe Scrivano 2022-07-05 15:16:28 UTC 
yes, I think you are correct.  The c/storage fix didn't hit the v4.0-rhel branch yet
Comment 9 errata-xmlrpc 2022-11-08 09:16:44 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.