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.

Sign up for GitHub

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

Jump to bottom

Container in multiple networks not showing all connections #1573

Closed
idcrosby opened this issue Jun 9, 2016 · 1 comment
Closed

Container in multiple networks not showing all connections #1573

idcrosby opened this issue Jun 9, 2016 · 1 comment
Assignees
@2opremio
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Milestone
0.16.0

Comments

@idcrosby
Copy link

idcrosby commented Jun 9, 2016

We have service which is connected to two networks, so has two IPs (as seen here via docker inspect)
screen shot 2016-06-09 at 14 52 32

On Scope, it is only showing one IP:
screen shot 2016-06-09 at 14 53 52

Attaching reports file. Affected service is "front-end"
report_09_06_json.zip
@2opremio 2opremio added the bug Broken end user or developer functionality; not working as the developers intended it label Jun 9, 2016
@2opremio 2opremio added this to the 0.16.0 milestone Jun 9, 2016
@2opremio
Copy link
Contributor

2opremio commented Jun 9, 2016 •
edited
Loading

To clarify this further, there are short-lived connections from 10.32.0.2 which weren't being displayed as edges in Scope because the container was only attributed IP 10.40.0.8

@2opremio 2opremio mentioned this issue Jun 10, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@2opremio 2opremio

Labels
bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Milestone
0.16.0
Development

No branches or pull requests
2 participants
@idcrosby @2opremio