-
Notifications
You must be signed in to change notification settings - Fork 712
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
Scope no longer works on Rancher 1.2 (uses CNI networking) #2164
Comments
Thanks for reporting this @johnrengelman !
Do you happen to know the reason for this? (I have never personally used Rancher) I am asking because Scope works with Kubernetes (and CNI plugins), and the containers still show their IP with More importantly, do you know how could we obtain the IP of the containers?
This is a core piece of the Scope functionality, so I wouldn't put it in a plugin, but directly in Scope. I am happy to guide you once we figure out how to obtain the IPs (for normal containers is done here and the networks from Docker plugins are obtained here) |
Rancher is launching the containers with Inspecting that container:
Checking Docker Networks:
Notice the last one corresponds to the
So, not sure what else I can do from that point. There's a |
Related: #1550 Answering myself:
I think we've only ever tested the weave CNI plugin and we use other means to obtain the IPs in that case. |
Aha! Lacking a generic way to obtain the container IPs and Networks from CNI, this should be good enough:
|
@johnrengelman If you want to give it a try, in order to add the rancher IPs and Networks you would have to:
EDIT: You will also need to incorporate a new prefix for Rancher ( |
An alternative approach (suggested by @bboreham ) which could more-generically cover CNI plugins in all platforms would be to exec into all the networking namespaces. Quoting him:
|
@johnrengelman Want to give it a try? |
@2opremio Yeah, I'm going to put it on my list for taking a crack at this week. |
Fantastic! Let me know if you need any help.
…On Mon, Jan 30, 2017 at 7:42 PM, John Engelman ***@***.***> wrote:
@2opremio <https://github.com/2opremio> Yeah, I'm going to put it on my
list for taking a crack at this week.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2164 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACQOJMIlg6jqMKFJplJ3Kr4bNBX5UUumks5rXi8hgaJpZM4Lv59f>
.
|
With Rancher 1.2, Rancher has moved to CNI for networking, so the container IP is no longer available via
docker inspect
. This causes the graph to lose connection edges.I'm curious what the solution for this is. I'm not familiar with the weave scope code, so would it require a custom Rancher plugin for probe to discover that information?
I'd be willing to take a shot at implementing this.
The text was updated successfully, but these errors were encountered: