Open zacps opened 1 year ago
Same here. Is there a workaround?
@zacps I finally got back on this project, where I was stuck with this issue and I resolved it as follows:
Add an input e.g. use-cache
:
use-cache:
type: boolean
description: Whether or not to use the Docker action's cache feature.
default: true
Optionally configure the cache options when calling the docker-build-push
workflow:
with:
cache-from: ${{ inputs.use-cache == 'true' && 'type=gha' || 'type=local,src=/tmp' }}
cache-to: ${{ inputs.use-cache == 'true' && 'type=gha, mode=max' || 'type=local,dest=/tmp' }}
Make sure you pass the input forward from your test YAML!
Issue is stale and will be closed in 14 days unless there is new activity
This is not a valid solution to me, since it requires changing the workflow. Has anyone succeeded in having GHA Cache working in act
?
Bug report info
Command used with act
Describe issue
The
gha
cache style would either work or silently be ignored, instead the job fails if it is configured.The other parts of the workflow file are sensitive.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response