-
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
inspect command: Populate Bridge field in network settings #6618
Comments
Do you mean there should be
|
No - that looks like the output of a network from |
A friendly reminder that this issue had no activity for 30 days. |
Should be possible, but a little annoying to retrieve. Maybe a good job for
an intern?
…On Sat, Jul 25, 2020, 07:20 Daniel J Walsh ***@***.***> wrote:
@QiWang19 <https://github.com/QiWang19> @mheon <https://github.com/mheon>
What is the scoop on this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6618 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3AOCDHSHEH5JW5IDAK5H3R5K5YZANCNFSM4N7S42FA>
.
|
Know one has worked on this, and it is still an issue. (At least I verified the bug using the repeater above). @containers/podman-maintainers Anyone want to take a look? |
@baude do you have time for this? |
A friendly reminder that this issue had no activity for 30 days. |
Still an issue. |
@mheon Any chance you can work on this? |
I can peek at it ... |
when inspecting a container that is only connected to the default network, we should populate the default network in the container inspect information. Fixes: containers#6618 Signed-off-by: baude <[email protected]>
when inspecting a container that is only connected to the default network, we should populate the default network in the container inspect information. Fixes: containers#6618 Signed-off-by: baude <[email protected]> MH: Small fixes, added another test Signed-off-by: Matthew Heon <[email protected]>
/kind feature
Populate bridge field in network settings when applicable
Steps to reproduce the issue:
sudo podman run -m=40m -p 8080:89 --network=bridge redis
sudo podman inspect <container>
Describe the results you received:
Describe the results you expected:
Bridge to be populated with the cni id of the bridge in use
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: