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
Crucially, the same would hapen if, e.g. /tmp/dlinstaller_env.sh was already present for unrelated reasons (e,g. created by datalad-installer).
This is probably not very alarming (given that /tmp is usually wiped on reboot) but maybe we can improve on build encapsulation.
Note: datalad-installerappends to the /tmp/dlinstaller_env.sh file; the cut command used in the definition file to get the temporary directory produces two lines of output if the file has two lines.
Reported by Stefanie
The text was updated successfully, but these errors were encountered:
Note: datalad-installer appends to the /tmp/dlinstaller_env.sh file; the cut command used in the definition file to get the temporary directory produces two lines of output if the file has two lines.
I can build the container image with
apptainer
(everything applies forsingularity
, too):When, for some reason, I want to build the image again, it fails:
The runs leave behind, in the host system's
/tmp
these files, produced bydatalad-installer
:Removing the
/tmp/dlinstaller_env.sh
file allows the new build to proceed:Crucially, the same would hapen if, e.g.
/tmp/dlinstaller_env.sh
was already present for unrelated reasons (e,g. created by datalad-installer).This is probably not very alarming (given that
/tmp
is usually wiped on reboot) but maybe we can improve on build encapsulation.Note:
datalad-installer
appends to the/tmp/dlinstaller_env.sh
file; thecut
command used in the definition file to get the temporary directory produces two lines of output if the file has two lines.Reported by Stefanie
The text was updated successfully, but these errors were encountered: