env ACTIONS_RUNNER_ACTION_ARCHIVE_CACHE still cause API rate limit even after pinning <sha>

Open
#140 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
github-actions, kubernetes

Research direction

Start by reproducing the workflow on a self-hosted runner with ACTIONS_RUNNER_ACTION_ARCHIVE_CACHE configured on the persistent volume and debug logging enabled. Compare action resolution for cached actions and SHA-pinned actions, including docker/login-action, and verify that cached actions no longer trigger API rate-limit errors.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Shell
Stars
64
Forks
17
Avg merge
1d 12h
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/action-versions

All issues in actions/action-versions

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.