env ACTIONS_RUNNER_ACTION_ARCHIVE_CACHE still cause API rate limit even after pinning <sha>
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
- Domain
- ci-cd, devops, infrastructure
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from actions/action-versions
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
actions/action-versions#172 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
actions/action-versions#49 · 2 comments ·
All issues in actions/action-versions
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pearu/agent-sandbox#422 ·
Maintainers usually reply within 1 day
-
area/ui enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
melgarafael/DeskcommCRM#4993 ·
Maintainers usually reply within 1 day
-
meta::needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 70/100
docker-mailserver/docker-mailserver#4864 ·
Maintainers usually reply within 1 day
-
Bump zig to >= 0.17.1 in main images: 0.17.0 emits duplicate LC_LOAD_DYLIB, darwin binaries abort in dyldPossibly taken @SuperQ claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
prometheus/golang-builder#417 ·
Maintainers usually reply within 1 day
-
application-issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Installomator/Installomator#3657 · 1 comment ·
Maintainers usually reply within 3 days