tools: toolchain: avoid docker-provided /tmp

On at least one system, using the container's /tmp as provided by docker
results in spurious EINVALs during aio:

INFO  2018-12-27 09:54:08,997 [shard 0] gossip - Feature ROW_LEVEL_REPAIR is enabled
unknown location(0): fatal error: in "test_write_many_range_tombstones": storage_io_error: Storage I/O error: 22: Invalid argument
seastar/tests/test-utils.cc(40): last checkpoint

The setup is overlayfs over xfs.

To avoid this problem, pass through the host's /tmp to the container.
Using --tmpfs would be better, but it's not possible to guess a good size
as the amount of temporary space needed depends on build concurrency.
Message-Id: <20181227101345.11794-1-avi@scylladb.com>
This commit is contained in:
Avi Kivity
2018-12-27 12:13:45 +02:00
committed by Duarte Nunes
parent 2c4a732735
commit b349e11aba

View File

@@ -1,3 +1,3 @@
#!/bin/bash
docker run --sig-proxy=true --rm -u "$(id -u):$(id -g)" --cap-add SYS_PTRACE -v "$PWD:$PWD" -w "$PWD" "$(<tools/toolchain/image)" "$@"
docker run --sig-proxy=true --rm -u "$(id -u):$(id -g)" --cap-add SYS_PTRACE -v "$PWD:$PWD" -v /tmp:/tmp -w "$PWD" "$(<tools/toolchain/image)" "$@"