Yun Peng

@rickeylev Yes, porting the launcher to Linux and macOS shouldn't be too hard. There is no fundamental Windows specific dependencies.

Moving the //src/tools/launcher to its own repo is going to be very hard, because the launcher also depends on cc_libraries under //src/main/cpp/util. But I do think it's a good idea...

> I'm also fine with modifying this launcher-code in Bazel itself; I don't own it, so I'd like to know who we send PRs to for approval. I'm the original...

@petemounce Thanks! I filed an issue to track this: https://github.com/bazelbuild/continuous-integration/issues/1456

/cc @brandjon Can you help advise how to fix this?

FYI @uhthomas

@brandjon ping, do you have any idea what's happening here?

Since https://github.com/bazelbuild/bazel/commit/98d376faeb206f14838156ce4cb305ddbfce08fa is in Bazel 5.0, this means rules_docker has to fix this issue to be able to work with the next Bazel release.

> The linked commit (bazelbuild/bazel@98d376f) is from January 2021, over a year ago. Has it only recently been merged? If not, what has now caused this problem? Yes, the commit...

@gregestren To reproduce: ``` docker run -it --init gcr.io/bazel-public/ubuntu1804-java11 root@4f4a89faff2e:/# mkdir workdir root@4f4a89faff2e:/# cd workdir/ root@4f4a89faff2e:/workdir# git clone https://github.com/bazelbuild/rules_docker.git root@4f4a89faff2e:/workdir# cd rules_docker/ root@4f4a89faff2e:/workdir/rules_docker# export USE_BAZEL_VERSION=98d376faeb206f14838156ce4cb305ddbfce08fa root@4f4a89faff2e:/workdir/rules_docker# bazel build //tests/container:alpine_arch_ppc64le 2022/01/19...