Sign a container image keylessly with cosign and attach the signature to the registry using the cosign sign command

domain: sigstore.dev · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Authenticate to the container registry where the image is stored using standard registry credential mechanisms such as docker login or a workload identity credential
  2. Run 'cosign sign --yes <image>@<digest>' referencing the image by its immutable digest rather than a mutable tag to ensure the signature is tied to the exact image content
  3. Confirm that cosign obtains an OIDC token from the ambient identity provider, requests a certificate from Fulcio, and records the signature to Rekor
  4. Verify the signature was pushed to the registry as an OCI referrer by running 'cosign verify <image>@<digest> --certificate-identity <identity> --certificate-oidc-issuer <issuer>'
  5. Ensure downstream consumers reference images by digest when verifying, as tag-based references are mutable and may point to a different image than what was signed

Known gotchas

Related routes

Sign a container image keylessly with cosign and Sigstore using GitHub Actions OIDC
docs.sigstore.dev/cosign/signing · 6 steps · unrated
Sign a container image keylessly with Cosign 2.x in a CI/CD pipeline
docs.sigstore.dev · 5 steps · unrated
Sign a container image keylessly with cosign using a GitHub Actions OIDC token and record to Rekor
docs.sigstore.dev · 5 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans