-
Notifications
You must be signed in to change notification settings - Fork 29
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
Cache not working #245
Comments
I don't see any use of cache exporters in your workflow. You can use the gha exporter for example: - name: Build and Push Docker Images
uses: docker/bake-action@v5
env:
TAG: ${{ steps.release-tag.outputs.tag }}
with:
source: "."
files: "compose.yaml"
workdir: "./docker"
push: ${{ env.dryRun == 'false' }}
load: true
set:
*.cache-from=type=gha
*.cache-to=type=gha,mode=max More info: https://docs.docker.com/build/ci/github-actions/cache/ |
Would need to look at your Dockerfile and build logs to figure out if this related to context changes (maybe Can you share your |
Thanks for the help, this is my Dockerfile and this the .dockerbuild: Personally I don't see anything that could result in cache invalidation. Edit: I even tried to just re-run the same build and I obtained the same results. |
Seems cache is busted at Wonder if this is a bug with new Can you try without Can you also change this step: # This gives us access to buildx
- name: Set up Docker CLI
uses: docker/setup-buildx-action@v3 to # This gives us access to buildx
- name: Set up Docker CLI
uses: docker/setup-buildx-action@v3
with:
buildkitd-flags: --debug And post the BuildKit logs from post step: https://docs.docker.com/build/ci/github-actions/configure-builder/#buildkit-container-logs |
Thanks, I removed the This is the buildkit log: This the dockerbuild: I still see low cache percentage. |
Hi! We are observing issues with the cache as well. For identical contents, sometimes the build simply doesn't use the cache. These two builds:
differ by cnpem/epics-in-docker@635b6d0, and that |
Contributing guidelines
I've found a bug, and:
Description
I'm trying to use this action to build a multi stage image using a docker compose configuration file. The build is working correctly and the images are pushed to the Google Artifacts registry just fine, but subsequent builds are not taking advantage of the layers cache even though nothing in the repository changed at all.
Expected behaviour
I would expect this to be way higher than 0%
Actual behaviour
Cache seem not to be used at all?
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
BuildKit logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: