From 79a494b2aaf11fcc95008dbdb54afb0efa664cd6 Mon Sep 17 00:00:00 2001 From: Yusuke Kuoka Date: Sun, 17 Jul 2022 19:44:07 +0900 Subject: [PATCH] doc: Note to fully populate the pool of PVs before checking if the cache is effective (#1655) --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index ecacc89e..d08bbe50 100644 --- a/README.md +++ b/README.md @@ -1447,6 +1447,8 @@ reused across runner pods to retain `/var/lib/docker`. _Be sure to add the volume mount to the container that is supposed to run the docker daemon._ +_Be sure to trigger several workflow runs before checking if the cache is effective. ARC requires an `Available` PV to be reused for the new runner pod, and a PV becomes `Available` only after some time after the previous runner pod that was using the PV terminated. See [the related discussion](https://github.com/actions-runner-controller/actions-runner-controller/discussions/1605)._ + By default, ARC creates a sidecar container named `docker` within the runner pod for running the docker daemon. In that case, it's where you need the volume mount so that the manifest looks like: @@ -1482,6 +1484,8 @@ With `dockerdWithinRunnerContainer: true`, you need to add the volume mount to t The module cache dir can be customized by setting `GOMOD_CACHE` so by setting it to somewhere under `$HOME/.cache`, we can have a single PV to host both build and module cache, which might improve Go module downloading and building time. +_Be sure to trigger several workflow runs before checking if the cache is effective. ARC requires an `Available` PV to be reused for the new runner pod, and a PV becomes `Available` only after some time after the previous runner pod that was using the PV terminated. See [the related discussion](https://github.com/actions-runner-controller/actions-runner-controller/discussions/1605)._ + ```yaml kind: RunnerSet metadata: