Use create_dir_all for cargo directory. #908
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.
Use create_dir_all for cargo directory.
Cargo builds all intermediate directories to
CARGO_HOME
, if not present, and hard errors if it cannot. This differs from our behavior, where we silently ignore failures and only attempt to build the current directory (ignores errors if it actually exists). If using a rootful container engine, this means we create the cargo directory and it is owned by root. This only occurs if the package has no dependencies, another fix that usingcargo metadata
solved.An example of the hard failure shown as the following (some lines are omitted for brevity):
Cargo
Old Cross
Container Engine Runs as Root
Rootless Container Engine
New Cross
Container Engine Runs as Root
Rootless Container Engine
$ CROSS_CONTAINER_ENGINE=podman CARGO_HOME=/path/to/my/cargo ~/git/cross/target/debug/cross build Error: 0: could not run container 1: Permission denied (os error 13)