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

EndpointID isn't valid in Network Inspect #2586

Closed
sflxn opened this issue Oct 5, 2016 · 3 comments
Closed

EndpointID isn't valid in Network Inspect #2586

sflxn opened this issue Oct 5, 2016 · 3 comments
Labels
component/portlayer/network kind/defect Behavior that is inconsistent with what's intended priority/p4

Comments

@sflxn
Copy link
Contributor

sflxn commented Oct 5, 2016

If we execute docker network inspect, the EndpointID listed is actually the ID of the container. That doesn't appear right. Below is an example output:

loc@ubuntu:~/go/src/github.com/vmware/vic$ docker network inspect bridge
[
    {
        "Name": "bridge",
        "Id": "3622e8f3cb80450b6610ae9e04905047fe94d7de21b8180539edfaa7e57f4b74",
        "Scope": "",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "",
            "Options": {},
            "Config": [
                {
                    "Subnet": "172.16.0.0/16",
                    "Gateway": "172.16.0.1"
                }
            ]
        },
        "Internal": false,
        "Containers": {
            "81bee217730745383e77a683b2ef7f6d01e3e9d33fcd72266bc31270b8015c32": {
                "Name": "modest_wilson",
                "EndpointID": "81bee217730745383e77a683b2ef7f6d01e3e9d33fcd72266bc31270b8015c32",
                "MacAddress": "",
                "IPv4Address": "172.16.0.2/16",
                "IPv6Address": ""
            }
        },
        "Options": {},
        "Labels": {}
    }
]
@mdubya66 mdubya66 added this to the VIC GA Release milestone Oct 6, 2016
@mdubya66 mdubya66 added kind/defect Behavior that is inconsistent with what's intended kind/bug/no-repro labels Nov 2, 2016
@mlh78750 mlh78750 modified the milestones: v0.9.0, VIC GA Release Nov 10, 2016
@hmahmood hmahmood self-assigned this Dec 13, 2016
@hmahmood
Copy link
Contributor

Acceptance:

  • verify that endpoint id not the same as the container id and is unique per endpoint

@hmahmood hmahmood removed their assignment Jan 17, 2017
@mhagen-vmware mhagen-vmware removed this from the v0.9.0 milestone Jan 18, 2017
@corrieb
Copy link
Contributor

corrieb commented Jul 19, 2017

Confirmed this is still a bug and is easy to reproduce. Can't be a difficult fix.

@hickeng
Copy link
Member

hickeng commented Jun 14, 2018

This is not recreating while looking at #8052

@hickeng hickeng closed this as completed Jun 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/portlayer/network kind/defect Behavior that is inconsistent with what's intended priority/p4
Projects
None yet
Development

No branches or pull requests

8 participants