fix precompiled driver container failures when enabling OpenRM #175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have found that the OpenRM modules fail to load successfully as it's unable to find the firmware files in the
/lib/firmware
directory. This was happening due to two reasons:/lib/firmware
files were being installed during the container image build-time. See here/lib/firmware
files were wiped out as we mount the/run/nvidia/driver/lib/firmware
directory . See hereTo fix this issue, we make the following changes
nvidia-driver-${DRIVER_BRANCH}-server
package, so that the actual takes place during container runtime and thelib/firmware
files are installed AFTER the mount/sys/module/firmware_class/parameters/path
. This is performed in non precompiled containers and it is needed for the OpenRM Kernel module to load successfully