Docker/Singularity image?

[onertipaday]

First of all, thanks for this tool/pipeline: I've just started tinkering with it but it seems well designed. I was wondering if you are considering to build a Docker/Singularity image for making SAMSA2 installation even easier: I know it is a major effort but I'm convinced it could be very useful in spreading the software adoption (e.g., HPC environments). Thanks in advance.

[transcript]

I'm going to mark this as Enhancement and future update, but it's predicated on me learning how to build Docker images. It's on my to-do list, but it's overshadowed by some other priorities at the moment.

[sghignone]

I'm looking at it. I thing the best is to place the db outside the container, so not to make it enormous.

[transcript]

That would be best, most likely. We'd want to have two inputs, one for the Subsystems database, one for the RefSeq database (as they are organized differently). It's feasible to run the program with just one of these, so they would both be optional inputs, although at least one would need to be provided.

[sghignone]

Sam, as soon as I have more time I want discuss with you some enhancements I have in mind. I'll contact you in private.

[RJ3]

I created an Apptainer/Singularity container for SAMSA2.
(Apptainer is the new name for Singularity)

I agree not to put the databases in the container image because they are so big. I package them with SquashFS and then mount them into the container.

Are you still interested in this? @sghignone @transcript @onertipaday