You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Warning: Failed to export build record: /home/runner/work/_temp/docker-actions-toolkit-16m5IG/export/rec.dockerbuild not found
When generating build summary in our GitHub Actions, we are using the buildx.build.ref from metadata to export the build record. When using call, this attribute is not set:
Which is the right behavior as no build record is written for subrequests anyway.
But we also have a fallback in our GitHub Actions in case buildx.build.ref is not set that checks if a local state is available as part of this build. And in this case we have one as we are generating a local state for subrequests but I don't think it makes sense to do so.
Relates to https://github.com/docker/docs/actions/runs/11502549192/job/32017891983#step:6:21
When generating build summary in our GitHub Actions, we are using the
buildx.build.reffrom metadata to export the build record. When usingcall, this attribute is not set:buildx/build/build.go
Lines 525 to 526 in 746eadd
Which is the right behavior as no build record is written for subrequests anyway.
But we also have a fallback in our GitHub Actions in case
buildx.build.refis not set that checks if a local state is available as part of this build. And in this case we have one as we are generating a local state for subrequests but I don't think it makes sense to do so.cc @dvdksn