Move installed binaries out of $CARGO_HOME #18
Conversation
The intent is to make the container workable with $CARGO_HOME mounted from the host, to preserve Cargo caches and the authentication token between container runs. If a container run invokes rustup, this may override the binaries moved to /usr/local/bin with freshly installed binaries in $CARGO_HOME/bin/. This is perfectly fine for incremental container images.
|
Why do you think this PR will be merged? |
Because it solves an acute problem for users of this container, in a clean and simple way, with no disadvantages known to me? |
Then rustup is the thing that needs to be changed! This is the official Docker image for the Rust programming language, and as such it should be have as "normally" as possible. Having rustup's proxy binaries in some random directory is not a normal thing to do. If you want to move these binaries out of the way, you're welcome to do that in your own image based off of the official one, or even make your own from scratch. |
This is a one-line fix for #17. The binaries, plus an
envfile which is only meaningful when$CARGO_HOMEis populated with binaries, are all that is installed there by the Docker image build.If a container run invokes rustup, this may override the binaries
moved to
/usr/local/binwith freshly installed binaries in$CARGO_HOME/bin/.This is perfectly fine for incremental container images.