After I run the docker-compose of this project on my computer, I have a problem when I call it under a project.

[liushuai05]

Please forgive me for being a novice at bazel. I copied the entire docker-compose directory of this project to my computer, and then executed run.sh. Yes, it worked. Here is a log of its work.

$ ./run.sh 
Registering automatic unmount for volumes/worker-fuse-ubuntu22-04/build
+ sudo fusermount -u volumes/worker-fuse-ubuntu22-04/build
fusermount: failed to unmount /home/xxx/docker-compose/Buildbarn/volumes/worker-fuse-ubuntu22-04/build: Invalid argument
+ true
+ sudo rm -rf volumes/bb volumes/worker-fuse-ubuntu22-04 volumes/worker-hardlinking-ubuntu22-04
+ mkdir -p volumes
+ mkdir -m 0777 volumes/worker-fuse-ubuntu22-04 volumes/worker-fuse-ubuntu22-04/build volumes/worker-fuse-ubuntu22-04/cas volumes/worker-fuse-ubuntu22-04/cas/persistent_state
+ mkdir -m 0777 volumes/worker-hardlinking-ubuntu22-04 volumes/worker-hardlinking-ubuntu22-04/build volumes/worker-hardlinking-ubuntu22-04/cas volumes/worker-hardlinking-ubuntu22-04/cas/persistent_state
+ mkdir -m 0700 volumes/worker-fuse-ubuntu22-04/cache volumes/worker-hardlinking-ubuntu22-04/cache
+ mkdir -p volumes/storage-ac-0/persistent_state volumes/storage-ac-1/persistent_state volumes/storage-cas-0/persistent_state volumes/storage-cas-1/persistent_state
+ chmod 0700 volumes/storage-ac-0/ volumes/storage-ac-0/persistent_state volumes/storage-ac-1/ volumes/storage-ac-1/persistent_state volumes/storage-cas-0/ volumes/storage-cas-0/persistent_state volumes/storage-cas-1/ volumes/storage-cas-1/persistent_state
[+] Running 10/10
 ✔ Container buildbarn-runner-installer-1                Created                                              0.0s 
 ✔ Container buildbarn-scheduler-1                       Created                                              0.0s 
 ✔ Container buildbarn-storage-1-1                       Created                                              0.0s 
 ✔ Container buildbarn-frontend-1                        Created                                              0.0s 
 ✔ Container buildbarn-worker-hardlinking-ubuntu22-04-1  Created                                              0.0s 
 ✔ Container buildbarn-browser-1                         Created                                              0.0s 
 ✔ Container buildbarn-worker-fuse-ubuntu22-04-1         C...                                                 0.0s 
 ✔ Container buildbarn-runner-fuse-ubuntu22-04-1         C...                                                 0.0s 
 ✔ Container buildbarn-storage-0-1                       Created                                              0.0s 
 ✔ Container buildbarn-runner-hardlinking-ubuntu22-04-1  Created                                              0.0s 
Attaching to browser-1, frontend-1, runner-fuse-ubuntu22-04-1, runner-hardlinking-ubuntu22-04-1, runner-installer-1, scheduler-1, storage-0-1, storage-1-1, worker-fuse-ubuntu22-04-1, worker-hardlinking-ubuntu22-04-1
worker-hardlinking-ubuntu22-04-1  | 2025/06/04 08:21:48 Worker {"datacenter":"linkoping","hostname":"ubuntu-worker.example.com","rack":"4","slot":"15","thread":"0"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-hardlinking-ubuntu22-04-1  | 2025/06/04 08:21:48 Worker {"datacenter":"linkoping","hostname":"ubuntu-worker.example.com","rack":"4","slot":"15","thread":"2"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-hardlinking-ubuntu22-04-1  | 2025/06/04 08:21:48 Worker {"datacenter":"linkoping","hostname":"ubuntu-worker.example.com","rack":"4","slot":"15","thread":"3"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-hardlinking-ubuntu22-04-1  | 2025/06/04 08:21:48 Worker {"datacenter":"linkoping","hostname":"ubuntu-worker.example.com","rack":"4","slot":"15","thread":"1"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-hardlinking-ubuntu22-04-1  | 2025/06/04 08:21:48 Worker {"datacenter":"linkoping","hostname":"ubuntu-worker.example.com","rack":"4","slot":"15","thread":"4"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-hardlinking-ubuntu22-04-1  | 2025/06/04 08:21:48 Worker {"datacenter":"linkoping","hostname":"ubuntu-worker.example.com","rack":"4","slot":"15","thread":"6"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-hardlinking-ubuntu22-04-1  | 2025/06/04 08:21:48 Worker {"datacenter":"linkoping","hostname":"ubuntu-worker.example.com","rack":"4","slot":"15","thread":"5"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-hardlinking-ubuntu22-04-1  | 2025/06/04 08:21:48 Worker {"datacenter":"linkoping","hostname":"ubuntu-worker.example.com","rack":"4","slot":"15","thread":"7"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:48 Reinitializing data store, as persistent state was not found
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:48 Worker {"datacenter":"amsterdam","hostname":"ubuntu-worker.example.com","rack":"3","slot":"10","thread":"4"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:48 Worker {"datacenter":"amsterdam","hostname":"ubuntu-worker.example.com","rack":"3","slot":"10","thread":"7"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:48 Worker {"datacenter":"amsterdam","hostname":"ubuntu-worker.example.com","rack":"3","slot":"10","thread":"0"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:48 Worker {"datacenter":"amsterdam","hostname":"ubuntu-worker.example.com","rack":"3","slot":"10","thread":"3"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:48 Worker {"datacenter":"amsterdam","hostname":"ubuntu-worker.example.com","rack":"3","slot":"10","thread":"2"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:48 Worker {"datacenter":"amsterdam","hostname":"ubuntu-worker.example.com","rack":"3","slot":"10","thread":"6"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:48 Worker {"datacenter":"amsterdam","hostname":"ubuntu-worker.example.com","rack":"3","slot":"10","thread":"1"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:48 Worker {"datacenter":"amsterdam","hostname":"ubuntu-worker.example.com","rack":"3","slot":"10","thread":"5"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
runner-installer-1                | /bb
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:48 Unimplemented opcode OPCODE-52
runner-installer-1 exited with code 0
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:48 Worker {"datacenter":"amsterdam","hostname":"ubuntu-worker.example.com","rack":"3","slot":"10","thread":"5"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:49 Worker {"datacenter":"amsterdam","hostname":"ubuntu-worker.example.com","rack":"3","slot":"10","thread":"1"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-hardlinking-ubuntu22-04-1  | 2025/06/04 08:21:49 Worker {"datacenter":"linkoping","hostname":"ubuntu-worker.example.com","rack":"4","slot":"15","thread":"2"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"
worker-fuse-ubuntu22-04-1         | 2025/06/04 08:21:49 Worker {"datacenter":"amsterdam","hostname":"ubuntu-worker.example.com","rack":"3","slot":"10","thread":"7"}: rpc error: code = Unavailable desc = Worker failed readiness check: connection error: desc = "transport: Error while dialing: dial unix /worker/runner: connect: no such file or directory"

# ps：There is no output until here, which means it may no longer report an error.
w Enable Watch

http://localhost:7982:

The following is the configuration in my project:

# .bazelrc
# Enable Bzlmod for every Bazel command
common --enable_bzlmod
# iBazel 优化配置
build:ibazel --remote_cache=grpc://127.0.0.1:8980
build:ibazel --remote_executor=grpc://127.0.0.1:8980

# build:ibazel --remote_instance_name=ji_an
# build:ibazel --remote_instance_name=ji_an
build:ibazel --remote_instance_name=fuse
build:ibazel --local_ram_resources=HOST_RAM*0.8
build:ibazel --local_cpu_resources=HOST_CPUS-1
# build:ibazel --run_output=true
build:ibazel  --features=race
build:ibazel --watchfs
build:ibazel --remote_upload_local_results=true   
build:ibazel --remote_accept_cached=true
build:ibazel --experimental_fetch_all_coverage_outputs 
build:ibazel --experimental_split_coverage_postprocessing

# 显示错误
build:ibazel --verbose_failures

I encountered an error when I executed bazel build //:goravel --config=ibazel ：

$ bazel build //:goravel  --config=ibazel
WARNING: Option 'local_ram_resources' is deprecated: --local_ram_resources is deprecated, please use --local_resources=memory= instead.
WARNING: Option 'local_cpu_resources' is deprecated: --local_cpu_resources is deprecated, please use --local_resources=cpu= instead.
INFO: Invocation ID: b46610ad-8666-4966-812e-9dca48a5f6ea
WARNING: Option 'local_ram_resources' is deprecated: --local_ram_resources is deprecated, please use --local_resources=memory= instead.
WARNING: Option 'local_cpu_resources' is deprecated: --local_cpu_resources is deprecated, please use --local_resources=cpu= instead.
INFO: Analyzed target //:goravel (0 packages loaded, 0 targets configured).
ERROR: /home/xxx/.cache/bazel/_bazel_xxx/34fc8b882affe2a1da1ff739219c1d45/external/gazelle++go_deps+io_opentelemetry_go_otel/internal/attribute/BUILD.bazel:3:11: GoCompilePkg external/gazelle++go_deps+io_opentelemetry_go_otel/internal/attribute/attribute.a failed: (Exit 34): UNAVAILABLE: No workers exist for instance name prefix "fuse" platform {}
java.io.IOException: io.grpc.StatusRuntimeException: UNAVAILABLE: No workers exist for instance name prefix "fuse" platform {}
        at com.google.devtools.build.lib.remote.GrpcRemoteExecutor.executeRemotely(GrpcRemoteExecutor.java:241)
        at com.google.devtools.build.lib.remote.RemoteExecutionService.executeRemotely(RemoteExecutionService.java:1987)
        at com.google.devtools.build.lib.remote.RemoteSpawnRunner.lambda$exec$2(RemoteSpawnRunner.java:313)
        at com.google.devtools.build.lib.remote.Retrier.execute(Retrier.java:245)
        at com.google.devtools.build.lib.remote.RemoteRetrier.execute(RemoteRetrier.java:120)
        at com.google.devtools.build.lib.remote.RemoteRetrier.execute(RemoteRetrier.java:109)
        at com.google.devtools.build.lib.remote.RemoteSpawnRunner.exec(RemoteSpawnRunner.java:278)
        at com.google.devtools.build.lib.exec.AbstractSpawnStrategy.exec(AbstractSpawnStrategy.java:161)
        at com.google.devtools.build.lib.exec.AbstractSpawnStrategy.exec(AbstractSpawnStrategy.java:121)
        at com.google.devtools.build.lib.exec.SpawnStrategyResolver.exec(SpawnStrategyResolver.java:45)
        at com.google.devtools.build.lib.analysis.actions.SpawnAction.execute(SpawnAction.java:253)
        at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.executeAction(SkyframeActionExecutor.java:1177)
        at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.run(SkyframeActionExecutor.java:1082)
        at com.google.devtools.build.lib.skyframe.ActionExecutionState.runStateMachine(ActionExecutionState.java:166)
        at com.google.devtools.build.lib.skyframe.ActionExecutionState.getResultOrDependOnFuture(ActionExecutionState.java:95)
        at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor.executeAction(SkyframeActionExecutor.java:566)
        at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.checkCacheAndExecuteIfNeeded(ActionExecutionFunction.java:946)
        at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.computeInternal(ActionExecutionFunction.java:377)
        at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.compute(ActionExecutionFunction.java:218)
        at com.google.devtools.build.skyframe.AbstractParallelEvaluator$Evaluate.run(AbstractParallelEvaluator.java:467)
        at com.google.devtools.build.lib.concurrent.AbstractQueueVisitor$WrappedRunnable.run(AbstractQueueVisitor.java:435)
        at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteAction.compute(ForkJoinTask.java:1735)
        at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteAction.compute(ForkJoinTask.java:1726)
        at java.base/java.util.concurrent.ForkJoinTask$InterruptibleTask.exec(ForkJoinTask.java:1650)
        at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:507)
        at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1394)
        at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1970)
        at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:187)
Caused by: io.grpc.StatusRuntimeException: UNAVAILABLE: No workers exist for instance name prefix "fuse" platform {}
        at io.grpc.Status.asRuntimeException(Status.java:533)
        at io.grpc.stub.ClientCalls$BlockingResponseStream.hasNext(ClientCalls.java:631)
        at com.google.devtools.build.lib.remote.GrpcRemoteExecutor.lambda$executeRemotely$2(GrpcRemoteExecutor.java:175)
        at com.google.devtools.build.lib.remote.Retrier.execute(Retrier.java:245)
        at com.google.devtools.build.lib.remote.RemoteRetrier.execute(RemoteRetrier.java:120)
        at com.google.devtools.build.lib.remote.RemoteRetrier.execute(RemoteRetrier.java:109)
        at com.google.devtools.build.lib.remote.GrpcRemoteExecutor.lambda$executeRemotely$3(GrpcRemoteExecutor.java:146)
        at com.google.devtools.build.lib.remote.util.Utils.refreshIfUnauthenticated(Utils.java:532)
        at com.google.devtools.build.lib.remote.GrpcRemoteExecutor.executeRemotely(GrpcRemoteExecutor.java:144)
        ... 27 more
Target //:goravel failed to build
INFO: Elapsed time: 3.218s, Critical Path: 3.00s
INFO: 9 processes: 8 action cache hit, 9 internal.
ERROR: Build did NOT complete successfully

I hope I can get help. Thank you very much.

[stagnation]

You have asked Bazel to execute on the "fuse" workers with an empty set of platforms properties (The --remote_instance_name=fuse flag).

UNAVAILABLE: No workers exist for instance name prefix "fuse" platform {}

The "fuse" part is right, as you can see in the left column in the scheduler view (thanks for including that)!
But the next column has the platforms properites: OsFamily=Linux, ContainerImage=.....
Which is important for dispatch.

You should instead have Bazel ask for "fuse" works with those two platform properties:
Prefereably by setting up a toolchain: https://github.com/buildbarn/bb-deployments/blob/master/.bazelrc#L36
Or you can tinker around without a toolchain to try it out. But for production you should use a toolchain: https://github.com/buildbarn/bb-deployments?tab=readme-ov-file#bazel-without-a-remote-toolchain

[liushuai05]

You have asked Bazel to execute on the "fuse" workers with an empty set of platforms properties (The --remote_instance_name=fuse flag).

UNAVAILABLE: No workers exist for instance name prefix "fuse" platform {}

The "fuse" part is right, as you can see in the left column in the scheduler view (thanks for including that)! But the next column has the platforms properites: OsFamily=Linux, ContainerImage=..... Which is important for dispatch.

You should instead have Bazel ask for "fuse" works with those two platform properties: Prefereably by setting up a toolchain: https://github.com/buildbarn/bb-deployments/blob/master/.bazelrc#L36 Or you can tinker around without a toolchain to try it out. But for production you should use a toolchain: https://github.com/buildbarn/bb-deployments?tab=readme-ov-file#bazel-without-a-remote-toolchain

I completely copied the tools folder into my project, and then added platforms and rules_cc to MODULE.bazel. Running build still reported the error failed _ precondition: there are no workers whose instance names are prefixed with "fuse”platform {}. I think your MODULE.bazelz still contains a lot of content, and there are some patches of other packages, such as bb_worker. Do I have to include this information in the project to work properly? If all these contents are included in my project, it will change too much for my project.

#.bazelrc
# Enable Bzlmod for every Bazel command
common --enable_bzlmod
# iBazel 优化配置
 build:ibazel --remote_cache=grpc://127.0.0.1:8980
build:ibazel --remote_executor=grpc://127.0.0.1:8980
#build:ibazel  --remote_cache=grpc://10.10.10.110:9092  
# build:ibazel --remote_instance_name=ji_an
# build:ibazel --remote_instance_name=ji_an
build:ibazel --remote_instance_name=fuse
build:ibazel --local_ram_resources=HOST_RAM*0.8
build:ibazel --local_cpu_resources=HOST_CPUS-1
# build:ibazel --run_output=true
build:ibazel  --features=race
build:ibazel --watchfs
build:ibazel --remote_upload_local_results=true   
build:ibazel --remote_accept_cached=true
build:ibazel --experimental_fetch_all_coverage_outputs 
build:ibazel --experimental_split_coverage_postprocessing

# 显示错误
build:ibazel --verbose_failures

# your host machine.
build:ibazel --jobs=64
# Make sure that the remote execution platform and the matching toolchains
# take precedence over the other definitions in the WORKSPACE file.
build:ibazel --extra_toolchains=//tools/remote-toolchains:all

# When running Ubuntu 22.04 executors.
build:remote-ubuntu-22-04 --config=ibazel
build:remote-ubuntu-22-04 --extra_execution_platforms=//tools/remote-toolchains:ubuntu-act-22-04-platform

#MODULE.bazel
###############################################################################
# Bazel now uses Bzlmod by default to manage external dependencies.
# Please consider migrating your external dependencies from WORKSPACE to MODULE.bazel.
#
# For more details, please check https://github.com/bazelbuild/bazel/issues/18958
###############################################################################
module(
    name = "goravel",  # 替换为你的项目名称
    version = "0.1.0",
)

bazel_dep(name = "rules_go", version = "0.51.0")
bazel_dep(name = "gazelle", version = "0.40.0")
bazel_dep(name = "bazel_skylib", version = "1.5.0")
bazel_dep(name = "platforms", version = "0.0.11")
bazel_dep(name = "rules_cc", version = "0.0.17")

go_deps = use_extension("@gazelle//:extensions.bzl", "go_deps")
go_deps.from_file(go_mod = "//:go.mod")
use_repo(go_deps, "com_github_eclipse_paho_mqtt_golang", "com_github_fogleman_gg", "com_github_go_pay_gopay", "com_github_go_redis_redis", "com_github_gomodule_redigo", "com_github_goravel_example_proto", "com_github_goravel_framework", "com_github_goravel_gin", "com_github_gorilla_websocket", "com_github_jinzhu_copier", "com_github_joho_godotenv", "com_github_liu_cn_json_filter", "com_github_mitchellh_mapstructure", "com_github_nfnt_resize", "com_github_opentracing_opentracing_go", "com_github_pkg_errors", "com_github_redisbloom_redisbloom_go", "com_github_shakinm_xlsreader", "com_github_shopspring_decimal", "com_github_silenceper_wechat_v2", "com_github_sony_sonyflake", "com_github_spf13_cast", "com_github_stretchr_testify", "com_github_sunary_sqlize", "com_github_swaggo_http_swagger", "com_github_swaggo_swag", "com_github_tencentyun_cos_go_sdk_v5", "com_github_uber_jaeger_client_go", "com_github_xuri_excelize_v2", "io_gorm_driver_clickhouse", "io_gorm_gorm", "org_golang_google_grpc")

go_sdk = use_extension("@rules_go//go:extensions.bzl", "go_sdk")

# Download an SDK for the host OS & architecture as well as common remote execution platforms.
go_sdk.download(version = "1.23.0")

# Alternately, download an SDK for a fixed OS/architecture.
go_sdk.download(
    goarch = "amd64",
    goos = "linux",
    version = "1.23.0",
)

# Register the Go SDK installed on the host.
# go_sdk.host()

[moroten]

Try to use --config=remote-ubuntu-22-04 to get the execution platform registered.

[liushuai05]

Try to use --config=remote-ubuntu-22-04 to get the execution platform registered.

Yes, I tried to execute it, and it told me a lot of error messages. It seems that you still need to get it to other folders or rely on it to work normally (I didn't use the source code of buildbarn/bb-deployments to execute it directly, but my project adopted goravel/goravel, and of course I made it compatible with bazel), such as other configurations in the module, MODULE.bazel and so on. I don't want to introduce too many documents that have nothing to do with the project, because there are others who maintain this project with me.

$ bazel build //:goravel --config=remote-ubuntu-22-04
WARNING: Option 'local_ram_resources' is deprecated: --local_ram_resources is deprecated, please use --local_resources=memory= instead.
WARNING: Option 'local_cpu_resources' is deprecated: --local_cpu_resources is deprecated, please use --local_resources=cpu= instead.
INFO: Invocation ID: 3f1b2004-2759-4e72-86ac-2ef932b7a9a5
WARNING: For repository 'bazel_skylib', the root module requires module version bazel_skylib@1.5.0, but got bazel_skylib@1.7.1 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: Option 'local_ram_resources' is deprecated: --local_ram_resources is deprecated, please use --local_resources=memory= instead.
WARNING: Option 'local_cpu_resources' is deprecated: --local_cpu_resources is deprecated, please use --local_resources=cpu= instead.
ERROR: no such package '@@[unknown repo 'remote_config_cc' requested from @@]//': The repository '@@[unknown repo 'remote_config_cc' requested from @@]' could not be resolved: No repository visible as '@remote_config_cc' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration
ERROR: /home/xxx/.cache/bazel/_bazel_edison/34fc8b882affe2a1da1ff739219c1d45/external/rules_cc+/cc/private/toolchain/BUILD:96:14: Target '@@rules_cc+//cc/private/toolchain:compiler' depends on toolchain '@@[unknown repo 'remote_config_cc' requested from @@]//:cc-compiler-k8', which cannot be found: no such package '@@[unknown repo 'remote_config_cc' requested from @@]//': The repository '@@[unknown repo 'remote_config_cc' requested from @@]' could not be resolved: No repository visible as '@remote_config_cc' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration'
ERROR: /home/xxx/.cache/bazel/_bazel_edison/34fc8b882affe2a1da1ff739219c1d45/external/protobuf+/build_defs/BUILD.bazel:27:29: errors encountered resolving select() keys for @@protobuf+//build_defs:config_msvc
ERROR: /home/xxx/.cache/bazel/_bazel_edison/34fc8b882affe2a1da1ff739219c1d45/external/protobuf+/BUILD.bazel:232:10: errors encountered resolving select() keys for @@protobuf+//:protoc
ERROR: Analysis of target '//:goravel' failed; build aborted: Analysis failed
INFO: Elapsed time: 7.174s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully

[moroten]

Unfortunately, it is implemented as a local_path_override so you will need to use local_path_override in your own MODULE.bazel as well.