Bryan Boreham

I don't think there is a way to request individual parameter changes via the yaml generator, so you'd need to capture the output and edit it, then re-apply to your...

Oh there is a helm chart but I don't use it myself. https://github.com/helm/charts/tree/master/stable/weave-scope

That’s a little terse. Can you do a differential diagnosis against the CI build which is working fine? Are you building inside the build container? (Eg by running `make`)

Suggest you take a look at what is installed by the build container, as a guide to what you’ll need on your host.

Note `make prog/scope` will give you the plain binary, built by a container.

If you install all dependencies on the host then `make prog/scope BUILD_IN_CONTAINER=false`.

`esc` is a dependency of the build. For the provided build process it is installed here: https://github.com/weaveworks/scope/blob/e6faa2ba4bf842bb81993a64232554c281ced644/backend/Dockerfile#L25

We do a couple of cross-platform builds in CI to check it doesn't break: https://github.com/weaveworks/scope/blob/e6faa2ba4bf842bb81993a64232554c281ced644/.circleci/config.yml#L116 Some features are stubbed out but I think that's based on OS rather than CPU.

> I want to cross-compile the arm architecture on x86_64. Is this feasible? The line I gave you does exactly that. > vendor/github.com/docker/docker/pkg/system/stat_linux.go:11:3: cannot use s.Rdev (type uint32) as type...

Thanks for your report. Scope's terminal is implemented using the [xterm](https://xtermjs.org/) module, and according to its description, "Screen reader support can be turned on using the `screenReaderMode` option". So, if...