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
Support for running Singularity-in-Docker or Singularity-in-Singularity has been informally tracked throughout the life of SingularityCE to date. We do not currently perform any automated testing of nested container execution. Issues arise from changes made to code where the effect on nested execution was not tested / considered.
Given extensive use of container-based CI systems to build containers, it is not uncommon for Singularity to be run under Docker or another OCI runtime. Similarly, HPC centers may e.g. run Singularity from a workflow that is itself run in a Singularity-based workflow automation.
We will introduce basic testing of nested workflows in SingularityCE's e2e suite. We catalogue, and will aim to address any blocking issues that prevent nested execution in native and OCI mode.
The text was updated successfully, but these errors were encountered:
Improve, document, and test nested container behaviour
E.g.
failed to add as session directory
#3217Support for running Singularity-in-Docker or Singularity-in-Singularity has been informally tracked throughout the life of SingularityCE to date. We do not currently perform any automated testing of nested container execution. Issues arise from changes made to code where the effect on nested execution was not tested / considered.
Given extensive use of container-based CI systems to build containers, it is not uncommon for Singularity to be run under Docker or another OCI runtime. Similarly, HPC centers may e.g. run Singularity from a workflow that is itself run in a Singularity-based workflow automation.
We will introduce basic testing of nested workflows in SingularityCE's e2e suite. We catalogue, and will aim to address any blocking issues that prevent nested execution in native and OCI mode.
The text was updated successfully, but these errors were encountered: