-
Notifications
You must be signed in to change notification settings - Fork 236
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
Add SLSA to goreleaser workflow #3075
Comments
Todo
|
PR for slsactl. |
The docker manifest creation issue is not related the Prime registry permissions, but the fact that we only use provenance meta data there.
The issue is explained here. Unfortunately the "real solution" does not work (as confirmed in the comments) because we are already using containerd as storage. So until this is fixed I suppose we have to rely on yet another step. And signing for the manifest in GoReleaser is then also not possible. |
All new releases should be signed in the Prime registry. Successful run for Fleet |
When doing prime releases, goreleaser needs to push to that registry.
Similar to https://github.com/rancher/ecm-distro-tools/blob/45fe661ce4c4d58e938e480383ce5ef26c251cb6/actions/publish-image/action.yaml#L163-L175
goreleaser should sign the image, when doing the buildx of the image.
The text was updated successfully, but these errors were encountered: