-
Notifications
You must be signed in to change notification settings - Fork 121
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
#370 breaks GitHub Actions build example #381
Comments
We have the same issue when trying to use upload-artifact to upload bake json files for use elsewhere |
Pin docker/metadata-action to 5.4 until docker/metadata-action#381 is fixed
Pin docker/metadata-action to 5.4 until docker/metadata-action#381 is fixed (cherry picked from commit 3d13f41)
I've run into the same issue. I also see that the example in https://github.com/docker/metadata-action?tab=readme-ov-file#bake-definition still uses |
I will update the example with this new behavior since 5.5.0. In the meantime you can do: -
name: Rename meta bake definition file
run: |
bakeFile="${{ steps.meta.outputs.bake-file }}"
mv "${bakeFile#cwd://}" "/tmp/bake-meta.json" |
Pin docker/metadata-action to 5.4 until docker/metadata-action#381 is fixed
Contributing guidelines
I've found a bug, and:
Description
#370 has broken example documentation from Docker on how one could use the metadata action in a larger workflow to build multi-platform images in GitHub Actions. Specifically, attempting to rename the temporary bake file generated by the metadata action in a follow-up step.
mv "${{ steps.meta.outputs.bake-file }}" "/tmp/bake-meta.json"
https://docs.docker.com/build/ci/github-actions/multi-platform/#with-bake
Attempting to do so now results in an action error like:
Expected behaviour
File is found and renamed.
Actual behaviour
File not found.
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: