I gather that it runs builds inside a chroot where the only available files are the dependencies you specified explicitly (including the compiler[1]), at least

I gather that it runs builds inside a chroot where the only available files are the dependencies you specified explicitly (including the compiler[1]), at least in "strict" mode[2]. Or else it must monitor what files are opened during the build step and fails the build if it saw an unexpected file being opened. It never explains any of this explicitly, but there are hints. [1], [2], [3]. [1] "Many rules also have additional attributes for rule-specific kinds of dependency, e.g. 'compiler'" -- http://bazel.io/docs/build-ref.html#types_of_dependencies http://bazel.io/docs/build-ref.html#types_of_dependencies [2] http://bazel.io/docs/build-encyclopedia.html#cc_binary.hdrs_check http://bazel.io/docs/build-encyclopedia.html#cc_binary.hdrs_... [3] "The build system runs tests in an isolated directory where only files listed as 'data' are available" -- http://bazel.io/docs/build-ref.html#data http://bazel.io/docs/build-ref.html#data Edit: A comment below seems to suggest that this is not the case: "Within Google we use a form of sandboxing to enforce that" (emphasis mine). -- https://news.ycombinator.com/item?id=9259147 https://news.ycombinator.com/item?id=9259147