rbe_configs_gen fails if image has bazel as its entrypoint #1006
Description
Due to not specifying --entrypoint to docker create, the container is immediately stopped after attempting docker start. This additionally leads to a misleading error that makes it appear that the container was killed as part of the docker exec command.
Captured output:
2024/03/15 12:03:04 Running: 'docker exec -w /workdir/cpp_configs_project -e USE_BAZEL_VERSION=7.1.0 -e ABI_VERSION=clang -e BAZEL_COMPILER=clang -e BAZEL_TARGET_LIBC=glibc_2.19 -e BAZEL_TARGET_SYSTEM=x86_64-unknown-linux-gnu -e ABI_LIBC_VERSION=glibc_2.19 -e BAZEL_HOST_SYSTEM=i686-unknown-linux-gnu -e BAZEL_TARGET_CPU=k8 -e CC=clang -e CC_TOOLCHAIN_NAME=linux_gnu_x86 b6f5da053b2802fd5f887ba457a2efbaef7d147341c87d25fc4604f0043e26f5 /workdir/bazelisk build @local_config_cc//...'
2024/03/15 12:03:13 Output: Extracting Bazel installation...
Starting local Bazel server and connecting to it...
2024/03/15 12:03:13 Running: 'docker stop -t 0 b6f5da053b2802fd5f887ba457a2efbaef7d147341c87d25fc4604f0043e26f5'
2024/03/15 12:03:13 Config generation failed: Config generation failed: failed to generate C++ configs: Bazel was unable to build the C++ config generation targets in the toolchain container: exit status 137