Skip to content
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

Disable provenance, which results in extra artifacts in quay #11

Merged
merged 1 commit into from Jan 26, 2023

Conversation

jmontleon
Copy link
Member

No description provided.

@jmontleon
Copy link
Member Author

@kaovilai, IIUC this should get rid of the extra artifacts we are seeing.

docker/setup-buildx-action#187

As a temporary workaround, instead of pinning to a lower buildx version (once pinned, things often stay pinned ), I can recommend setting --provenance=false on the buildx cli, or provenance: false if using the docker/build-push-action. This will disable the attestation that's causing that change to the multi-platform image.

Signed-off-by: Jason Montleon <jmontleo@redhat.com>
@jmontleon jmontleon merged commit a27691c into konveyor:main Jan 26, 2023
@jmontleon
Copy link
Member Author

In the log for one of the builds with the extra artifacts in quay (listed as unknown on unknown, rather than linux on aarch64) the SHA matched the attestation manifest

2023-01-26T18:09:30.1608722Z #64 exporting manifest sha256:881334ffb38f96ebbb107ded2230b51c6ae746922c9a8de2429953b0fd9c7233 done
2023-01-26T18:09:30.1609153Z #64 exporting config sha256:cd7493aa493810d4fe531297fe6b31734e1f13b04d9bf311d5f537e36d11b97c done
2023-01-26T18:09:30.1609602Z #64 exporting attestation manifest sha256:78c2acc1e56a268dcb40764ef2a3fb53d325097f42c63dde5d3b2e728b0a7e0e done

@jmontleon
Copy link
Member Author

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants