Podman ps and podman port with other container's network namespaces

[mheon]

If a container is created with --net=container, when podman ps and podman port are run on the container, we won't see any ports (as the ports are bound in the network namespace of another container). We should account for this and display the ports of the other container here, as the container does have ports forwarded to it.

[vrothberg]

@baude, @mheon : I think we can fix this along with some other networking work (e.g., POD issues).

[mheon]

Agree - this is very important for pod work

…

On Mon, Nov 19, 2018, 07:08 Valentin Rothberg ***@***.*** wrote: @baude <https://github.com/baude>, @mheon <https://github.com/mheon> : I think we can fix this along with some other networking work (e.g., POD issues). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#846 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHYHCIwgntjzwWeb83kjqrsEsGSK99eAks5uwp8pgaJpZM4USR8T> .

[mheon]

I think Port may be partially fixed already

…

On Mon, Nov 19, 2018, 08:05 Matthew Heon ***@***.*** wrote: Agree - this is very important for pod work On Mon, Nov 19, 2018, 07:08 Valentin Rothberg ***@***.*** wrote: > @baude <https://github.com/baude>, @mheon <https://github.com/mheon> : I > think we can fix this along with some other networking work (e.g., POD > issues). > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#846 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AHYHCIwgntjzwWeb83kjqrsEsGSK99eAks5uwp8pgaJpZM4USR8T> > . >

[rhatdan]

What is the latest on this issue?

[mheon]

Fairly certain this is still broken