Port to arm64

[vielmetti]

In envoyproxy/envoy#1861 (comment) , @moderation is attempting a port of Envoy to arm64. After getting pretty far they got stuck in a dependency on lyft/protoc-gen-validate.

I suspect that one of the issues is a hardcoded dependency to arm64 binaries in the build_container script at

https://github.com/lyft/protoc-gen-validate/blob/master/scripts/build_container.sh#L18
https://github.com/lyft/protoc-gen-validate/blob/master/scripts/build_container.sh#L38

However there may be more issues lurking; using this issue to track them.

[rodaine]

Hm, that script is only run in the context of building the Docker image for the purposes of testing. However, for Envoy and in general, PGV uses Bazel. I'd look at those build rules and ensure that they are compatible with arm64. Will be glad to help if you can pinpoint the issues!

[moderation]

As @rodaine points out the container build script isn't the source of the problem. I expect the issue is somewhere in https://github.com/lyft/protoc-gen-validate/tree/master/bazel. There are bunch of work arounds for since fixed issues and some of the dependencies are quite old. Still digging.

[akonradi]

@moderation and I chatted offline and it looks like the current blocker is a bug in rules_go repository's support for arm64 go toolchain versions. The issue is that if repository_ctx.os.name is 'linux', there's no way to set the host as linux_arm64 - it defaults to linux_amd64. See
https://github.com/bazelbuild/rules_go/blob/3b103d6954cd4508e1f63c8e2ea57bda18d98bcf/go/private/sdk.bzl#L31-L37

[vielmetti]

The upstream issue on bazel has been resolved.