Open jgrn307 opened 5 years ago
So sorry for the slow reply, I missed the email notification for this somehow.
Okay, with Singularity:
Are you building the image from the Singularity file (also what version of Singularity are you using)?
Or are you pulling the image from DockerHub and running it with Singularity?
The Singularity build uses an XFCE Remote Desktop to run CloudCompare inside of it, whereas if you run Docker on your own machine, it will be looking to use your display drivers. If you're on an HPC, those drivers are not set, so you're seeing this error. It likely needs VirtualGL to run the display rendering as well.
I hate this QXcbConnection: Could not connect to display
error - it is a constant problem when running on remote desktops.
You could try singularity shell docker://tswetnam/cloudcompare:latest
and then work interactively with the container.
Its the weekend now, but I'll try and fix this on Monday - feel free to contact me via other means (tswetnam@cyverse.org). Would be happy to chat in person.
Hi there! I posted this in the CC forum but I thought I'd post it here too -- I'm trying to use your current docker image (imported to singularity) to do headless command line mode, but I'm getting this error:
singularity exec ~/gearslaboratory-gears-singularity-master-gears-cloudcompare.simg CloudCompare -SILENT \ -O /data/gpfs/assoc/gears/lidarchange/scratch/wscharffenberger/ALS_TLS_UAV_registration/P406_E2/Unregistered/P406_E2_ALS.las \ -O /data/gpfs/assoc/gears/lidarchange/scratch/wscharffenberger/ALS_TLS_UAV_registration/P406_E2/Unregistered/P406_E2_TLS.las \ -ICP
QXcbConnection: Could not connect to display Aborted (core dumped)
Any ideas what could be going on?