Open jasonbdly opened 1 week ago
Since this seems to be more closely related to the upstream bazel_lib package, I submitted an issue there as well: https://github.com/bazel-contrib/bazel-lib/issues/964. Hopefully this gets some discussion started about how Windows support could be added.
Yes, this needs to be fixed in bazel-lib before it can be fixed here.
FYI windows support here is close to non-existent as we don't have the resources to develop for windows. i would not expect this to work even if we fix zstd toolchain.
I'm working on migrating a bunch of disparate shell build scripts to Bazel. The project consists of a set of grpc servers written in Go and exposed as their own binaries, each of which are subsequently built into
Containerfile
images running on top ofdebian:bookworm-slim
, and spun up in a local Kubernetes cluster via Docker Desktop.The problem I'm running into occurs when attempting to build the
oci_image
target for any of these grpc servers (with the recommended toolchain_resolution_debug flag enabled):IIUC, it looks like
aspect_bazel_lib
doesn't provide a toolchain for zstd that works on Windows? Is this a legitimate support issue for Windows, or have I misconfigured something somewhere? Are there any workarounds I can attempt to use? Is there any additional information I can provide to narrow this down? This may be at least partially related to https://github.com/bazel-contrib/rules_oci/issues/714, but I'm not totally sure.Here's the relevant
BUILD
file for reference:And the
MODULE.bazel
file:The output from
bazelisk version
: