diff options
| author | David Tolnay <dtolnay@chromium.org> | 2019-01-23 12:31:05 -0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-01-24 00:51:51 -0800 |
| commit | 5c8dae6ad7829b2db5317e0431d0ab2de5a9d725 (patch) | |
| tree | 2dbf697d75d981c1664273a957355acaf078bffa /tpm2-sys/build.rs | |
| parent | d3144f7a52608d5295dd5bf8edc4f3d76ae4ad82 (diff) | |
| download | crosvm-5c8dae6ad7829b2db5317e0431d0ab2de5a9d725.tar crosvm-5c8dae6ad7829b2db5317e0431d0ab2de5a9d725.tar.gz crosvm-5c8dae6ad7829b2db5317e0431d0ab2de5a9d725.tar.bz2 crosvm-5c8dae6ad7829b2db5317e0431d0ab2de5a9d725.tar.lz crosvm-5c8dae6ad7829b2db5317e0431d0ab2de5a9d725.tar.xz crosvm-5c8dae6ad7829b2db5317e0431d0ab2de5a9d725.tar.zst crosvm-5c8dae6ad7829b2db5317e0431d0ab2de5a9d725.zip | |
kokoro: Avoid docker build from stdin to support COPY
Under the old command, the build would fail with:
Step 15/25 : COPY pkgconfig/* /usr/lib/pkgconfig
COPY failed: no source files were specified
The Docker documentation at
https://docs.docker.com/v18.03/engine/reference/builder/
explains:
Note: If you build using STDIN (docker build - < somefile), there is
no build context, so COPY cant be used.
TEST=it built successfully
Change-Id: I4d9fcb085009f4a47d7caecabf6eb711f5cab6b7
Reviewed-on: https://chromium-review.googlesource.com/1431356
Commit-Ready: David Tolnay <dtolnay@chromium.org>
Tested-by: David Tolnay <dtolnay@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Diffstat (limited to 'tpm2-sys/build.rs')
0 files changed, 0 insertions, 0 deletions