-
Notifications
You must be signed in to change notification settings - Fork 31
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
unknown cache exporter #306
Comments
This syntax looks correct: set: |
*.cache-from="type=gha"
*.cache-to="type=gha,mode=max" But it should be: set: |
*.cache-from=type=gha
*.cache-to=type=gha,mode=max I wonder if Can you show the full logs of the |
Ok I tried on my side and it gives:
{
"group": {
"default": {
"targets": [
"image"
]
}
},
"target": {
"image": {
"attest": [
{
"builder-id": "https://github.com/docker/test-docker-action/actions/runs/13720577244/attempts/1",
"inline-only": "true",
"mode": "min",
"type": "provenance"
}
],
"context": "https://github.com/docker/test-docker-action.git#032e801d9756d88af32f1c3acceea67f3446c6cf",
"dockerfile": "./multistage.Dockerfile",
"cache-from": [
{
"type": "gha"
}
],
"cache-to": [
{
"type": "gha,mode=max"
}
],
"platforms": [
"linux/amd64",
"linux/arm64"
]
}
}
} This is wrong though: "cache-to": [
{
"type": "gha,mode=max"
}
], I tried locally with:
But works fine: "cache-to": [
{
"mode": "max",
"type": "gha"
}
], So I wonder if this has something to do with args passed to exec in GitHub's toolkit: https://github.com/actions/toolkit/blob/dc22dc7cad322ab3cf9280133face378c63195f7/packages/exec/src/exec.ts#L17 |
Contributing guidelines
I've found a bug, and:
Description
I'm running bake-action like this:
and I'm getting error:
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 cacheActual behaviour
Image doesn't build due to error
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
BuildKit logs
Additional info
No response
The text was updated successfully, but these errors were encountered: