Skip to content
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.

network inspect output is non-intuitive #1373

Closed
cpuguy83 opened this issue Nov 3, 2015 · 2 comments
Closed

network inspect output is non-intuitive #1373

cpuguy83 opened this issue Nov 3, 2015 · 2 comments

Comments

@cpuguy83
Copy link
Contributor

cpuguy83 commented Nov 3, 2015

Since a multi-host network is by definition available on every node of the cluster, there is only one entry in docker network ls.
However, if I docker network inspect multi I only get output from a single engine:

[
    {
        "Name": "multi",
        "Id": "5580acd70dd89d58cecd16df769ace923c91226ce9d6e22828ec83efd8a25c46",
        "Scope": "global",
        "Driver": "overlay",
        "IPAM": {
            "Driver": "default",
            "Config": [
                {}
            ]
        },
        "Containers": {
            "eaf4bc7e2f99fd3b82e7647ec449cd515cc1d53dffe3a037fa877121ce6f6508": {
                "EndpointID": "4de7a3ba418425e2e1a9ba7191ae8e302c56132163ddb7fa6ac65334a3e00e53",
                "MacAddress": "02:42:0a:00:01:02",
                "IPv4Address": "10.0.1.2/24",
                "IPv6Address": ""
            }
        },
        "Options": {}
    }
]

In reality I have 3 containers attached to this network, however there doesn't seem to be anyway to actually get at that information.

@abronan
Copy link
Contributor

abronan commented Nov 3, 2015

Yes we discussed about that in #1262 but this couldn't make it in time for 1.0.0. This will likely be included in a 1.0.1 with some small enhancements.

@abronan
Copy link
Contributor

abronan commented Dec 17, 2015

Closed by #1547

@abronan abronan closed this as completed Dec 17, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants