Using this action, I encountered a strange error. Then I realized that the problem was that I had set the CARGO_HOME environment variable in a previous step and that this variable was passed as -e argument to the docker run command.
So, when trying to use the rustup command the wrong PATH was used instead of the immediately previous one installed.
I believe this is a dangerous misconfiguration that may lead to an unusable action for some users.
For this reason I would explicitly exclude some variables such as CARGO_HOME that should not be passed.
Hi, I'm Dario.
Using this action, I encountered a strange error. Then I realized that the problem was that I had set the
CARGO_HOME
environment variable in a previous step and that this variable was passed as-e
argument to thedocker run
command. So, when trying to use therustup
command the wrongPATH
was used instead of the immediately previous one installed.I believe this is a dangerous misconfiguration that may lead to an unusable action for some users. For this reason I would explicitly exclude some variables such as
CARGO_HOME
that should not be passed.