Closed koadman closed 2 years ago
Hello,
I am experiencing the same issue (ImportError: No module named pkg_resources). Did you find a solution?
I must admit I've not looked into this issue! I will make it a priority.
@escamero can you tell me what version of Singularity you are using? We've had some local insdtallations that were really old, which had more problems than others -- mind you, on other projects.
I have isolated this problem to a simple issue within the Singularity image: the path /lib/python2.7/site-packages
is inaccessible due to permissions. As yet, I have not explored how to correct this unintended side-effect.
Short-term Solution
As a running container is read-only this prevents a simple chmod, however you can create a sandbox version that is writable.
With the sandbox created, you can then apply new permissions to this path and bin3C will work.
# sandbox (file-system based)
singularity build --sandbox bin3c_sbsif docker://cerebis/bin3c:latest
# give everyone read and execute permission
chmod a+x,a+r bin3c_sbsif/lib/python2.7/site-packages
# run the container
singularity exec bin3c_sbsif bin3C -h
The new image has been pushed to Docker Hub.
Please note that the latest code exists in the branch py3
. I have just created a Docker image that uses this branch, but I will hold off on releasing it until I have time to test.
Attempted use of the 'latest' bin3c docker image via singularity fails: