跳转到主内容

由于缺少签名,无法在隔离的 OpenShift 环境中镜像 NetApp Trident Operator 镜像

Views:
37
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
snapx
Last Updated:

适用于

  • RedHat Openshift
  • Trident(v25.10.0-linux-only 及更高版本)

问题

  • 尝试使用 oc-mirror 工具将 Trident Operator 从 Red Hat Certified Operator Index 镜像到内部注册表时,该过程失败,并出现与缺少映像签名相关的错误。
  • 示例:
[ERROR]: [Worker] error mirroring image docker://registry.connect.redhat.com...r-image@sha256:... error: reading signatures: reading manifest ... .sig in registry.connect.redhat.com/netapp/trident-operator-image: name unknown: Image not found
[ERROR]: [Worker] error mirroring image docker://registry.connect.redhat.com...support@sha256:... error: reading signatures: reading manifest ... .sig in registry.connect.redhat.com/netapp/trident-autosupport: name unknown: Image not found
[ERROR]: [Worker] error mirroring image docker://registry.connect.redhat.com...trident@sha256:... error: reading signatures: reading manifest ... .sig in registry.connect.redhat.com/netapp/trident: name unknown: Image not found
Cause:
Red Hat’s certified operator registry (registry.connect.redhat.com or registry.redhat.io) may not include image signatures for some operator images. The oc-mirror tool, by default, expects these signatures when mirroring, and fails if they are missing.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.