Matthias Radestock
Matthias Radestock
does `127.0.0.1:4040` work?
btw, this does work just fine for me. - Docker version? - docker-compose version? - v1 or v2 yaml?
works fine for me on Linux with v2 and ``` $ docker version Client: Version: 17.06.1-ce API version: 1.30 Go version: go1.8.3 Git commit: 874a737 Built: Thu Aug 17 22:51:12...
``` $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 8cb551a5e597 weaveworks/scope:1.6.4 "/home/weave/entry..." 21 seconds ago Up 9 seconds tmp_scope_1 $ docker-compose ps Name Command State Ports ------------------------------------------------------------...
perhaps try adding the equivalent of `-p 0.0.0.0:4040:4040` to the compose file. [That's what the `scope` script does on a mac](https://github.com/weaveworks/scope/blob/v1.6.3/scope#L190).
The docker-compose docs are complicated enough as is, so I'd rather avoid having multiple variants. But I guess we have no choice :( Running with `--privileged: true` instead of running...
To be clear, we are talking about k8s labels here, right?
It just occurred to me that we shouldn't just focus on ECS here, e.g. for hosts that are EC2 VMs, the Scope details panel for the host could link to...
> Specific services perhaps? RDS has just come up in the context of Weave Cloud troubleshooting.
Is this a dup of #1143?