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
The current naming scheme for built singularity images derives only from the cfgtype and the cfgarch, such that any Singularity-based environment will be called "singularity-.sif``. This name does not encode the identifier of the template, and thus it will be impossible to have builder datasets with several Singularity-based but different build enviroments next to eachother.
As discussed in the call, we can fix this with parametrizing cfgarch, cfgtype, and template, and creating the buildenvironment names from all of them
The text was updated successfully, but these errors were encountered:
aqw
changed the title
BUG: All singularity build templates will be build with identical names
BUG: All singularity build templates will be built with identical names
Jul 12, 2022
mih
changed the title
BUG: All singularity build templates will be built with identical names
All singularity build templates will be built with identical names
Jul 12, 2022
The current naming scheme for built singularity images derives only from the
cfgtype
and thecfgarch
, such that any Singularity-based environment will be called "singularity-.sif``. This name does not encode the identifier of the template, and thus it will be impossible to have builder datasets with several Singularity-based but different build enviroments next to eachother.As discussed in the call, we can fix this with parametrizing cfgarch, cfgtype, and template, and creating the buildenvironment names from all of them
The text was updated successfully, but these errors were encountered: