You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we advise users that if they would like to demultiplex files they must first download bcl2fastq, move the .zip file into the programs directory, and then re-build the container. It would be convenient if users were able to add custom software into the container without needing to re-build it, perhaps by binding to a certain location within the container.
Let's see if we can download and build externally bcl2fastq and install it as a working version with any needed libraries or accessory files. If that is possible then really our fixed builds san bcl2fastq will be fine for reproducibility.
As for the bcl2fastq issue, I agree that we should explore building the software outside and providing the binary to the container as a binding. However, this is a compiled c++ program and how to create a portable binary is beyond my capabilities at the moment. Nick is probably the best person to consult on this.
There may be a potential solution for this in the use of the fakeroot feature. Administrators will need to ensure that user namespace UID/GID mapping is properly configured, which is outlined in the admin guide. It seems that admins can use singularity config fakeroot to set up the correct configuration for a user.
Users may need to configure their distribution so that unprivileged user namespace creation is enabled. In the case of REHL (which is what our server runs on):
Currently, we advise users that if they would like to demultiplex files they must first download
bcl2fastq
, move the.zip
file into theprograms
directory, and then re-build the container. It would be convenient if users were able to add custom software into the container without needing to re-build it, perhaps by binding to a certain location within the container.This issue was discussed previously by @JeffAndBailey in #32 (comment) and by @aydemiro in #32 (comment):
The text was updated successfully, but these errors were encountered: