I am using a self-hosted runner in my Kubernetes cluster.
Due to API rate limiting while resolving actions, I have configured a static Persistent Volume (PV) to cache the actions used in my workflow, by setting the ACTIONS_RUNNER_ACTION_ARCHIVE_CACHE environment variable in the runner to point to my static PV.
After enabling debug logs during a workflow rerun, I can see that the actions are being copied from the PV. However, I still sometimes hit the API rate limit even though the actions are present in the PV and the ACTIONS_RUNNER_ACTION_ARCHIVE_CACHE environment variable is configured.
I also tried using the commit SHA instead of the version tag (e.g., actions/checkout@), but I still occasionally encounter API rate limits.
Getting the below error: ##[debug]GitHub.DistributedTask.WebApi.UnresolvableActionDownloadInfoException: API rate limit exceeded while resolving action docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9.
I am using a self-hosted runner in my Kubernetes cluster.
Due to API rate limiting while resolving actions, I have configured a static Persistent Volume (PV) to cache the actions used in my workflow, by setting the ACTIONS_RUNNER_ACTION_ARCHIVE_CACHE environment variable in the runner to point to my static PV.
After enabling debug logs during a workflow rerun, I can see that the actions are being copied from the PV. However, I still sometimes hit the API rate limit even though the actions are present in the PV and the ACTIONS_RUNNER_ACTION_ARCHIVE_CACHE environment variable is configured.
I also tried using the commit SHA instead of the version tag (e.g., actions/checkout@), but I still occasionally encounter API rate limits.
Getting the below error: ##[debug]GitHub.DistributedTask.WebApi.UnresolvableActionDownloadInfoException: API rate limit exceeded while resolving action
docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9.