tree 02c29ef3fd24b269c89f60e5259a0ee7ec391080
parent ffc70804987bf5c1ce32f8fee5bb54ad3da3e092
author Geoffrey Martin-Noble <gcmn@google.com> 1595880259 -0700
committer GitHub <noreply@github.com> 1595880259 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfHzNDCRBK7hj4Ov3rIwAAdHIIAHD+nAXMVju78tkCGr8VKdrc
 xxTkSLr4OU7Ejx3ZjKw8Cv+RxPAa02Mu7K6Aw9M/fQRiEJ5bd+T6fyXPb0kgIqNU
 Jg+YO7GxmoousXiRpSBwuJPX3JiLANMTTzhhsQKyeSLvP/f4f43PuZK0TKsKq3Zt
 fI8EU0rpAu0O3etrveeH2LaERfL3lMznvqBPs/dE3AEvesZi0UM8VRM8MKHMBl/8
 Ow2pgxDY8Z66oXBAqmCDUI65nv7xu3Aq57nRISaPwYwE3PT2vNbhdAZzBVbmsMIz
 87d/G/s9/oJmZZLAoj+TxAskx0b7UombvnClH4qw0CoDoexQIag3S/psWiItkUA=
 =vaXg
 -----END PGP SIGNATURE-----
 

Avoid running docker builds as root (#2663)

Instead of mounting the user's existing Bazel cache, create a fake home
directory under the Kokoro root directory.

This is another attempt at https://github.com/google/iree/pull/2566
which had to be rolled back for the Bazel integrations build because it
made it three times slower. It turns out the root cause there is that
the docker container volumes are by default mounted in /tmpfs which on
Kokoro is a local-ssd. The home directory, on the other hand, is a
persistent SSD. The integrations job is running Bazel with 64 cores,
which means it's IO bound. The difference turns out to be substantial.

Fixes https://github.com/google/iree/issues/2653

Tested:
Ran simulate_kokoro on the core build locally to confirm this doesn't
break RBE cloud credentials.
The integrations presubmit on this PR takes 20 minutes, as before.