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 1756919 - Podman inspect does not parse the keys of the returned JSON
Summary: Podman inspect does not parse the keys of the returned JSON
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-30 08:25 UTC by Tibor Dudlák
Modified: 2023-04-08 09:10 UTC (History)
7 users (show)

Fixed In Version: RHEL 8.2, Podman 1.6.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 15:47:35 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-37625 0 None None None 2023-04-08 09:10:30 UTC
Red Hat Product Errata RHSA-2020:1650 0 None None None 2020-04-28 15:48:20 UTC

Description Tibor Dudlák 2019-09-30 08:25:35 UTC
Description of problem:
Podman does not parse the keys of the returned JSON from podman inspect

Version-Release number of selected component (if applicable):
podman-1.4.2-2.module+el8.1.0+4016+4220c060.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Deploy a FreeIPA server container
2. podman inspect --format '{{ range .Mounts }}{{ if eq .Destination "/data" }}{{ .Source }}{{ end }}{{ end }}' freeipa-server-container

Actual results:
podman can not parse Source not Desination

Expected results:
The values can be parsed as they are in podman inspect output without an --format option

Additional info:
I have observed this issue on fedora as well, update to newer podman solved issue for me

Comment 1 Tibor Dudlák 2019-09-30 10:25:28 UTC
Running this command results into:

Error: Template parsing error: template: image:1:28: executing "image" at <.Destination>: can't evaluate field Destination in type *libpod.InspectMount
Error: Template parsing error: template: image:1:11: executing "image" at <.Volumes>: can't evaluate field Volumes in type *shared.InspectContainer

Comment 3 Matthew Heon 2019-09-30 12:35:29 UTC
The rework on `podman inspect` output landed in 1.5.1, I think. We should have a 1.6.x or later build in 8.1.1, which will include the fix.

Comment 4 Tibor Dudlák 2019-09-30 14:24:16 UTC
Thanks for clarification.

Comment 10 errata-xmlrpc 2020-04-28 15:47:35 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, 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-2020:1650


Note You need to log in before you can comment on or make changes to this bug.