Currently remote and local build environments are very different. Remote builds are executed in a remote execution container and local builds are executed on the host system. Since the build relies on certain system libraries (ex. glibc), the inputs of the build will change between local and remote invocations.

To workaround this, we may be able to spin up a remote execution container and call Bazel inside of the container, ex in SCons:

if local_mode:

  run_inside_docker_container("bazel build --config=local //...")

else:

  subprocess.run("bazel build //...")