-
Notifications
You must be signed in to change notification settings - Fork 693
Incompatibility with rules_docker and current rules_go #943
Comments
Actually I am also getting the following error as well with 0.8.0: $ bazel build //...
INFO: Build option --platforms has changed, discarding analysis cache.
ERROR: While resolving toolchains for target //:external_dns_image: no matching toolchains found for types @io_bazel_rules_docker//toolchains/docker:toolchain_type
ERROR: Analysis of target '//:external_dns_image' failed; build aborted: no matching toolchains found for types @io_bazel_rules_docker//toolchains/docker:toolchain_type
INFO: Elapsed time: 0.220s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded, 143 targets configured) When I am using the cross compilation flag: |
Let me add a bit of clarity. rules_docker 0.8.0 works sorta when I do not specify rules_docker 0.8.1 does not work at all ... |
cc @nlopezgi |
Here is the weird $ bazel build //:external_dns_image
ERROR: /Users/chlove/Workspace/src/github.com/kubernetes-incubator/external-dns/BUILD.bazel:37:1: every rule of type _app_layer implicitly depends upon the target '@gzip//:gzip', but this target could not be found because of: no such package '@gzip//': The repository '@gzip' could not be resolved
ERROR: Analysis of target '//:external_dns_image' failed; build aborted: no such package '@gzip//': The repository '@gzip' could not be resolved |
Hey @chrislovecnm , |
Both 0.8.0 and 0.8.1 do not work. So the changes are in the rules_go, or in rules_docker after rules docker 0.7.x. Also we have all the new challenges will how bazel loads the C++ toolchains as well. |
It is not the bazel version. Just went back to 0.23.1 and had the same problem. |
This seems to be an issue with the new rules_go, because I went back to 0.7 rules_docker. |
responded on the rules_go issue. |
It appears that the upstream rules_go bug is fixed: bazelbuild/rules_go#2089. |
@nlopezgi now that the upstream issue is resolved, what would be needed to retest this? It would be great to be able to remove this scary-looking blurb from the README.md: |
bazel version:
Note: I am using rules_go https://github.com/bazelbuild/rules_go/tree/8ea79bbd5e6ea09dc611c245d1dc09ef7ab7118a because I am trying to get cross compilation working again.
I am noticing an issue was introduced with the current 0.8.1 release. When using 0.8.1 and https://github.com/bazelbuild/rules_go/tree/8ea79bbd5e6ea09dc611c245d1dc09ef7ab7118a from rules_go I am getting the error:
With rules_docker 0.8.0 I do not get this error when I am not cross compiling. When I use
--platforms=@io_bazel_rules_go//go/toolchain:linux_amd64
, 0.8.0 does not work as well.I have tried to add the
docker_toolchain_configure
calls and also the calls to register the tool chains. Using thedocker_toolchain_configure
does not help. Using theregister_toolchains
call just give me a weird error that@gzip
does not exist.The repo that I am working out of is located here: https://github.com/chrislovecnm/external-dns/tree/work-on-bazel
The text was updated successfully, but these errors were encountered: