Skip to content
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 ps and podman port with other container's network namespaces #846

Closed
mheon opened this issue May 29, 2018 · 5 comments

Comments

Projects
None yet
3 participants
@mheon
Copy link
Collaborator

commented May 29, 2018

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.

@mheon mheon added the enhancement label May 29, 2018

@vrothberg

This comment has been minimized.

Copy link
Member

commented Nov 19, 2018

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

@mheon

This comment has been minimized.

Copy link
Collaborator Author

commented Nov 19, 2018

@mheon

This comment has been minimized.

Copy link
Collaborator Author

commented Nov 19, 2018

@rhatdan

This comment has been minimized.

Copy link
Member

commented Dec 22, 2018

What is the latest on this issue?

@mheon

This comment has been minimized.

Copy link
Collaborator Author

commented Dec 22, 2018

Fairly certain this is still broken

baude added a commit to baude/libpod that referenced this issue Feb 13, 2019

show container ports of network namespace
in cases where a container is part of a network namespace, we should
show the network namespace's ports when dealing with ports. this
impacts ps, kube, and port.

fixes: containers#846

Signed-off-by: baude <bbaude@redhat.com>

baude added a commit to baude/libpod that referenced this issue Feb 13, 2019

show container ports of network namespace
in cases where a container is part of a network namespace, we should
show the network namespace's ports when dealing with ports. this
impacts ps, kube, and port.

fixes: containers#846

Signed-off-by: baude <bbaude@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.