On 09/09/2019 16:22, Loris Bennett wrote:
Hi Pablo,
Thanks for the info. Is there some particular reason why one would want
to use a system RPM? I generally prefer to install all our software as
modules to an NFS share, so there is no issue of roll-out to the cluster
nodes.
There's a couple of reasons why installing Singularity through EasyBuild
isn't the best approach (and not recommended by the Singularity developers).
The primary one is that you should only have the latest version of
Singularity available for your users, to ensure you're running a version
where all known/disclosed security issues have been fixed.
If you install Singularity using EasyBuild, you'll need to perform
additional steps afterwards which require 'sudo', since some parts
require admin privileges.
We've been reluctant to include easyconfigs for recent versions of
Singularity for this reason, but perhaps we should either remove all
Singularity easyconfigs to clarify our point, or make sure we update to
the latest available version ASAP (but that doesn't prevent people to
leave old Singularity versions installed).
regards,
Kenneth
I'll look into writing an easyconfig for Singularity 3.
Cheers,
Loris
Pablo Escobar Lopez <[email protected]> writes:
Hi Loris
In singularity 3.x the developers did a new implementation using golang instead
of the python/C used in 2.x
https://archive.sylabs.io/2018/02/singularity-golang/
This changed the build procedure for 3.x so the existing easyconfigs
no longer work with 3.x . Someone would need to create new easyconfigs
for 3.x. Also some users prefer to deploy singularity as RPM in their
systems.
regards,
Pablo.
On Mon, Sep 9, 2019 at 4:06 PM Loris Bennett <[email protected]> wrote:
Hi,
I see the most recent version of Singularity available is
Singularity-2.4.2-GCC-5.4.0-2.26.eb
Is there any particular reason why there are no easyconfigs for version
3?
Regards
Loris
--
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin Email [email protected]
