RUNNER_TOOL_CACHE Path issue #213

Open
opened 2023-05-24 06:59:30 +00:00 by PittyXu · 2 comments

I use catthehacker/ubuntu:act-latest image. And found that the environment variable RUNNER_TOOL_CACHE is set to/opt/hostedtoolcache, but the runner will create a act-toolcache volume and mount it to /toolcache when it is initialized.
The action toolkit caches the tool according to the environment variable RUNNER_TOOL_CACHE.
Is there a problem with the environment variable setting or the two paths are different?

Env:[RUNNER_TOOL_CACHE=/opt/hostedtoolcache RUNNER_OS=Linux RUNNER_ARCH=X64 RUNNER_TEMP=/tmp LANG=C.UTF-8]

Mounts:[{Type:volume Source:act-toolcache Target:/toolcache ReadOnly:false Consistency: BindOptions:<nil> VolumeOptions:<nil> TmpfsOptions:<nil> ClusterOptions:<nil>} {Type:volume Source:GITEA-ACTIONS-TASK-80_WORKFLOW_JOB-nuclei-scan-env Target:/var/run/act ReadOnly:false Consistency: BindOptions:<nil> VolumeOptions:<nil> TmpfsOptions:<nil> ClusterOptions:<nil>}
...
I use `catthehacker/ubuntu:act-latest` image. And found that the environment variable `RUNNER_TOOL_CACHE` is set to`/opt/hostedtoolcache`, but the runner will create a `act-toolcache` volume and mount it to `/toolcache` when it is initialized. The `action toolkit` caches the tool according to the environment variable `RUNNER_TOOL_CACHE`. Is there a problem with the environment variable setting or the two paths are different? ``` Env:[RUNNER_TOOL_CACHE=/opt/hostedtoolcache RUNNER_OS=Linux RUNNER_ARCH=X64 RUNNER_TEMP=/tmp LANG=C.UTF-8] Mounts:[{Type:volume Source:act-toolcache Target:/toolcache ReadOnly:false Consistency: BindOptions:<nil> VolumeOptions:<nil> TmpfsOptions:<nil> ClusterOptions:<nil>} {Type:volume Source:GITEA-ACTIONS-TASK-80_WORKFLOW_JOB-nuclei-scan-env Target:/var/run/act ReadOnly:false Consistency: BindOptions:<nil> VolumeOptions:<nil> TmpfsOptions:<nil> ClusterOptions:<nil>} ... ```
a1012112796 added the
related
act
label 2023-06-01 03:12:30 +00:00
Member

act Maintainers are discussed in this PR.

act Maintainers are discussed in this [PR](https://github.com/nektos/act/pull/1494).
Member

This issue is similar to #70. As @sillyguodong said, it's related to the upstream and there is a PR trying to fix this. You could set the RUNNER_TOOL_CACHE environment variable to /toolcache to cache tools to act-toolcache volume for now, like #70 (comment)

This issue is similar to #70. As @sillyguodong said, it's related to the upstream and there is a PR trying to fix this. You could set the `RUNNER_TOOL_CACHE` environment variable to `/toolcache` to cache tools to `act-toolcache` volume for now, like https://gitea.com/gitea/act_runner/issues/70#issuecomment-734824
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/act_runner#213
No description provided.