Project

General

Profile

Feature #22284

Allow the Singularity wrapper to ensure unicity of bind mounts

Added by Marco Mambelli 5 months ago. Updated 26 days ago.

Status:
New
Priority:
Normal
Category:
-
Target version:
Start date:
04/04/2019
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Description

Dave pointed out to me that older 3.x versions of Singularity were failing it the same destination is mounted twice (this is just a warning in 2.x and 3.1.1).

An option in the checks for the bind mounts could ensure that the same destination is not used twice.
Simple behavior consistent w/ Singularity is to use the first one and discard w/ a warning the following mounts on that destination

Evaluate the possibility to have a uniqueness selection where following definitions override the previous one. The main question is to define a consistent behavior between Factory, Frontend, and defaults. Which one sets the values, which ones can be overridden?

History

#1 Updated by Marco Mambelli 2 months ago

  • Target version changed from v3_5 to v3_5_1

#2 Updated by Marco Mambelli about 2 months ago

  • Target version changed from v3_5_1 to v3_4_6

#3 Updated by Marco Mambelli 26 days ago

  • Target version changed from v3_4_6 to v3_4_7


Also available in: Atom PDF