[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1068578: RFH: singularity-container -- container platform focused on supporting "Mobility of Compute"



On Mon, Apr 08, 2024 at 08:59:26AM +0300, Andrius Merkys wrote:
> On 2024-04-07 15:28, Nilesh Patra wrote:
> > Assistance required with maintaining the singularity-container package.
> 
> I am not offering help with singularity-container, but do you by any chance
> know why apptainer is not packaged for Debian? I cannot find a wnpp bug.

I am lazy to find references right now, but you should be able to find it in
debian-hpc and debian-devel archives. If I don't miss anything this was the
sequence of events:

1) While updating singularity-container, Andreas created a repo for apptainer on
salsa.
2) The goal at that time was to get a mobility compute (either apptainer or
singularity) up and running
3) singularity and apptainer codebases are in sync so as per my understanding
there's no real point in having *both* - here's a brief discussion about it[1]

My opinion: It does not make a lot of sense to package apptainer as well.
Although the latter is "community" maintained, the codebases for
sylabs/singularity and apptainer are in close sync at most times which also
means they keep inheriting CVEs from each other too.

As a result one may not be able to maintain apptainer well in stable release
either unless they have:
a) Good/Great go programming skills
b) ability to deal with CVEs and backports

I'd like to just link to a similar discussion thread about the same rather than
repeating the points[2] and here's what upstream says[3].

What do you think?

[1]: https://lists.debian.org/debian-hpc/2022/08/msg00021.html
[2]: https://lists.debian.org/debian-devel/2023/01/msg00078.html
[3]: https://lists.debian.org/debian-devel/2023/01/msg00080.html

Best,
Nilesh

Attachment: signature.asc
Description: PGP signature


Reply to: