weaveworks / scope

Monitoring, visualisation & management for Docker & Kubernetes

Home Page:https://www.weave.works/oss/scope/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

How come I don't get all the purty lines? :p

YouveGotMeowxy opened this issue · comments

commented

image

I'm using the latest version of Scope via the Docker container on a Win 10 machine w/Docker Desktop.

I thought I was sposed to see a bunch of lines showing how the containers are connected to each other?

Here's the Compose I use:

version: '2'

services:
    scope:
        container_name: scope
        hostname: scope
        image: weaveworks/scope
        ports:
            - '9029:4040'
        volumes:
          - "/var/run/docker.sock:/var/run/docker.sock:rw"
        command:
          - "--probe.docker=true"
          - "--weave=false"

Did I screw something up?

The lines are generated from TCP connections, and Scope has a variety of strategies to extract those from Linux. If you could post the logs of the 'probe' container we may be able to see what went wrong.

commented

Hi @bboreham

Here's what the logs show when I load up Scope and click a few buttons:

yesterday at 4:46 PM time="2019-12-26T22:46:10Z" level=info msg="publishing to: 127.0.0.1:4040"
yesterday at 4:46 PM <probe> INFO: 2019/12/26 22:46:10.164836 Basic authentication disabled
yesterday at 4:46 PM <app> INFO: 2019/12/26 22:46:10.175175 app starting, version 8b1296c8, ID 4de35a13a2575d41
yesterday at 4:46 PM <app> INFO: 2019/12/26 22:46:10.176037 command line args: --mode=app --probe.docker=true --weave=false
yesterday at 4:46 PM <app> INFO: 2019/12/26 22:46:10.178889 Basic authentication disabled
yesterday at 4:46 PM <probe> INFO: 2019/12/26 22:46:10.186449 command line args: --mode=probe --probe.docker=true --weave=false
yesterday at 4:46 PM <app> INFO: 2019/12/26 22:46:10.186679 listening on :4040
yesterday at 4:46 PM <probe> INFO: 2019/12/26 22:46:10.189595 probe starting, version 8b1296c8, ID 205683cc2eebae8b
yesterday at 4:46 PM <probe> INFO: 2019/12/26 22:46:10.221703 Control connection to 127.0.0.1 starting
yesterday at 4:46 PM <probe> WARN: 2019/12/26 22:46:10.276206 Error setting up the eBPF tracker, falling back to proc scanning: cannot open kprobe_events: open /sys/kernel/debug/tracing/kprobe_events: no such file or directory
yesterday at 4:46 PM <probe> ERRO: 2019/12/26 22:46:10.277904 Docker: problem with bridge docker0: route ip+net: no such network interface
yesterday at 4:46 PM <probe> ERRO: 2019/12/26 22:46:10.278498 plugins: problem loading: no such file or directory
yesterday at 4:46 PM <probe> INFO: 2019/12/26 22:46:10.320661 Publish loop for 127.0.0.1 starting
yesterday at 5:04 PM time="2019-12-26T23:04:42Z" level=info msg="publishing to: 127.0.0.1:4040"
yesterday at 5:04 PM <probe> INFO: 2019/12/26 23:04:42.397546 Basic authentication disabled
yesterday at 5:04 PM <app> INFO: 2019/12/26 23:04:42.477399 app starting, version 8b1296c8, ID 705095a15ebe4cb8
yesterday at 5:04 PM <app> INFO: 2019/12/26 23:04:42.494311 command line args: --mode=app --probe.docker=true --weave=false
yesterday at 5:04 PM <probe> INFO: 2019/12/26 23:04:42.496381 command line args: --mode=probe --probe.docker=true --weave=false
yesterday at 5:04 PM <probe> INFO: 2019/12/26 23:04:42.496471 probe starting, version 8b1296c8, ID 7670dc1e28f1154c
yesterday at 5:04 PM <app> INFO: 2019/12/26 23:04:42.497181 Basic authentication disabled
yesterday at 5:04 PM <app> INFO: 2019/12/26 23:04:42.517057 listening on :4040
yesterday at 5:04 PM <probe> INFO: 2019/12/26 23:04:42.724173 Control connection to 127.0.0.1 starting
yesterday at 5:04 PM <probe> WARN: 2019/12/26 23:04:42.737861 Error setting up the eBPF tracker, falling back to proc scanning: cannot open kprobe_events: open /sys/kernel/debug/tracing/kprobe_events: no such file or directory
yesterday at 5:04 PM <probe> ERRO: 2019/12/26 23:04:42.747660 Docker: problem with bridge docker0: route ip+net: no such network interface
yesterday at 5:04 PM <probe> ERRO: 2019/12/26 23:04:42.747945 plugins: problem loading: no such file or directory
yesterday at 5:04 PM <probe> INFO: 2019/12/26 23:04:44.682348 Publish loop for 127.0.0.1 starting
yesterday at 5:04 PM <probe> WARN: 2019/12/26 23:04:46.161543 Docker reporter took longer than 1s
yesterday at 5:04 PM <probe> WARN: 2019/12/26 23:04:46.901911 Docker reporter took 2.1101688s (longer than 1s)
yesterday at 5:43 PM time="2019-12-26T23:43:33Z" level=info msg="publishing to: 127.0.0.1:4040"
yesterday at 5:43 PM <probe> INFO: 2019/12/26 23:43:33.701381 Basic authentication disabled
yesterday at 5:43 PM <probe> INFO: 2019/12/26 23:43:33.851565 command line args: --mode=probe --probe.docker=true --weave=false
yesterday at 5:43 PM <probe> INFO: 2019/12/26 23:43:33.851906 probe starting, version 8b1296c8, ID 7a11d3358dee304e
yesterday at 5:43 PM <app> INFO: 2019/12/26 23:43:33.853106 app starting, version 8b1296c8, ID 4fd65abab5d76bca
yesterday at 5:43 PM <app> INFO: 2019/12/26 23:43:33.853292 command line args: --mode=app --probe.docker=true --weave=false
yesterday at 5:43 PM <app> INFO: 2019/12/26 23:43:33.865569 Basic authentication disabled
yesterday at 5:43 PM <app> INFO: 2019/12/26 23:43:33.867525 listening on :4040
yesterday at 5:43 PM <probe> WARN: 2019/12/26 23:43:34.337132 Error setting up the eBPF tracker, falling back to proc scanning: cannot open kprobe_events: open /sys/kernel/debug/tracing/kprobe_events: no such file or directory
yesterday at 5:43 PM <probe> ERRO: 2019/12/26 23:43:34.341401 Docker: problem with bridge docker0: route ip+net: no such network interface
yesterday at 5:43 PM <probe> ERRO: 2019/12/26 23:43:34.341672 plugins: problem loading: no such file or directory
yesterday at 5:43 PM <probe> INFO: 2019/12/26 23:43:34.341883 Control connection to 127.0.0.1 starting
yesterday at 5:43 PM <probe> INFO: 2019/12/26 23:43:35.797625 Publish loop for 127.0.0.1 starting
yesterday at 5:43 PM <probe> WARN: 2019/12/26 23:43:36.591796 Dropping report to 127.0.0.1
yesterday at 6:04 PM time="2019-12-27T00:04:21Z" level=info msg="publishing to: 127.0.0.1:4040"
yesterday at 6:04 PM <probe> INFO: 2019/12/27 00:04:21.229327 Basic authentication disabled
yesterday at 6:04 PM <app> INFO: 2019/12/27 00:04:21.458645 app starting, version 8b1296c8, ID 2c6fe4aaf87bbaa4
yesterday at 6:04 PM <app> INFO: 2019/12/27 00:04:21.458690 command line args: --mode=app --probe.docker=true --weave=false
yesterday at 6:04 PM <app> INFO: 2019/12/27 00:04:21.459435 Basic authentication disabled
yesterday at 6:04 PM <probe> INFO: 2019/12/27 00:04:21.459849 command line args: --mode=probe --probe.docker=true --weave=false
yesterday at 6:04 PM <probe> INFO: 2019/12/27 00:04:21.459886 probe starting, version 8b1296c8, ID 2dbbad81a98dbaa8
yesterday at 6:04 PM <app> INFO: 2019/12/27 00:04:21.466747 listening on :4040
yesterday at 6:04 PM <probe> WARN: 2019/12/27 00:04:21.690676 Error setting up the eBPF tracker, falling back to proc scanning: cannot open kprobe_events: open /sys/kernel/debug/tracing/kprobe_events: no such file or directory
yesterday at 6:04 PM <probe> INFO: 2019/12/27 00:04:21.744805 Control connection to 127.0.0.1 starting
yesterday at 6:04 PM <probe> ERRO: 2019/12/27 00:04:21.783629 Docker: problem with bridge docker0: route ip+net: no such network interface
yesterday at 6:04 PM <probe> ERRO: 2019/12/27 00:04:21.792562 plugins: problem loading: no such file or directory
yesterday at 6:04 PM <probe> INFO: 2019/12/27 00:04:24.892602 Publish loop for 127.0.0.1 starting
yesterday at 6:04 PM <probe> WARN: 2019/12/27 00:04:25.281651 Dropping report to 127.0.0.1
yesterday at 6:04 PM <probe> WARN: 2019/12/27 00:04:26.064321 Dropping report to 127.0.0.1

commented

Bueller? ...