podman inspect network doesn't include running containers #14126
Comments
github-actions
bot
added
macos
|
@baude I think you looked at this before? I am not the biggest fan of adding this to the network inspect output. The current network inspect output is not docker compatible at all, there are just a lot of different things in the podman/docker network stack. You can get docker compatible output via the API. Although I am not sure if this is correctly implement there. |
|
The question I have, Is it useful to a user to figure out which containers are using a particular network? |
You can get this with |
|
Ok, as long as that is easy to retrieve, I don't see the compatibility as that big of an issue. |
|
this is a duplicate of a jira card i was working on. the code is done but the problem is that would be a breaking change on output. we discussed podman 5, but i also would like to go back and look at things to see if i can weasel it in without breaking changes. |
|
This would work but would break compatibility with docker (which I understand is not a big concern for you). |
|
we really do try on the compatibility stuff. in this case, the easy button just won't work ... but if you look at my update, i committed to trying it a different way. I have the code all written and it works, so not far away. |
|
A friendly reminder that this issue had no activity for 30 days. |
|
@baude what is the state of this one now? |
|
feel victim to other priorities. will try to pick back up soon, |
|
A friendly reminder that this issue had no activity for 30 days. |
|
@Luap99 PTAL |
|
A friendly reminder that this issue had no activity for 30 days. |
|
A friendly reminder that this issue had no activity for 30 days. |
|
cannot be done until podman 5 |
|
Sorry I missed that. Wish there was a way to stop the reminder on issues waiting for podman 5. |
Like docker podman network inspect should output the information of
running container with their ip/mac address on this network.
However the output format is not docker compatible as this cannot
include all the info we have and the previous output was already not
compatible so this is not new.
New example output:
```
[
{
...
"containers": {
"7c0d295779cee4a6db7adc07a99e635909413a390eeab9f951edbc4aac406bf1": {
"name": "c2",
"interfaces": {
"eth0": {
"subnets": [
{
"ipnet": "10.89.0.4/24",
"gateway": "10.89.0.1"
},
{
"ipnet": "fda3:b4da:da1e:7e9d::4/64",
"gateway": "fda3:b4da:da1e:7e9d::1"
}
],
"mac_address": "1a:bd:ca:ea:4b:3a"
}
}
},
"b17c6651ae6d9cc7d5825968e01d6b1e67f44460bb0c140bcc32bd9d436ac11d": {
"name": "c1",
"interfaces": {
"eth0": {
"subnets": [
{
"ipnet": "10.89.0.3/24",
"gateway": "10.89.0.1"
},
{
"ipnet": "fda3:b4da:da1e:7e9d::3/64",
"gateway": "fda3:b4da:da1e:7e9d::1"
}
],
"mac_address": "f6:50:e6:22:d9:55"
}
}
}
}
}
]
```
Fixes containers#14126
Fixes https://issues.redhat.com/browse/RHEL-3153
Signed-off-by: Paul Holzinger <[email protected]>
stale-locking-app
bot
added
the
locked - please file new issue/PR
/kind bug
Description
podman network inspectdoesn't include containers using the networkSteps to reproduce the issue:
Create network
podman network createStart container
podman run -it --network podman1 alpineInspect network
podman inspect podman1Describe the results you received:
podman inspect podman1does not contain a list of containers using the network.Describe the results you expected:
Same command in docker contains a list of containers.
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 podmanorapt list podman):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Macbook M1 installed with homebrew
The text was updated successfully, but these errors were encountered: