Paul Bastide

Tag: oc-plugin

  • Downloading oc-compliance on ppc64le

    My team is working with the OpenShift Container Platforms Optional Operator – Compliance Operator. The Compliance Operator has a supporting tool oc-compliance.

    One tricky element was downloading the oc-compliance plugin and I’ve documented the steps here to help

    Steps

    1. Navigate to https://console.redhat.com/openshift/downloads#tool-pull-secret

    If Prompted, Login with your Red Hat Network id.

    1. Under Tokens, select Pull secret, then click Download

    2. Copy the pull-secret to your working directory

    3. Make the .local/bin directory to drop the plugin.

    $ mkdir -p ~/.local/bin
    1. Run the oc-compliance-rhel8 container image.
    $ podman run --authfile pull-secret --rm -v ~/.local/bin:/mnt/out:Z --arch ppc64le registry.redhat.io/compliance/oc-compliance-rhel8:stable /bin/cp /usr/bin/oc-compliance /mnt/out/
Trying to pull registry.redhat.io/compliance/oc-compliance-rhel8:stable...
Getting image source signatures
Checking if image destination supports signatures
Copying blob 847f634e7f1e done  
Copying blob 7643f185b5d8 done  
Copying blob d6050ae37df3 done  
Copying config 2f0afdf522 done  
Writing manifest to image destination
Storing signatures
    1. Check the file is ppc64le
    $ file ~/.local/bin/oc-compliance 
/root/.local/bin/oc-compliance: ELF 64-bit LSB executable, 64-bit PowerPC or cisco 7500, version 1 (SYSV), dynamically linked, interpreter /lib64/ld64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=d5bff511ee48b6cbc6afce6420e780da2f0eacdc, not stripped

    If it doesn’t work, you can always verify your architecture of the machine podman is running on:

    $ arch
ppc64le

    It should say ppc64le.

    You’ve seen how to download the ppc64le build.

    References