Thank you very much @DaveInCanada ; I’m not a native speaker and I don’t usually use English regularly.
I’ve found the issue, at least in my case.
To fix it, it’s necessary to modify a file from the command line interface (CLI), so each person should proceed at their own risk.
In the user_config.yaml file, located in the ixVolume volume (a Dataset automatically created by the system), in my case it’s found at /mnt/.ix-apps/user_config.yaml. (in your case it may be another route)
This file contains all the configurations for installed applications. Upon reviewing it, I found a specific section related to the GPU (in every app you can use GPU):
resources:
gpus:
nvidia_gpu_selection:
'0000:07:00.0':
use_gpu: true
uuid: '' <<-- the problem
use_all_gpus: false
As you can see, the uuid field is empty ('') when it should contain the UUID obtained by running nvidia-smi -L. I replaced all empty uuid fields with the correct UUID (without quotes, directly GPU-xxxxx…), saved the file, and restarted the application from the graphical user interface (GUI). Everything worked smoothly.
In addition, you need to define the IOMMU group for your GPU. In my case, it is 0000:07:00.0, which can be found using the command lspci -Dnn | grep -i NVIDIA. Thanks to @Mortorojo for the helpful addition.
It seems that the issue occurs because, for some reason, Docker leaves the uuid field empty after an update, possibly because the driver isn’t installed at that moment, or for some other unknown reason.
At least now I don’t have to reconfigure all applications to make them work with the GPU.