-
Notifications
You must be signed in to change notification settings - Fork 3
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
run without containers #29
Comments
Hello @HannoSpreeuw The makefile is provided as a convenience. This error message is from either For example, try In this instance I suggest |
Thanks. |
But my colleague found this package for installation of udocker. |
But is running prefactor-cwl without containers not possible at all?
Running without containers would involve a lot of extra work. |
Currently the Makefile installs the main udocker branch: https://github.com/EOSC-LOFAR/prefactor-cwl/blob/master/Makefile#L24 Can you try out the latest
|
Also, what is the version of |
[hspreeuw@fs5 prefactor-cwl]$ curl --version |
make run-udocker |
Needs lapack. Should be no problem. |
module load lapack |
Very weird. We have /usr/lib64/liblapack.so.3 |
Hi @HannoSpreeuw all these things have been more of a tech demo than a plug-and-play and ready-to-use solution. I'm not sure why udocker doesn't work, it looks like there might be a bug with it and it doesn't initialise the shared libraries properly inside the containers. Can't you use Singularity? |
Is this the default dataset, or did you edit anything?
Means that liblapack inside the container was not found (for whatever reason) so any changes outside the container (like |
That makes sense....duh. |
Somehow this error disappeared when I got more disk space on the cluster. Now |
make run on a cluster without docker gives
Docker is not available for this tool, try --no-container to disable Docker
So I tried
make run --no-container
but that gives
make: unrecognized option '--no-container'
So I tried
make --no-container
but that also gives
make: unrecognized option '--no-container'
The text was updated successfully, but these errors were encountered: