fix bolt tasks with docker_exp transport #258
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tldr; #257 broke running bolt commands against docker_exp provisioned containers
Behind the scenes, the bolt docker transport uses
docker cp
to upload and dowload files to the containers.Unfortunately, we're using
--tmpfs /tmp
when creating containers, sodocker cp
is unable to upload or download to that path (or any tmpfs path). Technically it's uploading files to the container filesystem, but...From docker cp documentation corner cases:
Ultimately the problem needs to be solved in the bolt docker transport, but that's a much harder problem to solve. For now, not mounting tmpfs fixes this problem.