-
Notifications
You must be signed in to change notification settings - Fork 174
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
docker network inspect does not show container in endpoint list if powered on out-of-band #8052
Comments
The root cause looks during handleEvent https://github.com/vmware/vic/blob/master/lib/portlayer/network/network.go#L120 |
This is related to #8405 Yang is fixing to process containerPoweredOn event. |
@hickeng @wjun with the fix #8405, this issue does not appear. The steps are: 1> list all containers yuyangbj@yuyangbj-vic:~/GoProjects/src/github.com/yuyangbj/vic/bin$ docker --tls ps yuyangbj@yuyangbj-vic:~/GoProjects/src/github.com/yuyangbj/vic/bin$ docker --tls network inspect routable 2> Power off the container VM from vSphere client yuyangbj@yuyangbj-vic:~/GoProjects/src/github.com/yuyangbj/vic/bin$ docker --tls network inspect routable 3> Power on the container VM from vSphere client, everything looks good yuyangbj@yuyangbj-vic: |
This issue applies only if the container has been powered on out-of-band. The container is also omitted if it is powered off, but that aligns with regular docker behaviour (although possibly counter-intuitive for a VCH where the connection to the network is independent of an assigned address on it).
We see the same output irrespective of whether the container is just created, powered off, or powered on by out-of-band means.
My primary concern here is whether this occurs during an HA restart.
Steps to recreate
The text was updated successfully, but these errors were encountered: