-
Notifications
You must be signed in to change notification settings - Fork 517
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local cache remains empty despite cache-to and cache-from configuration #1054
Comments
Having the same issue. I'm trying all of the variously proposed options to get my github action cache to persist across multiple runners, cannot figure it out. So I tried running the build 2 times in the same runner, both times getting this issue where
Run: https://github.com/mozilla/addons-server/actions/runs/8019019347/job/21906086963?pr=21893 |
You need to set the Tried in this repo through #1066 and looks good to me:
Also you should consider using the |
Thanks for testing and pointing to the docs @crazy-max. I tried your setup, and the cache works for me (replacing
But as soon as I replace this path with - name: Cache Docker layers
uses: actions/cache@v4
with:
path: ~/.cache/docker-ci
key: ${{ runner.os }}-buildx-${{ github.sha }}
restore-keys: |
${{ runner.os }}-buildx- I tried to remove this folder, and let the workflow create it, but it didn't work either.
That solution would be suitable if the cache content wasn't sensitive or private, which is the case here. |
Don't think |
Contributing guidelines
I've found a bug, and:
Description
I'm running Docker on a Self Hosted Github Actions Runner, and I've configured a local cache path at
~/.cache/docker-ci
, as well as specifying it inbuild-push-action
fields.However, the cache remains empty after each build
Expected behaviour
The cache should be populated and used by Docker to speedup the future builds.
Actual behaviour
The cache remains empty:
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
BuildKit logs
No response
Additional info
Related closed issue that I found:
I can't share the repository as it's a private project.
The text was updated successfully, but these errors were encountered: