The driver-toolkit container build tries to curl the extract-vmlinux script, which does not work in the (disconnected) ART build environment. This script is available as part of the kernel packages already installed in the location /usr/src/kernels/${INSTALLED_KERNEL}/scripts/extract-vmlinux, at least on the architectures for which the script will work. In the other architectures, we can just install whichever gcc version is available by default in the ART builds. This is needed in order for force the driver-toolkit to install the specific gcc version which was used to compile the kernel in the driver-toolkit.
Verified in build: 4.9.0-0.nightly-2021-07-15-015134 1. Go to the OpenShift release nightly build page for the nightly build, click "Download the installer," and then click "release.txt." 2. Search for "driver-toolkit" and pull the corresponding image to your dev machine with the command: podman pull --authfile /path/to/pullsecret <openshift_release_repo>/<corresponding_image_to_your_dev_machine> 3. Enter the following command from the terminal: podman run <image_from_previous_step> cat /tmp/kernel_info | grep -Eo "gcc version ([0-9\.]+)" | grep -Eo "([0-9\.]+)" 4. Enter the following command from the terminal: podman run <image_from_previous_step> dnf list installed | grep gcc 5. Ensure that the output from step 3 matches the installed version of gcc from step 4 ================================================================== Output: Step 3: 8.4.1 Step 4: gcc.x86_64 8.4.1-1.el8 @rhel-8-appstream-rpms-x86_64 libgcc.x86_64 8.4.1-1.el8 @System
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:3759