docker-run.sh uses $HOME/.cargo for CARGO_HOME

[rob-solana]

Problem

Using CARGO_HOME set to HOME/.cargo for crates we want to build and run in CI isn't going to work nicely... Normally when doing that, we'd add CARGO_HOME/bin to the PATH. However, were we do that, we're likely to negate the value of using a docker image, which has pre-installed, specific versions of cargo, rust, etc.

Proposed Solution

The fix (to enable installing and running any random --bin crate during a build) has two parts:

1. have docker-run.sh not use $HOME/.cargo as CARGO_HOME, have it use the workspace or something else with predictable, controlled contents.
2. update our rust Dockerfiles to put $CARGO_HOME/bin on the PATH via an ENV directive (because using --env from docker-run.sh can't do it correctly)

[rob-solana]

actually, it turns out that Dockerfile can't do this right, either:

ENV PATH ${CARGO_HOME}/bin:${PATH}

doesn't make a dynamic PATH variable, it binds the value during docker build...

moving on to something in the workspace instead

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This stale issue has been automatically closed. Thank you for your contributions.