Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-10268

CSO 3.15.3 failed to startup caused by 'GLIBC not found' error

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • Critical

       

      Description

      CSO failed to startup caused by 'GLIBC not found' error

      Version

      registry.redhat.io/quay/quay-container-security-operator-rhel8@sha256:181b8ead12a4addbe5c1d57339bbe6e3419bd91ef241c6c6f0f3319cfc88f1cf

      Reproduced Steps
      1. Login OCP
      2. Install CSO
      Actual Results

      CSO pod keeps in CrashLoopBackOff states,

      pod logs:

      /bin/security-labeller: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /bin/security-labeller)
/bin/security-labeller: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /bin/security-labeller)

       

              marckok Marcus Kok
              rhn-support-dyan Dongbo Yan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: