-
Notifications
You must be signed in to change notification settings - Fork 114
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
Process get_software_versions
terminated with an error exit status (1)
#102
Comments
Hi there, |
I install my Docker refer to official instruction: And run the test.
My java and nextflow verison
|
Hm, looks like docker isn't the problem. Maybe @apeltzer has another idea? |
thanks. @d4straub can you tell me your nfcore run environment including OS name and version, jdk version, docker version and nextflow version ? I can try again. |
Not sure if it helps, none of this should matter, but here is what you requested: |
Thanks for your info. @d4straub In my case, I try singularity instead of Docker and then work. |
@d4straub I run the demo testdata and then an new issue occurs.
|
So last time docker didn't work as it should. Was on the right track after all. The test run is typically started by this command: |
Still the same error by
|
Same problem: libGL.so.1 seems part of it. Whats your singularity version? When singularity isn't properly set up this might happen, again @apeltzer would be the expert here ;) |
The related softs version are listed as
|
Similarly, I run
|
That looks like a different error to me.
|
Yes. You are right. docker and singularity are independent. |
@d4straub @apeltzer Sorry for the delay reply. From my side I need anyone's help. I try the singularity version 3.0.1 and still can not work as
I suspect It was caused by basic OS so I test on Debian 9. Even still can not work but
|
With basic OS the container somehow cannot access the shared library which is available in the container. I am no expert here, but this shouldn't happen, I have no lead what could cause it. With Debian 9 there seems to be no access to the folder system, meaning singularity has no access. This leads to the suspicion that singularity isn't installed properly. |
Okay. I got it. I am trying on potential test. @d4straub Pipeline completed successfully on centos 7.5 and #102 (comment) but which cause this issue still unknown. Even I haven't test other pipelines, I think ENVs should be provided along with every nf-core pipelines. Now you can close this issue. |
@d4straub I just wander a suitable docker version. Can you tell me which your team was using now ? |
We are not using docker but singularity to execute pipelines. |
Thanks for your reply !!! |
Hi, I met this issue as follows.
The text was updated successfully, but these errors were encountered: