-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman inspect format doesn' t work for Container Port bindings #8444
Comments
more interesting behaviours
however,
|
/assign @jwhonce PTAL |
The man page indicates to me that it returns go format structs OR JSON. |
with previous version, because you could specify JSON in 2.1.x
and now it returns
|
@jwhonce PTAL |
ok , so forget about the json thing, @jwhonce can you give me a way to obtain the port bindings, I can't iterate over the map and I don't know how to do it, I tried in all different formats without success
or
however, I can get the map
|
ok, so the problem is that is not returning a map when it tries to evaluate, it tries to evaluate a slice
|
anyway, this is a big problem and blocker for docker users to migrate to podman, the |
@jwhonce PTAL |
* Add template func to inspect template processing * Added test using repro from containers#8444 Fixes containers#8444 Signed-off-by: Jhon Honce <jhonce@redhat.com>
I have this same issue on version 2.2.1. |
Is it working on the main branch? |
I don’t see that commit in a release yet, so it will probably land in
Podman 3.0, likely coming in the next few weeks.
…On Sun, Jan 10, 2021 at 08:07 Daniel J Walsh ***@***.***> wrote:
Is it working on the main branch?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8444 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3AOCF2R2DHTI6CGITQ7FLSZGRATANCNFSM4T6PPDIA>
.
|
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
KIND uses
to get the exposed ports of the containers, this fails with new version because it no longer reports a json
It also says that the inspect command defaults to json
but it is returning a go struct:
Describe the results you expected:
Is json not going to be the default moving forward or not going to be available as output of the
inspect
command?Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: