vGPU driver for rhcos4.19 / rhel9.6 directory issue

[CLNRMN]

Hi

We're running an OpenShift Cluster with 4.19.x, which uses rhel9.6. According to the documentation, you should not use the rhcos-4.19 version tag anymore; instead, you should switch to rhel9.6.

We tried to build the vGPU image with the following parameters and got the error that the folder was not found.

export PRIVATE_REGISTRY=registry.company.com/company
export OS_TAG=rhel9.6
export VGPU_DRIVER_VERSION=570.124.06

VGPU_GUEST_DRIVER_VERSION=${VGPU_DRIVER_VERSION} IMAGE_NAME=${PRIVATE_REGISTRY}/driver make build-vgpuguest-${OS_TAG}
DOCKER_BUILDKIT=1 \
	docker  build --pull \
			--output=type=image,push=false \
			--platform=linux/amd64 \
			--tag registry.company.com/company/driver:570.124.06-rhel9.6 \
			--build-arg DRIVER_TYPE=vgpu \
			--build-arg VGPU_LICENSE_SERVER_TYPE=NLS \
			--build-arg DRIVER_VERSION="570.124.06-grid" \
			--build-arg DRIVER_BRANCH="570" \
			--build-arg GOLANG_VERSION="1.25.4" \
			--build-arg CVE_UPDATES="" \
			 \
			--file /home/username/git/public/gpu-driver-container/rhel9.6/Dockerfile \
			/home/username/git/public/gpu-driver-container/rhel9.6
[+] Building 0.0s (0/0)                                                                                                                                                                                                                        docker:default
ERROR: failed to build: unable to prepare context: path "/home/username/git/public/gpu-driver-container/rhel9.6" not found

To fix it, we've added the following line to the makefile to make it work.

diff --git a/Makefile b/Makefile
index ee633db..19a2f92 100644
--- a/Makefile
+++ b/Makefile
@@ -246,6 +246,7 @@ build-vgpuguest-%: DRIVER_TAG = $(DRIVER_VERSION:-grid=)
 
 # Source of truth for RHEL and CoreOS compatibility https://access.redhat.com/articles/6907891
 build-vgpuguest-rhcos%: SUBDIR = rhel9
+build-vgpuguest-rhel9%: SUBDIR = rhel9

Probably related to this change here: #486

[zviratko]

Just went here to report the same thing.
This whole thing is one huge mess.

[seb2020]

Hi,

Same issue for us. After the fix, the build is good.