Bryan Boreham

The probe code is organised into different subdirectories by source, so probably under `scope/probe/docker`. Next problem is deciding which node to put the data on - possibly the “tagger” could...

That's a 3rd-party package, so you could try asking in their repo. I guess for the current Scope build that header is installed by one of the `apt-get` lines. I...

Thanks for looking further at this. We currently have a 2-stage build with the Dockerfile in `backend` used as builder. You appear to have introduced a different 2-stage build, without...

Although it is not using Docker's 2-stage syntax, the `backend` image is effectively used in the same way. What needs to change is we need to end up with only...

#3845 reminded me there is a [`DNSSnooper`](https://github.com/weaveworks/scope/blob/b8d04b9f1ea03e0f69998dce64dc90d8d881df5c/probe/endpoint/dns_snooper.go#L1) which is not built for arm. I think this was to do with needing C libraries for pcap, which as you say you...

Duplicate of #2760?

Also note [I have proposed](https://github.com/weaveworks/scope/issues/3710) that we use Prometheus as a source for metrics in future, so perhaps a good opportunity to look at how we can source Kubernetes resource...

Thanks @CodeAholic . Maybe what is needed is clear instructions in the docs how to get Scope working with a proxy. If someone could make a PR for that, that'd...

Can you try modifying the DaemonSet to mount that path inside the container?

Small clarification: we were working on _macvtap_. Ipvlan will not work with the current code; it expects that you give it a device which can has its own L2 identity....