The normal singularity/apptainer validation has 2 parts:
return exit code 0
return a valid output that allows us to determine the apptainer/singularity mode or at least verify the correct execution of the command in the provided image
The 1st commit was "Accepting apptainer test also when returning the wrong output", was disabling 2 and accepting the apptainer executable as long as the exit code is 0. It also provides further debug output to help with troubleshooting. It was as a temporary workaround.
The second commit is the final solution and fixes #395
It kept the additional debug output, it is back to failing if the test returns the wrong output, and it fixes the regular expression validating the output.
There may be no initial blank if the first number in /proc/self/uid_map is big enough. This was tailing the previous expression.
The normal singularity/apptainer validation has 2 parts:
The 1st commit was "Accepting apptainer test also when returning the wrong output", was disabling 2 and accepting the apptainer executable as long as the exit code is 0. It also provides further debug output to help with troubleshooting. It was as a temporary workaround.
The second commit is the final solution and fixes #395 It kept the additional debug output, it is back to failing if the test returns the wrong output, and it fixes the regular expression validating the output. There may be no initial blank if the first number in /proc/self/uid_map is big enough. This was tailing the previous expression.