Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-3479

could not extract Wasm file from the image as Docker container number of layers must be 1 but got 2

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • OSSM 2.2.4
    • None
    • False
    • None
    • False

      Not able to create Wasm Plugin using below yaml.

      apiVersion: extensions.istio.io/v1alpha1
      kind: WasmPlugin
      metadata:
          name: 3scale-wasm-auth
          namespace: httpbin
      spec:
          url: oci://registry.redhat.io/openshift-service-mesh/3scale-auth-wasm-rhel8:0.0.1
          imagePullPolicy: Always
          imagePullSecret: 3096036-ub-eas-pull-secret
          phase: AUTHZ
          priority: 100
          workloadSelector:
              labels:
                  app: httpbin-api
          pluginConfig:
      

      Below error is thrown:

      httpbin-api-1-s8kb4 istio-proxy 2022-12-07T18:29:12.469822Z    error    wasm    cannot fetch Wasm module oci://registry.redhat.io/openshift-service-mesh/3scale-auth-wasm-rhel8:0.0.1: could not fetch Wasm binary: could not extract Wasm file from the image as Docker container number of layers must be 1 but got 2
      

      The cluster has below versions of service mesh and 3scale-operator:

      oc get csv
      NAME                                      DISPLAY                                          VERSION                 REPLACES                                  PHASE
      3scale-operator.v0.10.1-0.1675914645.p    Red Hat Integration - 3scale                     0.10.1+0.1675914645.p   3scale-operator.v0.10.1                   Succeeded
      
      istioctl version
      client version: 1.16.0
      control plane version: OSSM_2.2.4
      data plane version: 1.12.9 (30 proxies)
      

            Unassigned Unassigned
            rhn-support-atn Anand T N (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: