B
BlueBuild•2mo ago
Simen

Cosign v2.4.2 no stage or image found with that name

I am trying to build the secureblue image recipe-silverblue-main.yml using bluebuild and this is how it fails: 
l/silverblue-main-hardened:latest => Trying to pull ghcr.io/sigstore/cosign/cosign:v2.4.2...
l/silverblue-main-hardened:latest => Error: COPY --from=ghcr.io/sigstore/cosign/cosign:v2.4.2: no stage or image found with that name
ERROR => Failed:
  × Failed to build localhost/silverblue-main-hardened:latest
l/silverblue-main-hardened:latest => Trying to pull ghcr.io/sigstore/cosign/cosign:v2.4.2...
l/silverblue-main-hardened:latest => Error: COPY --from=ghcr.io/sigstore/cosign/cosign:v2.4.2: no stage or image found with that name
ERROR => Failed:
  × Failed to build localhost/silverblue-main-hardened:latest
Heres the recipie: https://github.com/secureblue/secureblue/blob/live/recipes/general/recipe-silverblue-main.yml I have done this prior to building:
Copy /etc/containers/policy.json to ~/.config/containers/policy.json 
podman image trust set --type accept docker.io/mikefarah/yq
podman image trust set --type accept ghcr.io/blue-build
podman image trust set --type accept quay.io/fedora-ostree-desktops
podman image trust set --type accept docker.io/mikefarah/yq
podman image trust set --type accept ghcr.io/blue-build
podman image trust set --type accept quay.io/fedora-ostree-desktops
Anyone know whats up?
GitHub
secureblue/recipes/general/recipe-silverblue-main.yml at live · sec...
Hardened Fedora Atomic and Fedora CoreOS images . Contribute to secureblue/secureblue development by creating an account on GitHub.
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?