Bazel build for rules_docker#java_image fails with "No matching toolchains found for types @bazel_tools//tools/cpp:toolchain_type. Maybe --incompatible_use_cc_configure_from_rules_cc has been flipped and there is no default C++ toolchain added in the WORKSPACE file"

[xushaoxiao]

Description of the bug:

While resolving toolchains for target //cover:cover_app_image.binary: No matching toolchains found for types @bazel_tools//tools/cpp:toolchain_type. Maybe --incompatible_use_cc_configure_from_rules_cc has been flipped and there is no default C++ toolchain added in the WORKSPACE file? See #10134 for details and migration instructions.

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

No response

Which operating system are you running Bazel on?

bazel build ...

What is the output of bazel info release?

5.1.1

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

INFO: Invocation ID: 3799285a-78e6-44e4-842b-138b573a0955
release 5.1.1-homebrew

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

ERROR: /Users/shaoxixu/Repos/big-gov-mono/cover/BUILD.bazel:91:11: While resolving toolchains for target //cover:cover_app_image.binary: No matching toolchains found for types @bazel_tools//tools/cpp:toolchain_type. Maybe --incompatible_use_cc_configure_from_rules_cc has been flipped and there is no default C++ toolchain added in the WORKSPACE file? See https://github.com/bazelbuild/bazel/issues/10134 for details and migration instructions.
ERROR: Analysis of target '//cover:cover_app_image' failed; build aborted: 
INFO: Elapsed time: 3.252s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded, 859 targets configured)
    Fetching @local_config_xcode; Building xcode-locator
    Fetching @com_github_google_go_containerregistry; fetching
    Fetching @com_github_pkg_errors; fetching

Have you found anything relevant by searching the web?

No response

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

No response

[sgowroji]

Hello @xushaoxiao, Did you try the workarounds mentioned in added issue. If still you are not resolved can you provide more details.

[tuananh]

Hello @xushaoxiao, Did you try the workarounds mentioned in added issue. If still you are not resolved can you provide more details.

that one works for go_image, what about java_image?

[comius]

cc @gravypod have there been changes in rules_docker? Could you investigate?

I'm not aware of any changes in Bazel that would have caused this.

[tuananh]

i rolled back to 0.22 and it works now. i guess i'll keeping using 0.22 for now

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

[xushaoxiao]

resolved, thanks.