some fixes for the new bare config example

[mostynb]

Here are a few proposed fixes for the bare example. It still doesn't quite work for me yet, I'm getting the following error:

ERROR: /home/user/.cache/bazel/_bazel_user/5dc217035a371a2209c1f6921a765276/external/zlib/BUILD.bazel:31:11 Executing genrule @zlib//:copy_public_headers failed (Exit 34). Note: Remote connection/protocol failed with: execution failed FAILED_PRECONDITION: No workers exist for instance "local" platform {"properties":[{"name":"OSFamily","value":"Linux"},{"name":"container-image","value":"docker://marketplace.gcr.io/google/rbe-ubuntu16-04@sha256:b516a2d69537cb40a7c6a7d92d0008abb29fba8725243772bdaf2c83f1be2272"}]}

[EdSchouten]

You’re likely getting the error because you are using Bazel Toolchains. For the bare deployment you should not, because the runner is not an Ubuntu 16.04 RBE container. You should either run Bazel on the same kind of system and use the auto-detected platform info, or write it manually.

[EdSchouten]

Whoops! Accidentally merged this and only saw afterwards that this added —config=ubuntu. That shouldn’t be in there.

[EdSchouten]

I just cleaned up the repo history a bit: the first and third commits in your PR have been merged. The second one (that changed --config) has been omitted.

[EdSchouten]

@mostynb Could you see what happens if you use what's in latest master, but with the --config=remote line removed? I don't think we need to pass in any --config now. That --config=remote part was just there to have all of the --spawn_strategy flags that were needed in the past.

[mickael-carl]

Also worth noting that an issue is present to document how to use platform properties: #20

[mostynb]

Could you see what happens if you use what's in latest master, but with the --config=remote line removed?

Yes, it works: #33

[EdSchouten]

Thanks for taking care of this!

[mostynb]

No problem- thanks for being so responsive!