@jeff.ohrstrom, thank you so much for your prompt reply! You were right that it was a binding issue - I already had $HOME in SINGULARITY_BINDPATH, but adding “/run” to the binding solved the issue since that is the location where the dbus stuff on our cluster is.
Now, when I start the Interactive Desktop, I am getting:
Script starting…
Generating connection YAML file…
Restoring modules from user’s default
Launching desktop ‘mate’…
**(process:10977): dconf-WARNING : 18:33:28.255: failed to commit changes to dconf: Cannot autolaunch D-Bus without X11 $DISPLAY
**** (mate-session:11010): WARNING **: 18:33:28.783: Cannot open display: **
Desktop ‘mate’ ended…
Cleaning up…
After this, I added “export DISPLAY=:0.0” to the “mate.sh” script. Although the “X11 $DISPLAY” message was resolved, the display can still not be opened:
Script starting…
Generating connection YAML file…
Restoring modules from user’s default
Launching desktop ‘mate’…
**** (mate-session:11404): WARNING **: 18:35:29.375: Cannot open display: **
Desktop ‘mate’ ended…
Cleaning up…
The error looks similar to the one described in Module not found launching Desktop. I am indeed using the “basic” template, but that is because when I use “vnc”, the Singularity image is not launched and I am getting “vncserver command is not found”, although the image has “vncserver” in it. Do you maybe have any suggestions on how to proceed and fix this error? If I should open a different issue, please let me know as well.