-
Notifications
You must be signed in to change notification settings - Fork 30
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
V6 broke interaction with docker/metadata-action #287
Comments
As v6 is now using Git context by default (https://github.com/docker/bake-action/releases/tag/v6.0.0), it needs some changes in the metadata-action step: https://github.com/docker/metadata-action?tab=readme-ov-file#bake-definition You need to use the local bake file by specifying the In your case: - name: Build
uses: docker/bake-action@60f5d53310314dbf8c33f0c8a01042536f2f6c36 # v6
with:
files: |
./docker-bake.json
cwd://${{ steps.meta-yyy.outputs.bake-file }}
targets: default
push: ${{ github.event_name != 'pull_request' || !startsWith(github.head_ref, 'renovate') }}
pull: true #always pull latest version of base images of whatever we are building More info: https://docs.docker.com/build/bake/remote-definition/#combine-local-and-remote-bake-definitions I will update the release notes. |
Thanks that work... |
feat #30 - from [docker/bake-action/issues/287](docker/bake-action#287) - Add 'cwd://' prefix to docker_bake_config_file_path in echo statements - Update 'files' input for buildx bake command to use 'cwd://' prefix - Apply changes across multiple workflow templates and actual workflow files
Contributing guidelines
I've found a bug, and:
Description
existing build scripts using docker/metadata-action are failing with v6 due to confusion about where the files are located
Expected behaviour
build success
Actual behaviour
ERROR: failed to solve: lstat /actions-runner/_work/_temp/docker-actions-toolkit-YZDiwT/docker-metadata-action-bake.json: no such file or directory
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: