unknown cache exporter
Open
Nobody has claimed this yet.
status/needs-investigation
- Dominant language
- TypeScript
- Stars
- 301
- Forks
- 43
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 20
Description
Contributing guidelines
- I've read the contributing guidelines and wholeheartedly agree
I've found a bug, and:
- The documentation does not mention anything about my problem
- There are no open or closed issues that are related to my problem
Description
I'm running bake-action like this:
- name: Build and push
uses: docker/bake-action@v6
env:
versions_string: ${{ steps.short-sha.outputs.sha }},latest
with:
push: true
files: |
./${{ matrix.package.directory }}/docker-bake.hcl
set: |
*.cache-from="type=gha"
*.cache-to="type=gha,mode=max"
and I'm getting error:
ERROR: failed to solve: unknown cache exporter: "gha,mode=max"
I've searched for other issues in the repo, and my configuration matches what others have said in the past should work I think
Expected behaviour
Action uses gha docker cache
Actual behaviour
Image doesn't build due to error
Repository URL
No response
Workflow run URL
No response
YAML workflow
name: Development Build
on:
push:
branches:
- development
jobs:
determine-apps-affected:
# ....
build_image:
runs-on: ubuntu-22.04
needs: [determine-apps-affected]
strategy:
matrix:
package: ${{ fromJson(needs.determine-apps-affected.outputs.matrix) }}
steps:
- uses: benjlevesque/short-sha@v3.0
id: short-sha
with:
length: 6
- name: Login to container registry
uses: docker/login-action@v3
with:
registry: ${{ VARS.CONTAINER_REGISTRY }}
username: ${{ vars.CONTAINER_REGISTRY_USERNAME }}
password: ${{ secrets.CONTAINER_REGISTRY_PASSWORD }}
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
- name: Set up QEMU
uses: docker/setup-qemu-action@v3
- name: Build and push
uses: docker/bake-action@v6
env:
versions_string: ${{ steps.short-sha.outputs.sha }},latest
with:
push: true
files: |
./${{ matrix.package.directory }}/docker-bake.hcl
set: |
*.cache-from="type=gha"
*.cache-to="type=gha,mode=max"
Workflow logs
No response
BuildKit logs
Additional info
No response
Contributor 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.
Research direction
Start with the provided workflow's Build and push step and its cache-from/cache-to settings, then reproduce the failure using docker/bake-action@v6. Compare the resulting behavior with the action and Buildx cache configuration; done means the gha cache exporter is accepted and the image builds successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100