New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mac: Cannot connect to X server running my singularity container #5524
Comments
Your help will be greatly appreciated! Thank you very much! Best, |
Btw, I have already tried the following on my Mac:
And change the following two lines:
Also,
|
It's not a 127.0.0.1 address. IIRC Mac defaults to The "easiest" (though not best) is to do: |
Thank you very much for your quick response! Super efficient!
I don't know much about DHCP. So I decide to go forward with your next suggestion:
This didn't solve my problem though. Here is what I did on my Mac:
Then I went to run my singularity container:
Any further comments? Thank you so much! Best, |
Can you try ssh-ing to some kind of straight Linux machine and running and X term application so that it will display on your Mac, to verify XQuartz is working okay.... or has that already been done? Please also note the current status of Singularity Desktop for Mac: https://sylabs.io/singularity-desktop-macos/
|
To expand on this... In the XQuartz preferences, you need to goto That's off by default. |
Thank you very much Jason and David! The error still applies.
I ssh to a ubuntu machine and then type
I saw a tiny clock window pop up, this means that my XQuartz in my Mac works fine.
I also check the box that says:Allow connections from network clients Then I restart XQuartz and tried:
There is one new error message No protocol specified, which I haven't seen before. I googled this error message but didn't find a way to fix this problem. Is there anything else I can do?
I understand that this Mac version of Singularity is still under development. I would love to know whether this X11 forwarding thing is related to the current version, or it is just because my mistakes at some settings. Thank you very much! Best, |
Run |
Ahhh! It works! Tried it on another Mac machine, also works! Hooray! Thank you so much Jason and David!!!! In summary:
You may need to type the following (or not)
Then try to run your singularity container, it should work now. I will try to ask another colleague to reproduce the results, as I have tried so many different things on these two Macs following Google search results. Just want to check for sure. Thank you so much!! A huge problem for me solved! Have a great night! (11:04pm here) Sending my virtual hugssssssss! |
Sounds good. Holler if you have any other issues. @dctrud ... Right, I can't close these... This can probably be closed now. :) |
Version of Singularity:
What version of Singularity are you using? Run:
(Freshly installed singularity Mac desktop version)
Expected behavior
I build my own singularity container, the usage and command history can be found at (https://github.com/zoeye859/presto_v3_singularity). It worked fine on multiple ubuntu machines, therefore I assume it worked OK.
However, when I try to run this container on my Mac (and my colleague's Mac), the X server cannot be connected, this means that I cannot interact with pop-up images using X11.
If I change the $DISPLAY path:
If choose /PS, the .ps file can be produced.
When running on ubuntu, the X server can plot images without problem.
After intensive research and many experiments, I believe it is something to do with the X11 forwarding on Mac, I think I'd better to submit an issue here to try some luck.
You may be interested in the following error too:
There was once I got the error saying
Steps to reproduce this behavior
Use a Mac machine
You can download PSRSOFT_yhy.simg following the README at (https://github.com/zoeye859/presto_v3_singularity)
What OS/distro are you running
Mac OS CATALINA 10.15.6 (19G73)
How did you install Singularity
My install history can be found at (https://github.com/zoeye859/presto_v3_singularity/blob/master/INSTALLATION%20RECORDS.md)
The text was updated successfully, but these errors were encountered: