Use a hardcoded toolcache path since we need to extract there to let Ruby work

This commit is contained in:
Benoit Daloze
2020-11-10 19:58:59 +01:00
parent bb3a0c6e0b
commit ba761ba8ff
5 changed files with 36 additions and 16 deletions
+4 -4
View File
@@ -203,10 +203,10 @@ if the [virtual environment](https://github.com/actions/virtual-environments) is
* Make sure to use the same operating system and version.
* Make sure to use the same version of libssl.
* Make sure that the operating system has `libyaml-0` installed
* The environment variable `RUNNER_TOOL_CACHE` must be set to same value as on GitHub-hosted runners
(`/opt/hostedtoolcache` on Linux, `/Users/runner/hostedtoolcache` on macOS, `C:\hostedtoolcache\windows` on Windows).
* That directory must be writable by the `runner` user.
* The runner software is running as user `runner` with a home directory of `/home/runner`, or you have created a symlink for the home directory of whatever user that the runner is running as to `/home/runner`.
* The default tool cache directory (`/opt/hostedtoolcache` on Linux, `/Users/runner/hostedtoolcache` on macOS,
`C:/hostedtoolcache/windows` on Windows) must be writable by the `runner` user.
This is necessary since the Ruby builds embed the install path when built and cannot be moved around.
* `/home/runner` must be writable by the `runner` user.
In other cases, please use a system Ruby or [install Ruby manually](https://github.com/postmodern/chruby/wiki#installing-rubies) instead.