-
Notifications
You must be signed in to change notification settings - Fork 131
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
MANIFEST_INVALID while pushing signature/attestation #252
Comments
... And now, tried the same with
|
Hey @sbose78 thanks for opening this issue. I browsed the |
Thank you @priyawadhwa for looking it up for me - should've done some looking around :) |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
/remove-lifecycle stale @sbose78 looks like the cosign issue was closed and support was added, does this work for you now? |
👋 @priyawadhwa , I will test this and let you know! |
Closing this for now, if this persists, I will re-open. |
@sbose78 It still fails for me: https://github.com/evryfs/base-ubuntu/runs/5173488457?check_suite_focus=true |
FWIW, pushing signatures and attestations to quay.io still fails with the error: The primary reason being that the media type Issue reported here - https://issues.redhat.com/browse/PROJQUAY-3386 |
Expected Behavior
Should have been able to push signature/attestations after being able to push the image.
( Image ref: quay.io/shbose/kaniko-chains:0.2 )
Actual Behavior
Push to registry fails.
Is this the issue with Quay.io not supporting a specific version of the schema?
Here's how my
docker manifest inspect...
looks like:Logs
Steps to Reproduce the Problem
kaniko-chains
Tasksecret
out of the dockerconfig json asregistration-credentials
and linked it undersecrets
&pullSecrets
in thepipeline
sa which is used to run my TaskRuns.Additional Info
The text was updated successfully, but these errors were encountered: