alpine:edge - zipper failed: error executing PythonZipper

Description of the bug:

build failed with an error

ERROR: /tmp/bazel-release/src/BUILD:65:10: Building Python zip: //src:create_embedded_tools [for tool] failed: (Segmentation fault): zipper failed: error executing PythonZipper command (from target //src:create_embedded_tools) 
  (cd /tmp/bazel_T4NJjXRi/out/execroot/io_bazel && \
  exec env - \
    PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
  bazel-out/aarch64-opt-exec-ST-6c355c207781/bin/external/bazel_tools/third_party/ijar/zipper cC bazel-out/aarch64-opt-exec-ST-6c355c207781/bin/src/create_embedded_tools.zip @bazel-out/aarch64-opt-exec-ST-6c355c207781/bin/src/create_embedded_tools.zip-0.params)
# Configuration: 6353960f9aefe49bda3895b7f057d4581a1d16ff11d58597cd3ab4acd1d96b65
# Execution platform: //:default_host_platform
Target //src:bazel_nojdk failed to build
INFO: Elapsed time: 286.522s, Critical Path: 15.88s
INFO: 425 processes: 17 internal, 408 local.
ERROR: Build did NOT complete successfully

ERROR: Could not build Bazel

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

wget https://github.com/bazelbuild/bazel/releases/download/7.0.0-pre.20230530.3/bazel-7.0.0-pre.20230530.3-dist.zip
unzip bazel-7.0.0-pre.20230530.3-dist.zip
env JAVA_HOME=/usr/lib/jvm/java-11-openjdk \
       EXTRA_BAZEL_ARGS="--tool_java_runtime_version=local_jdk" \
       bash ./compile.sh

More info in the comment https://github.com/bazelbuild/bazel/issues/5891#issuecomment-1382582327

Which operating system are you running Bazel on?

alpine:edge

What is the output of bazel info release?

bazel-7.0.0-pre.20230530.3-dist.zip

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

bazel-7.0.0-pre.20230530.3-dist.zip

What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?

bazel-7.0.0-pre.20230530.3-dist.zip

Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response