Closed cshilwant closed 1 month ago
That's a build attestation artifact.
https://docs.docker.com/build/metadata/attestations/attestation-storage/
I see. Only way to avoid it would be skipping metadata-action & just continue building with docker build. But that's not the motive. The issue can be ignored & closed
What's
unknown/unknown
under https://github.com/TexasInstruments/processor-sdk-doc/pkgs/container/processor-sdk-doc ?