You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When specifying a driver version in the ClusterPolicy object in the spec.driver.version property, the driver-daemonset pods are crashing with the error "InvalidImageName". This is caused by the image used for the driver container, which has the following format: "image: '/:525.60.13-rhcos4.11'". Obviously, the registry, repository and image is missing in the reference. The image value should be set to "nvcr.io/nvidia/driver:525.60.13-rhcos4.11".
3. Steps to reproduce the issue
Set the spec.driver.version property of the ClusterPolicy CR.
4. Information to attach (optional if deemed irrelevant)
1. Quick Debug Information
2. Issue or feature description
When specifying a driver version in the ClusterPolicy object in the spec.driver.version property, the driver-daemonset pods are crashing with the error "InvalidImageName". This is caused by the image used for the driver container, which has the following format: "image: '/:525.60.13-rhcos4.11'". Obviously, the registry, repository and image is missing in the reference. The image value should be set to "nvcr.io/nvidia/driver:525.60.13-rhcos4.11".
3. Steps to reproduce the issue
4. Information to attach (optional if deemed irrelevant)
The text was updated successfully, but these errors were encountered: